Jump to content

"TrackIR Device Unplugged"


Recommended Posts

DCSW 1.5.4, Win 10, TrackIR 5.4. and track clip pro. While flying simple missions in A-10C my TIR stops functioning and a message appears in top right corner: "TrackIR device unplugged" After a few minutes, TIR begins working again and message "TrackIR device plugged in." (or something like that). I have been using TIR for over 10 years with many other sims, including earlier versions of DCSW and never had this issue until now. I have tried to track the problem to perhaps interference from key presses or other controller inputs with no joy. Both TIR camera and pro tracker are plugged into main motherboard USB connectors.

Link to comment
Share on other sites

  • 3 months later...

I am having similar issues with similar setup, and the problem is consistent among Alpha and Beta.

 

My logs show multiple repetitions of keyboard and joystick lines, and the problem can be caused or sometimes remedied by either ALT-Tab to go to/from full screen mode. or unplugging and reconnecting a USB device.

 

If the problem is in repeated USB device initialization, what is the solution? Thanks!

 

-----LOG BELOW---

 

06088.025 INFO INPUT: Device [Keyboard] created deviceId = 95

06088.027 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 96

06088.027 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.042 INFO INPUT: Device [Keyboard] created deviceId = 97

06088.044 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 98

06088.044 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.059 INFO INPUT: Device [Keyboard] created deviceId = 99

06088.061 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 100

06088.061 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.076 INFO INPUT: Device [Keyboard] created deviceId = 101

06088.078 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 102

06088.078 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.092 INFO INPUT: Device [Keyboard] created deviceId = 103

06088.093 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 104

06088.093 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.225 INFO INPUT: Device [Keyboard] created deviceId = 105

06088.226 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 106

06088.226 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.242 INFO INPUT: Device [Keyboard] created deviceId = 107

06088.243 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 108

06088.243 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.244 INFO INPUT: Device [Keyboard] created deviceId = 109

06088.246 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 110

06088.246 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.259 INFO INPUT: Device [Keyboard] created deviceId = 111

06088.261 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 112

06088.261 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.275 INFO INPUT: Device [Keyboard] created deviceId = 113

06088.276 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 114

06088.276 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.525 INFO INPUT: Device [Keyboard] created deviceId = 115

06088.527 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 116

06088.527 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.527 INFO INPUT: Device [TrackIR] created deviceId = 117

06088.542 INFO INPUT: Device [Keyboard] created deviceId = 118

06088.543 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 119

06088.543 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.544 INFO INPUT: Device [Keyboard] created deviceId = 120

06088.546 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 121

06088.546 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.547 INFO INPUT: Device [Keyboard] created deviceId = 122

06088.549 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 123

06088.549 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.559 INFO INPUT: Device [Keyboard] created deviceId = 124

06088.619 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 125

06088.619 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.622 INFO INPUT: Device [Keyboard] created deviceId = 126

06088.625 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 127

06088.625 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.626 INFO INPUT: Device [Keyboard] created deviceId = 128

06088.629 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 129

06088.629 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.644 INFO INPUT: Device [Keyboard] created deviceId = 130

06088.648 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 131

06088.648 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.658 INFO INPUT: Device [Keyboard] created deviceId = 132

06088.660 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 133

06088.660 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06088.675 INFO INPUT: Device [Keyboard] created deviceId = 134

06088.677 INFO INPUT: Device [Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}] created deviceId = 135

06088.677 INFO INPUT: Joystick created[Logitech Extreme 3D {3001CCF0-0D4F-11e5-8001-444553540000}], ForceFeedBack: no

06144.070 INFO EDCORE: (dDispatcher)enterToState_:5

 

Link to comment
Share on other sites

This notification was introduced around when the VR support was added to Options. It went away for a bit thankfully but then reappeared recently. So, seems it can be fixed.

Visit the Hollo Pointe DCS World server -- an open server with a variety of COOP & H2H missions including Combined Arms. All released missions are available for free download, modification and public hosting, from my Wrecking Crew Projects site.

Link to comment
Share on other sites

  • 1 month later...

Try going to device manager, check to see if driver is properly loaded if not, manually drill down to trackir folder and install driver.

 

Worked for me.

[sIGPIC][/sIGPIC]

Primary Computer

ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5.

 

-={TAC}=-DCS Server

Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.

Link to comment
Share on other sites

  • 1 year later...
Try going to device manager, check to see if driver is properly loaded if not, manually drill down to trackir folder and install driver.

 

Worked for me.

 

A year+ later, still a regular issue. It's plugged in, it's unplugged.... it's plugged in, it's unplugged...

Link to comment
Share on other sites

  • 1 month later...

This is really starting to piss me off. It started a couple of weeks ago. How do I remove all references to TrackIR? Don't have TrackIR and this is really killing the immersion in VR.

Asus ROG C6H | AMD Ryzen 3600 @ 4.2Ghz | Gigabyte Aorus Waterforce WB 1080ti | 32Gb Crucial DDR4/3600 | 2Tb Intel NVMe drive | Samsung Odyssey+ VR | Thrustmaster Warthog | Saitek pedals | Custom geothermal cooling loop with a homemade 40' copper heat exchanger 35' in the ground

Link to comment
Share on other sites

I'm not getting it. My TIR is a bit older, I suppose.

 

Is it possible that your USB controller is beginning to fritz out?

The Hornet is best at killing things on the ground. Now, if we could just get a GAU-8 in the nose next to the AN/APG-65, a titanium tub around the pilot, and a couple of J-58 engines in the tail...

Link to comment
Share on other sites

No I got it fixed.

posted in the other thread

Asus ROG C6H | AMD Ryzen 3600 @ 4.2Ghz | Gigabyte Aorus Waterforce WB 1080ti | 32Gb Crucial DDR4/3600 | 2Tb Intel NVMe drive | Samsung Odyssey+ VR | Thrustmaster Warthog | Saitek pedals | Custom geothermal cooling loop with a homemade 40' copper heat exchanger 35' in the ground

Link to comment
Share on other sites

USB ports and drivers proves some inconsistency later. My recommendations are:

 

1. Change in BIOS the Compatibility for USB to "DISABLE". Win10 knows to handle the USB ports better this way.

2. I suspect also possible power issues with your motherboard and try to check followings:

a. check all your cables including the DisplayPort video cable and assure they are good quality and not prone to any short circuits

b. try use an powered USB hub, but be sure you have best quality hub on the market

3. Check TIR cables and eventually consider changing it completely... maybe it not make a perfect contact somewhere.

Romanian Community for DCS World

HW Specs: AMD 7900X, 64GB RAM, RTX 4090, HOTAS Virpil, MFG, CLS-E, custom

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...