...That's why open-sourced add-ons are less prone to vanish in the dark in these scenarios....
What I don't understand is the notion of "add-ons stop working". They do not stop working suddenly, they simply do not work in a new Orbiter release. They still work fine in the release they were made for. It is not as if the software somehow "grew old"....
Just some comments if I may:
The reason I love sc3 and other ini based development is exactly that: you can reuse the work and it is open-source. :thumbup: I support 1000% that concept.
My comment to "stop working" meant not being able to continue to do the same development with new Orbiter versions.
As was mentioned before, a realistic multistage rocket, like my VLS addon, was complicated but very interesting to do by the numbers. But that's what I want: to study the rockets, the missions, do some simple but accurate meshes, and try to simulate them, then share with others. And that's what I was talking about... I like to create stuff, not spending all the time messing with code. I have a real life job were I do just that!
Regarding old versions, of course that I can reinstall ORbiter 2006... Heck, I even have MS SpaceSim working on DosBox :lol:!
But there's a limit to the actual possibility of running older Orbiter versions on current hardware. I don't know if really old version (2003?) will run in 64bits OS...
I hope this clears up what I meant by "stop working". It was in a practical, not in a technical sense.
Now back to the topic itself, the fastest way to get starting in reviving TTM24, is to simply reuse the meshes but not redistribute them. Make the user always download the original addon. I can't think of any better "give proper credit" solution.