Say, if I understood you correctly, you mentioned somewhere that the maximal size of the cargo-boxes is 1.3 m^3. Isn't that a bit small? besides a small probe there's not much vessels you can pack into such a box to use this awesome feature.
Now that is cool.
Is it possible to have a version without a heatshield to save on mass when landing on an airless world?
Is the guidance just deorbit and land, or does does it target a specific point on the object?
Can other probes be made which use the same code base?
awesomely awesome man! cant wait for the release and will it land anywhere or can you specify where it will land?
Does the Arrow's autoland only work with XPDR, or can it land at regular pads?
Say, if I understood you correctly, you mentioned somewhere that the maximal size of the cargo-boxes is 1.3 m^3. Isn't that a bit small? besides a small probe there's not much vessels you can pack into such a box to use this awesome feature.
Unfortunately for the allmighty Probe his son is a bit idiot, and so it only deorbit and land straight where he can. Such complex autopilot would take one month at least of work and I did this in two days including the model.
"other probes"
You mean if I open the source ? that is possible for those that want it but all the commentary are in french as I took my Vessel template as source:
http://orbiter.dansteph.com/forum/read.php?f=5&i=10241&t=10241
-Ressources cargo (as fuel, oxygen etc. that can be "eaten" using the Vessel SDK
To clarify, I meant can other probes be made by interfacing with the UCGO SDK?
UCGO SDK for cargo is only providing a "packed" cargo mesh and a config file. Once the cargo unpacked an Orbiter "vessel" is spawned and author can do whatewer Orbiter C++ SDK permit. It's a vessel as any other.
The UCGO SDK don't care at all what are in the "spawn" type cargo and there is no "Probe" lines of code into the UCGO SDK is this is what you mean !?
Mhh I'm not sure I get your point and if my reply is clear ?
But if one want to make a better or another probe I'm ready to give my probe's source. (not cleaned and commented, but it contain only few lines)
Dan
Just some English nit-picking here. "Consumed" is a better term for "eaten".
What about "wolfed", "scoffed", "quaffed" and "nommed"?
Just some English nit-picking here. "Consumed" is a better term for "eaten".
I do know that people would like a self-landing cargo package. I remember seeing a discussion earlier about making a generic lander for Earth and Mars operations. The code from the Son of the Probe would be useful in that regard.
Or there could be a "Bombing MFD" or "Probe Release MFD": input landing point and store flight plan
Om nom nom nom nom... That's a tasty cargo you have here. :rofl:What about "wolfed", "scoffed", "quaffed" and "nommed"?
!! (We need a new smiley just for him...)"Vessel" in this case mean "active C++ module", spawning a Shuttle would look unrealistic of course but you can program a lot of active things: Probes, nuclear bomb , missiles, rescue module, explorator rover (You can spawn a UCGO small rover for example), base module, robots, everything active that would fit in 1.3 once packed in fact.
I'd bet on "Lesser Probe".:tiphat:And out of curiosity, is the (Idiot) Son of the Probe a False Probe, or just a lesser Probe? :lol:
Does this mean that UCGO looks for a 1.3 m^3 size limit on active vessels that can be spawned, or just that it would look silly to have a Shuttle-A (or Arrow, haha) get spawned out of a cargo container that is only 1.3 m^3 in volume? I'm thinking the latter, but wanted to ask.![]()
Is it possible to use the SDK to define the SOTP as cargo within cargo? In other words, deploy the SOTP cargo, poof there's the SOTP, SOTP lands, some pre-defined time later, poof there's something else spawned out of SOTP.
Don't moke the ISOTAP he just had no luck during birth... Lack of LOX during a few minutes...