Of course, this is also a function of playing a beta on a beta.
The F-14, F-16, Hornet, carrier, and many others are still in early access. They are available on the stable branch, yes, but they’re not close to done.
So logically if you can fly the released planes in the stable branch of DCS, with none of the above modules as AI either mind you, how many problems go away?
Obviously things like the MiG-21 radar/fps issue are significant, the 21 has been around quite awhile now.
Yet despite the appellation many people, including it seems ED at times, want to treat both OB and EA as if they were released. Hype and videos and such driving people to buy and fly today.
What they SHOULD be considered is “suitable for public testing.” Use them, find bugs, report them. Don’t make a massive MP mission on a server trying to use them all at once in a complex mission and then lose your #!$&@ when it inevitably breaks. Good testing minimizes variables to test specific things. About the only complicated test I would agree with is using the SC with the Hornet or Tomcat, because they really go together.
I personally don’t have 2 installs because of the space commitment, but honestly I should. Stable should have remained on 2.5.5 really. It was missing the lighting, the new modules, and a ton of fixes… but it was stable by DCS standards (lax as they may be at times).
When you want to try the Hornet or the carrier or the P-47 or whatever, you load up the OB and maybe connect with some others to see how things work and write down everything broken and report it.
Then when you want to actually do a good mission, you load up the stable and use the long existing planes and fly all night with minimal issues. We need to stop acting like the brand new stuff is good enough to use in that manner.