Lange_666

@BunyipBilly : 3th and 4th paragraph.

Triple buffering set to ON? If you hoover over it, it says: Allows you to enable or disable triple buffering for "OpenGL" applications.

Not much anymore, most values just show zero these days (used to be different).

I have the same feeling that overall rudder sensitivity has changed a few updates ago (since 2.9.6 if i remember correctly). After the update the aircrafts went "almost violently" left or right when rolling down the runway even with the slightest rudder input. At first I thought that the update had reset my rudder curves (also MFG Crosswind) to default. This was not the case, my set curves per aircraft were still all there. Maybe something has changed to the nose wheel behavior?

That's recently added then because i mentioned on their forum that i couldn't get the 4 to see the trackhat with 5.5.x but the official support dude from NaturalPoint who replied to my question a fewtimes never mentioned that a TIR4 would not work with 5.5.x. So... TrackIR 5 OR NEWER? Something in the pipeline?

For those who got it solved: What version of TrackIr are you using (4, 5 or even earlier hardware)? I can't get my TrackIR 4 working under any 5.5.x version (5.4.x works fine).

Unplugging USB didn't cut it for me (TrackIR 4). Still no detection of my Track hat with 5.5.1. Reverted back to 5.4.2.

Same here, no detection of my track hat on my TrackIR 4 when using 5.5.x (it's not a DCS issue, it's general). Reverting to 5.4.2 and all works fine again.

Still on a TrackIR 4 here. 5.5.x will not even detect my track hat so it doesn't even work at all in any sim. Reverted back to 5.4.2 which works fine.

Crap, i posted in the wrong thread. Can happen when you have to much tabs open...

Create an exception in your anit-virus software for the entire DCS folder and the DCS folder in your Saved Games folder. Then run a repair to get the files back your AV might have quarantined and you're good to go.

Yes, since they are not stored online but as a diff.lua file (as in different from DCS default) in your Saved Games DCS Input folder. The only time it would not be recognized is when you would do a full re-install of Windows because Windows will then re-assign a new controller ID number to your controllers. Since your backup uses the old ID numbers, the only way to get it working again is to replace your old controller ID's with the newly created ones. Example of these ID numbers (between the {} )

No poles here, mine is desktop with no extension.

I just wonder what the problem really is with wobbling? All bases (Virpil, VKB, TM AVA, old Cougar mods) which use a similar gimbal approach wobble around the centerpoint. This is due to the design. They will always wobble, and will wobble more with lighter springs and heavier sticks. But... it never has been a problem since i don't let go of the stick. So i just wonder what problem people have with the wobble. I prefer this 200% over the imprecise sticky plastic original TM WH gimbal which went out of the door as soon as i got it.)

@BIGNEWY: Something should be done about the possibility to buy separate modules that are incorporated into one single big module. If owning the whole module already, it should not be possible to buy the separate modules. FC is THE example. The individual modules should be greyed out in the e-shop if you own the full version.

If you do a little search here on the forum about AV scans and reporting viruses after a new update in DCS you would find lots of threads about it all telling the same thing: It are false positives !!! Just exclude the entire DCS folder and the Saved Games DCS folder in your AV scans and forget about it...

Same here. Really didn't think it was the autopilot correcting my inputs as none of the other free flights on other maps have it turned on.

Damn, i feel such a noob. Totally overlooked that.

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...