Sabadin

That's not a setting, that's instructions on how the different VR interactions work. Which is why 6of6, if I recall correctly, says "I don't know what this does" for certain hand controller buttons.

I know it wasn't in the patch notes, but just tested and this issue still exists in version 2.9.4.53549. Is there any traction on this besides "Purchase the SC module"?

100% reproducible by not having the Super Carrier Module installed as per the other thread on this issue.

Is this being tested internally both with and without the SC module installed? Because the controls remaining locked up after launch is still occurring in build 2.9.3.51704 without the SC module installed.

It's already happened to ED once, that's why forum rule 1.16 exists.

It's officially happening!!

The INS ATT advisory on the DDI is likely what is causing the Autopilot to fail to engage.

From the patch notes DCS Flaming Cliffs by ED MiG-29G. Cockpit indication doesn't work - fixed MiG-29. Large bounce after a heavy landing, no nose gear damage - fixed Su-25. Added single mission to Syria map SU-25T. SPPU-22-1 gunpad not doing any damage to light armor - added some armor piercing shells into the round rack Updated / added Instant Action missions Hadn't had a chance to test it myself, was an unexpected surprise to see in there.

Pretry sure your memory is serving you right, I also remember FC adding the 25T as the test bed for AFM. Edit: Upon reading the Flaming Cliffs section of the website you were definitely remembering right; Product Overview New product features include: All the capabilities of "LockOn: Modern Air Combat". Addition of the Su-25T as a player-flyable aircraft.

Finding myself in a situation where I'm currently stuck using the exact same GPU what I can tell you is basically leave the radeon driver settings at default, goes into the DCS settings and hit the Low preset, turn the normal textures option to high, if you fly mostly newer modules you can try medium but it's an unreadable mess on older ones. Make sure ground shadows are off, regular shadows you can set to low with minimal impact. Pretty much turning anything else up or on its going to be noticeable. Outside of larger cities, as long as the CPU can keep up, you can expect it to hold 20-25 and fps stable, not ideal but workable. Around larger cities, don't expect more than 12-15 fps no matter how low you crank the settings, the card just can't do it. And don't bother overclocking your 6850, the 1GB memory is mainly what holds it back and no safe level of OC will make a noticeable impact.

Having been through a similar scenario, as long as you remember your DCS e-shop username to be able to recover you're password, then you're all set. If the profile contains an A-10C key from the open beta then your NTTR key was automatically added to your profile.

If the airfoil on the horizontal stabilizers is like most traditional ones, they actually generate a downward force, so losing the right stabilizer would result in the left stabilizer generating an unopposed downward force on the left side. Sorry I'm on mobile so can't really throw together a good diagram

Silly question time; Have you tried unchecking "Disable Aero Interface" if you haven't already? I seem to remember that being a common issue when that feature was first implemented.

Well, it's definitely still the official RCAF designation, I'm guessing it was just to emphasize that they weren't really stock A models. http://www.rcaf-arc.forces.gc.ca/v2/equip/cf18/index-eng.asp

I think that's been the official designation for them since day 1, just nobody ever actually calls them that.