tarball

seems like a significant regression as most quality tutorials an references suggest that the flashing ATK on the HUD is there to help return to gimbal limits.

what became of this?

Is the new 2.0 version self updating? I can't quite tell from the UI.

Very interesting omission here.

Thanks. The manual in the Release version is older and the manual in the Open Beta version is newer, but not RC7 either.

Perhaps a silly question, but I'm guessing these updates only apply to Open Beta for the time being?

Straight to OB or will it appear in stable?

this needs to be stickied

Thanks for the post, going to check it out now. I sometimes wonder why ED bothers with a Beta/Stable version when things like this don't make it to the stable version. Then again, perhaps the 2020 version isn't finalized either. About to find out...

The bigger bug is the reflection. I wish FC3 got more love.

This too is my number one flown aircraft in DCS, far and away. Something about the Rook is compelling. Great ground attack and handling. I'd love a full fidelity as well. Ditto for nearly all the Russian aircraft.

old bugs, inconsistent and not up-to-date documentation. Then I see the ambitious product roadmap and realize that ED enjoys almost perfect market monopoly in their space. Despite this, they will be taking on the AAA, Ace Combat, Air-Quake space with Modern Combat. DCS is a pretty girl and gets away with these flaws. BMS is and older and not-as-pretty gal and has to deliver the goods, But yes, thank you for pointing this out as I love flying both the frogs.

I can't tell the rhyme or reason for what is fixed or not in DCS but these errors are very annoying as they remain in place for YEARS. Why would I have confidence in other products when simple products are left like this for a long time?

It seems DCS 2.5.2.18736.400 may have fixed this? can anyone confirm?

Why does this manual "dance" persist if this is a known performance issue? Why wouldn't the game do this internally? Just curious.