AKA_Clutter Posted June 11, 2024 Posted June 11, 2024 Hi, I original started this topic in the OH-58D Bugs and Issues channel, but after more testing today, it doens't appear only in the OH-58D. Bottom line is that Windows sees the device while I am in the main menu or in the control setting menu. When I go to fly, Widnows drops the device and then reconnects it (sometimes. Based on the two response to the other thread, at least two other people do NOT have this issue. I did verify that this issue is present in DCS V2.9.5.55918. This issue is NOT present in DCS v2.9.5.55300 Not sure if I should post here or in DCS bugs and issue channel. The full listing of the issue and testing done to date can be found at: Thanks for anyy and all help. ---------------- AKA_Clutter Win 10 Pro, Intel i7 12700k @4.6 GHz, EVGA RTX 3080 FTW, Ultra 64 GB G.Skill DDR4 3600 RAM, Acer 27" flat screen, HP Reverb G2, TM Warthog HOTAS with Virpil warBRD base, MFG Rudder Pedals, Virpil TCS Rotor Base with AH-64Dcollective, TrackIR 5 Pro w/Vector Expansion, PointCTRL.
AKA_Clutter Posted June 12, 2024 Author Posted June 12, 2024 OK< problem solved, sort of. At the suggestion of another user, I moved the TCS Rotor to a different USB port. I tried two ports on the motherboard first, and both times, the Grip would light up for 5 -10 seconds and then go dark. As far as I could tell it was never recognized. One of the ports OI tried was the port that my WarBRD base is plugged into. I t6hen plugged it into a powered USB 3.0 hum and then plugged it into one of the above motherboard ports. The TCS rotor was recognized and I just completed a 30 minute flight with no drops. Any clue as to why any of this happened, or why it makes sense (besides, that's computers for you). 1 ---------------- AKA_Clutter Win 10 Pro, Intel i7 12700k @4.6 GHz, EVGA RTX 3080 FTW, Ultra 64 GB G.Skill DDR4 3600 RAM, Acer 27" flat screen, HP Reverb G2, TM Warthog HOTAS with Virpil warBRD base, MFG Rudder Pedals, Virpil TCS Rotor Base with AH-64Dcollective, TrackIR 5 Pro w/Vector Expansion, PointCTRL.
Wostg Posted June 12, 2024 Posted June 12, 2024 I have the non-twisty rotor base with the ka50 grip, and it occassionally drops power or goes a bit odd until I pull the plug behind it in and out. I have both plugs (it is the one with the red extra usb right) in a powered hub, and have spent a long time making sure there's no twists or squeezes in the cables. So guessing its either a power supply thing or a design issue, but who knows. Assuming red is power supply I might try extending the black cable into the back of the pc directly and see if that solves whatever conflict may be happeneing. I can think of nothing heavier than an airplane I can think of no greater conglomerate of steel and metal I can think of nothing less likely to fly
AKA_Clutter Posted June 12, 2024 Author Posted June 12, 2024 @Wostg I had s similar issue with mine. It would be OK for a few months, and then not be recognized by Windows. I would have to unplug the device at the back and then plug it back it. It would work OOK for a few more months and then repeat the behavior. I finally worked with Virpil support and after a LOT of testing and sever months (due to the fact that it only occurred every few months) I think the problem has been solved. IIRC ultimately, I had to go inside the device, flip the USB and AUX connected at the back of the base, and switch the internal connectors. It has been working fine form about a year and a half. The "red" connector is not for power, but for connecting an auxiliary panel IIRC. Thanks for the response. 1 ---------------- AKA_Clutter Win 10 Pro, Intel i7 12700k @4.6 GHz, EVGA RTX 3080 FTW, Ultra 64 GB G.Skill DDR4 3600 RAM, Acer 27" flat screen, HP Reverb G2, TM Warthog HOTAS with Virpil warBRD base, MFG Rudder Pedals, Virpil TCS Rotor Base with AH-64Dcollective, TrackIR 5 Pro w/Vector Expansion, PointCTRL.
Recommended Posts