with the little that ive managed to learn of C++, i can imagine that it is simpler than other languages, you can just define constants of heating rate, and other parameters, then have each one change independently through user input or feedback from other parameters, and its quite free since you dont have to define them i a particular order or strict way. what i meant was the sheer number of variables that will be floating round, and it one goes "iffy", it could mess up quite a few other systems, then be a pain to find again
im sure you can manage it, the 100 was good stuff, this has potential to top the XRs, and i really mean that. just dont make the sub-systems as complicated as the Dragonfly's, a get-in-and-go mode would be nice (AUTO switch settings are nice)
which just gave me an idea: perhaps you could implement the AUTO settings, then make two vessel modes: noob and pro (names to be evaluated), in noob scenario,s everything is automated for you (or near enough) and in pro, you need to handle the sub-systems as well
looking forward to seeing this thing pan out!
it's not gonna be "dragonfly complicated"... that would be a lot more than what i'm going for here....
but what makes C++ good for handling this kind of thing, is that i can write up a class that generically represents the dependancy of a system from others by using a collection of pointers to the status of those other systems , so if it works once, it works always :yes: - that's the beauty of well-coded object orientation

plus, with multiple inheritance, C++ reigns supreme above the vast majority of other languages that disallow it in their unprobely ways, and makes things like this a lot more straightforward to conceive and set up :thumbup:
may the Probe be with dr. Stroustrup for creating it! and with dr. Schweiger for ever so kindly allowing us to use it! :lol:

---------- Post added at 05:19 PM ---------- Previous post was at 05:16 PM ----------
I honestly don't see the point in that. If a newbie wants an easy ride, he can fly an easier vessel.
It's better to make these things too hard than too easy. Too hard and it challenges you to learn. Too easy and it gets quickly boring. Orbiter I think is an excellent example of that. It's the way of the Probe.![]()
it is! the Probe smiles upon all things that are of complexity akin to rocket science and those who venture into learning those things :lol:
Also you can always use Lua for creating flight school scenarios. :thumbup:
have considered! - but i'll leave that for later, after we have actual systems to teach
