Puts the Fun in Dysfunctional
Absolutely you can have both, you can do whatever you like with it! I would suggest having the "developer" builds have a marker in their versioning somehow, to make it obvious to consumers they're effectively prerelease or snapshot builds. But I love the idea of a community of open source addons consuming the latest Orbiter changes automatically and rebuilding against the latest code to check they remain compatible!Could you do both? You'd have your release packages along the way to provide users with the latest stable version, but you would also have the "current" package for developers, built from the latest master commit. Maybe they could even set up their own repositories to look for changes in that package, automatically fetch it and compile their own addon coded against it, to get instant warning of impending trouble.
I like the beep change, for sure! The others are a bit subjective (e.g., the new scrams sound harsh to me), lol. In any case, I love the idea of having multiple sound packs users could choose from and use -- we could even bundle them all into the main XRSound zip.
Thanks for making this open source! Crazy week it has been for orbiter fans. I would love to contribute with this if you guys are interested. I'm not as smart as most of you so I won't be of any help programming and such but I do love sound design so I could do an overhaul of the sound to make it even more immersive. Not that the sounds are bad or anything right now but they can sound a bit flat at times. I made you guys a few a/b examples.
Let me know if this would be of any interest. I love doing these things and I love Orbiter.
I like the changed beep, and the APU - the scram is indeed quite a harsh re-imagining, but I really like the idea of these being selectable options, that the user can choose from.