Lange_666

Made a bit of video of the problem I encounter in the F-16C Free Flight mission. The inverted dive isn't necessary to trigger the F-16 choppy behavior. It can be triggered with any stick input. You can see that the F-16C rolls to the left every x-seconds. I then correct it. The last part of the video i don't correct it anymore and the plane goes rolls left and starts to climb (controls indicator shows no input at this point). Trim is neutral, so no trim input at all. This only happens on the Afghan map and in the Free Flight mission.

After updating to the latest version and installing the Afghanistan map i went in for a quick flight, took the F-16 Free Flight mission but the plane behaves weird. It pulls up gently without stick input and neutral trim. When i roll it upside down and pull a down warts 180, halfway through the dive the nose jumps to the left a bit and after leveling out the F-16 does a 5 to 10° roll to the left and then starts to pull up. If i counteract the roll with a bit of stick input, it flies level again but a few seconds later the same roll to left happens and this goes on and on even with the stick input to keep it upright. Trim doesn't help and even if i get it trimmed it won't stay but does the same thing over and over again. Then checked my inputs and curves, all fine. So what's causing this? First thing that came to mind was the overall update so i went into the F-16 Free Flight mission on a few other maps (Caucasus, Syria, Persian Gulf). No such problems there. F-16 flied like it should. Then tried the A-10 CII runway take-off mission on the Afghan map. Rolling down the runway i had a hard time to keep it going in a straight line, plane went from left to right, needed to correct a lot. When in the air, it behaved better then the F-16 but still had to correct a lot and also couldn't really trim the plane. No such problem on other maps. Then created an F-16 Free Flight mission on the Afghan map. All fine, no weird behavior. Next step, slow repair. Same problem, only on the Afghan map Next step, edit the original Afghan F-16 Free Flight mission, empty load, wind overall at 0 f/s. F-16 still shows weird roll / pull-up behavior. So what's causing this? And only on the Afghanistan map. Input controller panel shows nothing special, all fine.

It's the Turbo set to ON setting in OpenXR Toolkit when running DCS in MT that causes the game to crash when taking the headset off. In ST there is no such problem.

Virpil WarBRD base. If you drill new holes on your TM baseplate you can use that to mount your Virpil base on it because i found the Virpil base plate not stable enough when doing rough manouvres. Also, the TM stick is a lot heavier then the plastic Virpil stick so you need the heavy springs set mounted in the Virpil base to prevent is from leaning forward. But... once that is done you're all set and you'll notice the Virpil base is way much better then the Warthog one. If using TM Target you can get it to recognize the Virpil base as a TM base. Or get the new TM AVA base. Virpil example

Exclude your DCS folder in your Anti-Virus software and run a DCS repair to replace the 3 files that your AV probably has put into quarantine.

Oh well, you can't always read everything...

It's not available yet as far as i can see. null

It's a closed AIO system (All In One = pump+flexible tubes+radiator+fans). They are no more pain in the ass then an air cooled system.

Yes but... for how long? The 12GB on my 3080ti get already totally filled up on more demanding maps and that's not at full max settings. It doesn't cause any stutters at a capped 60 FPS so it's perfectly fine to play with the VRAM maxed out but you then buy yourself a system which runs against it's limits already. Same goes for the RAM. I have 64GB and it goes above 32 GB on more demanding maps or multiplayer and also not at max settings.

No need to thank me. Don't forget to run a DCS repair to get your quarantined files for the F15E and M2000C back in place (you might take a look at this: DCS Updater / Launcher to get your DCS stuff done from one single app. tip: don't mess with the Graphics Preset Editor)

No !!! You need to exclude the DCS folder in your anti-virus program so your anti-virus will skip it during scans Don't worry about the scan skipping stuff, if a real virus would reside on your computer, it will 99,99999999999999999% not originate from one of those files your AV found in your DCS folder. You mentioned you are using Windows Defender. For Windows 11: - Start: type Settings in the search bar, select Settings (System) - Go Privacy & Security - Go Windows Security - Go Virus & threat protection - Under "Virus & threat protection settings" select "Manage settings" - Scroll down to Exclusions and select "Add or remove exclusions" - Click the "+ Add an exclusion" button and add your DCS folder (and your Saved Games folder at the same time) there. Now run a repair again to redownload those files that returned a false positive. Once done you're all set.

Then you don't exclude DCS the correct way because if excluded it from the AV check and run a repair to get those quarantined files back, nothing DCS related should come up.

Your files are not infected. Your AV just detects it as a virus (even low risk!!). Like MAX said, there are numerous posts and threads about these false positives here in the forum. Never did i read that one of these false positives turned out to be a true positive. Just exclude your entire DCS folder (or the Mods/Aircrafts folder) from your AV scan, run a repair (to replace the quarantined files) and you're all set (or stay scared).

Grow a big pair of balls, exclude the DCS folder (or only the files that cause your AV to trip if you have small balls) from the AV scan and move on.

I have the same hashnr for this dll file. Removed the DCS folder from exclusion in the AV scan. When I then scan the single file with my AV it comes up clean. Then scanned the entire DCS folder, everything clean. Re-added DCS folder to exclusion in AV settings.

Yes (although I never felt the VKB Gladiator). It will depend on the size of the baseplate. For example the baseplate of a Virpil WarBRD is a bit smaller and a lot less heavy than that of the Warthog but I found the Virpil one it not stable enough when doing quick/hard maneuvers. So I drilled new holes in the Warthog baseplate to mount the Virpil base on it.

- Virpil (depending on the cams used) - VKB (depending on cams and gimbal design) - Thrustmaster with the new AVA base (depending on the cams) - Winwing (depending on the cams used). - others? My Virpil WarBRD base goes around smooth with no transition.

I would at least try other cams. On my Virpil I use cams with no center feel. The original cams had a feelable center point, I didn't like that.

From the bottom reply's on the above posted video: The ava emphasized that my f18 grip had a something loose in the pitch axis that made some clunk (roll was ok. a10 grip was ok) ... Googled it... its common. I opened the grip and retightened and loctited all the screws and the clunk is gone. There is one obvious screw inside that was the culprit. Had nothing to do with AVA but was very noticeable with AVA.

Personally I prefer the XL version. On the 15 button version you loose at least 2 buttons per page to go back and forth between pages leaving you with only 13 buttons (same goes for the XL off course but you still have 30 buttons per page to play with)

Just right click on a slot, it will show you the options to set the path yourself.

Virpil base has the same issue (with heavy (metal) Warthog stick mounted on it). I guess that with a lighter (plastic) stick it balances out more quickly. But, i never found this to be a problem. I never release the stick like in the video anyway so it's actually a non-issue.

I have crashes with Rift-S and running MT with Turbo Mode On when taking headset off (ST is fine). Turbo Mode set to OFF solves the problem. Bug has been around for quite a while, nothing to do with latest updates (either DCS or Oculus).

Works just fine right here and never got a Windows Defender action/warning about it.