Lange_666

Solved: First went back to the previous Open Beta version, no joy. From there i updated to the latest version again, no joy. Checked again, in DCS the hotkey's didn't work, in other games they did. Uninstalled and re-installed TrackIR software + drivers: OK

Solved: First went back to the previous Open Beta version, no joy. From there i updated to the latest version again, no joy. Checked again, in DCS the hotkey's didn't work, in other games they did. Uninstalled and re-installed TrackIR software + drivers: OK

As a last resort i did a repair, first a fast one, then a slow one, no joy. I'm thinking of reverting to the previous version where it still worked but something tells me this won't fix it. Anybody any clue on how DCS communicates with TrackIR? Or through which file/script? If TrackIR is active, the keyboard view commands are not responsive anymore and should be replaced by TrackIR's axis (which still works) and TrackIR hotkeys for centering, presision and pausing (which stopped working).

As a last resort i did a repair, first a fast one, then a slow one, no joy. I'm thinking of reverting to the previous version where it still worked but something tells me this won't fix it. Anybody any clue on how DCS communicates with TrackIR? Or through which file/script? If TrackIR is active, the keyboard view commands are not responsive anymore and should be replaced by TrackIR's axis (which still works) and TrackIR hotkeys for centering, presision and pausing (which stopped working).

After the latest update (yesterday) my TrackIR partially stopped working. The axis all still work so i can still look around but none of the TrackIR Hotkey's are detected by DCS. TrackIR detects the trackclip (green led) and it detects DCS (blue led). It also overrides the game view center commands (which it should do) but DCS is unresponsive to the Hotkey's that are setup in the TrackIR software. Played around with new hotkey's, new some view key's in game, no joy. Outside DCS (in TrackIR software or other sims as IL-2 and MSFS) everything works fine, so including the Hotkeys set in TrackIR software. I don't know where to look next....

Nothing in particular if used straight as input device. When ExportScript is used (to get aircraft data onto the StreamDeck) there can be some hick-ups with certain modules (script depending). I just wonder... how do you gonna use StreamDeck in VR?

Since yesterday's update TrackIR Hotkey's are no longer responsive in DCS. TrackIR works fine in it's setup software, if i look around the view move like it should. Same for the hotkeys, they work just fine. DCS is recognized by TrackIR software (blue light comes on), green light comes on when trackclip is in view and within DCS, i can look around like i normally do. But none of the hotkeys is being recognized by DCS. I did re-setup the trackIR hotkey's with other key-combo's and changed that accordingly in DCS. Works fine outside DCS in other games (IL-2, MSFS), not in DCS. If i remove the trackclip (green light goes out), i can use the keyboard that i just had setup to center the view, the moment in put the trackclip back on (green light turns on again), they become unresponsive. Also, everything concerning TrackIR is greyed out in the controls setup of DCS. I also noticed that for each module a new module input folder was created in the main DCS directory (not saved games) in the Mods\Aircraft\Input folder: A-10C example: Drive:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Input\A-10C. In here is a file "name.lua" which is created/updated with the new patch. It only contains the one line: return _('A-10C')

If i'm correct you need to buy a separate adapter to make this work with VKB. If you go Virpil (WarBRD base for sure) there is no need to use an adapter and you can use it with Target software (if you should use that) by rewriting the VID number of the device.

Exception are VIRPIL (bases) where you can rewrite the VID number making Target believe it's a Warthog stick/base.

Not in the mood for arguing? You... by all people? Unbelievable...

Really? And what's CEX play in this that it still works flawless today? None !! I have bought a 2nd handed MSI 1080Ti from somebody i didn't know which was then 2 years old and it worked flawless for another 3 years, i sold it a few months ago and even then it still works fine to this day. So i don't get your point.

I was reading this yesterday and thought "this doesn't happen to me" but this morning after my PC started i set everything up for a flight, loaded the utility, it still showed VR Headset as profile from my previous flight, selected Preset VR agai, and hit the VR button only to be greeted with the default settings when the game was loaded. Since nothing has changed in the utility i'll suspect the latest beta to be the culprit.

Bootloader method for re-detecting an undetected TM device. Worth a shot... https://ts.thrustmaster.com/download/accessories/pc/hotas/manual/HOTAS_Warthog/HWarthog_Bootloader_Method.pdf

At least this part looks OK. Means Windows sees it. Could be a conflict between WinWing and Thrustmaster. I would remove WinWing and test.

I have no clue. None of HID entry ever carried the name of the device they are connected too and even if i look into detail or events i only have USB/VID number and other data, never the device name. nullnull

I was not referring to USB sockets on your computer (i guess you swapped the stick around already to rule that out) but the USB connection of the stick itself, also check internally in the sticks base.

But even then the axis of the stick should work since they are setup by default. + No stick on the Control Panel / Devices and Printers (but the throttle is present) and Falcon 4.0 doesn't see it either.

Since you didn't mention you uninstalled and re-installed (reboot in between) the Warthog drivers you could give that a try. More to try: open up the stick,s base, looking for a (partly) disconnected plug, faulty USB wire/connection, stick to base connection etc...

More to try: Go Devices and Printers in the Windows Control Panel. Select either stick or throttle, right click, select Game Controller Settings, select either stick or throttle again in there, select Properties and see if the stick/throttle reacts to inputs.

Ok, nothing disabled. What about my 2 other questions?

Can you give some extra info on the phrase in red because i don't understand what you mean and how you "checked the driver and the window indication"? You mean it's still detected by the Windows Device manager? Any other game installed you can try the Warthog on? If you go to C:\Users\Your Name\Saved Games\DCS\Config\Input do you have a disabled.lua there (on the bottom of the list). If yes, what's in it?

They only offer rotor pedals according to their website. Links to their previous devices show empty.

I guess you can say that for a lot of headsets these days. Also i believe that that more and more headsets will go the wireless road. That's why i didn't get one yet, too much hassle to my liking to get it going (maybe i'm spoiled in this area with my Rift-S, start Oculus software and off you go) and the lack of display port.

@whitav8 really? Next time you ask a question my finger will the only thing you gonna get.

No, i subscribed for a test run on the MFG website. Milan wanted a test group of 30 people in the test run. The first ones i got for testing are the ones with the cutouts. Since i wanted an option to mount them lower, Milan made and send the ones with the 12 fixing holes. I have no idea what the other testers reported or what they got send as test pedals. I see that the ones with the cutouts didn't make into production, and the others i have never tried or seen. Mine don't have the MFG logo either. The ones i have resemble most to the grey ones: I'm also using a modified brake limiter set so i need to put less force on the pedals for braking. I have a set with an extended arm above the upper bolt with more holes for the spring to attach. Milan was so kind to make them on demand after i reported that i wanted to use less power for braking because using combat pedals requires a bit more force under braking compared to the ME109 pedals. I now see on the website that you can get a set of lighter springs instead.