![]() Edited Decemby DMagicĪlso, keeping track of orbital parameters for a certain duration is fairly straightforward, it's just the details that get in the way. Orbital Science does this in what I think is a pretty sturdy way. What happens when you dock or undock? Saving and loading which vessel is being tracked, checking if there are any requirements for the vessel, etc. Deciding how those GUIDs are sorted and what to do with them is another matter.Įdit: Also, keeping track of orbital parameters for a certain duration is fairly straightforward, it's just the details that get in the way. To make it persistent you would need to use a scenario module and just print out each GUID in a string whenever it saves. GetHashString is based (I think) on the contract title, and parameter titles and I think some other things. It's what gets stored in the persistent file and isn't based any parameters or values of the contract. ![]() You're looking for the unique contract identifier? Contract.ContractGUID is probably the best. Now to figure out where to steal some code for keeping a dictionary persistent for a save game, probably from KAC. More testing is required, but I think Contract.ContractID is going to work better.ĮDIT: Contract.ContractID does seem to be unique, and persistent between reloading the game. GetHashString() won't work: it keeps on changing when the scene changes. Thanks for the help: the dictionary idea is promising. I also really like the idea of being to use "shortcut" orbits that have fewer parameters to specify. But I think the most user friendly way would be as you've suggested - by letting the modder specify the orbital parameter, and having ContractConfigurer translate that into 3-4 Fine Print waypoints. Fine Print does this by defining waypoints though. Having a contract parameter where an orbit is defined is pure Fine Print territory - so this is definitely something where I'd to accomplish through integration, rather than creating my own parameter. ![]() Maybe I'll play with the code and see what I can do. "Tundra" orbits, Polar orbits, Keostationary, Keosynchronus, etc etc. It'd be really cool if there were some pre-defined orbits as well using the celestial body's parameters (so it'd work with RSS and 6.4x kerbin). of AN, AP Height, PE Height, or just Semi-Major and Semi-Minor Axes). I'd love to see parameters for Orbital Period, Eccentricity, Inclination, and other orbital parameters (Arg.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |