- Joined
- Jan 7, 2008
- Messages
- 5,790
- Reaction score
- 780
- Points
- 203
- Location
- Earth
- Website
- orbides.org
- Preferred Pronouns
- she/her
Makes sense, to a point. Then again, if it works on one system, it does not guarantee other systems will support it, making same uncertainty, albeit smaller.Because users care more about what does work with Orbiter than what doesn't. If you're looking for an addon and want to know if it's compatible with Orbiter 2010, but you only have a list of what has been tested and found broken, you still won't know.
And how said developers are supposed to know what to update? One example, Orulex 1.2, works fine for me in O2010, yet people asked for an update. Update out, lots of thanks, zero feedback, request for an update again.Isn't it the responsibility of the developer to determine whether or not their addon works, if they care about it continuing to work?
What does not work? How am i supposed to know?
Another example in a post above -
I sure would, but it's the first time i heard that there is a problem.There's neither a Meshland nor a Collision module for Orbiter 2010 yet, hopefully Artlav will provide a new one
Bottom line, a list of add-ons that work is GOOD, users come first.
But a list of add-ons that don't is also welcome.
Anyway, enough ranting about myself, there's a great new Orbiter 2010P1 to try out and
Which looks pretty much awesome.There's now a Project Apollo - NASSP 7 Beta for Orbiter 2010-P1: