Lange_666

I keep both left and right combined and only use it for the Collector. I also use it reversed, forward is Collector up instead of down. It's not what it should be but it works good enough for me. And... I fly heli's mostly in VR, makes things a lot easier + i mainly only fly the Huey, not the rest that I own. AH-64: although I find this a superb heli, I don't really like any 2 seater, plane or heli, wagon wheel comms for flying and getting the AI part to work are not really my thing (ditched the F-14 for that, will not buy the F4, C-47 and Hind for the same reason). Gazelle: tried it on a 14-day trial but found it way too twitchy, never found a good control setup.

There's a slider for that in the options tab "special". Also appliable for Mi-8 and AH-64: Ka-50 does not has that slider Don't know about Gazelle or Mi-24, i don't have these

Not a PL owner myself but stumbled upon this in relation to the floating out of the cockpit problem: It happens in MSFS2020 too. Read down from this post: https://www.avsim.com/forums/topic/651840-watery-edges-when-looking-sharp-left-or-right/?do=findComment&comment=5202273

In the last decades glacial stuff keeps moving faster and faster so we're good then? However, it moves so fast that it disappears...

I always had a response from them, can take a few days though.

^^^^ this ^^^^ It was mentioned by Skatezilla 2 pages up:

I have the same, never used the module manager anyway so...

Mmm, weird.... I don't have any of these issues. The preset I select stays selected and MT stays OFF after a reboot.

Let it go dude, you're pushing the wrong buttons!

Because stopping of a script all of a sudden required some time again I did some search again. A new Target version has been released, V3.0.24.618_rev1 which now includes AVA and a bugfix for the T.1600M The new Target version does not solve the above problems. Dragging the windows around in Target still defaults them back when Target is closed and reopened. I do have the Thrustmaster Combined device now when I open the Device Analyzer but not the single devices when no script is running. My MFD Crosswind pedals show up here when no script is running but disappears when a script is running. Stopping a script still takes time, going from 2 to 10 seconds. Searching the net I found a possible solution to this by deleting the DeviceManagementApp.exe. This stopped the script immediately when stopping a script but as I found out later, creates another problem where the single Warthog devices were present in game and also the combined one was when a script was run. This could lead to double inputs when a button or switch was activated. So that "solution" was a no go.

Did you open the link and read what you have to do? It's all explained in steps.

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