Apparent Conflict between OH-58D and Virpil VPC Rotor TCS Plus with AH-64D grip

[AKA_Clutter]

Hello,

OK, this is a weird one.

I have a Virpil collective (VPC Rotor TCS Plus) with the AH-64D.

Several times when I go to fly the KW, Windows keeps dropping the VPC Rotor TCS Plus.  What I mean is that if you look at the EIN 10 Game Controller's windows, it will show, and then drop.  Sometimes it does this 2 or three times, before it goes away for good.

This only happens when I go to fly the KW.  I have not had any issues when in the Controls Setting menu.

Also, I have tried it with the following modules (about 5 minutes each) with no issues.  KA-50 III, UH-1H, AH-64D, OH-6 Mod) Mi-24P.  I also tried with the Mi-8 and had the issue once, but then tried again, and did not have this issue.  I did try going back to the OH-58D after a successful run and the same issue occurred when trying to enter the OH-58D to fly.  I also went back to the 64D after that and it did not have the issue.

The issue is fairly consistent although I was able to fly it the other day for about 15 minutes.  I have tired it about 7 times today, and it did it each time.

MSI Z690 Edge, 64 GB DDR4, i7 12700 K, RTX 380, Samsung, m.2 2TB, TM Warthog HOTAS with Virpil WarBRD base, MFG rudder pedals, Logictch mouse and Razor Tartus pad.  Running WIN 10

null

[Toge]

Not to dismiss your bug report, but just to add that this is not universal. I have the TCS Plus base with Apache grip, and have flown hours in the Kiowa without any issues.

Considering that DCS simply listens to input from Windows basically (so it shouldn't affect the controllers in any way), and that you had the problem also with the Mi-8, I'd guess you have a connection (or some other) problem on the base itself which just occurs randomly.

[Vakarian]

Can you test this connecting the TCS base to another USB port (to a different hub if it's connected there) just to eliminate the possibility of a connection slowly dying? I've been flying with TCS Plus base with Apache grip since it released and never had a disconnect or any controller related issues in KW or any other module and I have 8-10 controllers connected at all times

 

 

[AKA_Clutter]

12 hours ago, Toge said:

Not to dismiss your bug report, but just to add that this is not universal. I have the TCS Plus base with Apache grip, and have flown hours in the Kiowa without any issues.

Considering that DCS simply listens to input from Windows basically (so it shouldn't affect the controllers in any way), and that you had the problem also with the Mi-8, I'd guess you have a connection (or some other) problem on the base itself which just occurs randomly.

Any and all data is welcome. I agree one would think that it would be totally oblivious to what module was using the input, or what program was being used.  However, given that I can interact with the rotor via the control setting menu and there aren't any disconnects, that sort of argues (not conclusively) against random occurrence. 
I did some more testing today (see below) but still not convinced that it is a "hardware" Connection issue.

2 hours ago, Vakarian said:

Can you test this connecting the TCS base to another USB port (to a different hub if it's connected there) just to eliminate the possibility of a connection slowly dying? I've been flying with TCS Plus base with Apache grip since it released and never had a disconnect or any controller related issues in KW or any other module and I have 8-10 controllers connected at all times

 

 

I will certainly try that as all data will help someone figure out the issue or get in the computer HOF for weird computer problems.  And it's nice to know that someone else has a ton of USB devices.

I had an issue with the Rotor TCS Plua base a couple of years ago where it would be disconnected on startup and I had to unplug and plug it back it to get it to be recognized.  That issue has been solved for at least a year now.  The issue here is that it Windows will drop it and then pick it back up (sometimes).

--------------------------------------------------------

 

I should also noted that I first noticed this issue in early June (June 5th? June 6th) and posted a question in the Virpil Discord on June 7th.  

Testing on 6/11/2024

Version 2.9.5.55918

No disconnects while in the main menu or control menus.

Started with the Apache.  Flew for 3 - 4 minutes and got one disconnect AND reconnect. 

Flew the UH-1 next and got several disconnect/connects in a 3 minute flight.

Went to the KW and got an instant disconnect during the loading to fly screen (the others didn't do that)  Reconnected once and then stayed disconnected.

Went to menu screen and control setting screens.  VPC rotor base was connected and didn't get any disconnected.

 

Version 2.9.5.55300

Due to different reason, I have a backup copy of DCS v 2.9.5.55300, so why not give that a try.

Loaded it up and flew the Apache, UH-1 and KA-50 for about 30 minutes total.  The collective didn't disconnect ONCE.

This seems to point to an issue with the latest update.

With that said, there are at least 2 people that aren't having any issues. Wish I could be the third on that bandwagon.

Thanks for the responses.

 

 

[AKA_Clutter]

16 hours ago, Toge said:

Not to dismiss your bug report, but just to add that this is not universal. I have the TCS Plus base with Apache grip, and have flown hours in the Kiowa without any issues.

Considering that DCS simply listens to input from Windows basically (so it shouldn't affect the controllers in any way), and that you had the problem also with the Mi-8, I'd guess you have a connection (or some other) problem on the base itself which just occurs randomly.

Any and all data is welcome. I agree one would think that it would be totally oblivious to what module was using the input, or what program was being used.  However, given that I can interact with the rotor via the control setting menu and there aren't any disconnects, that sort of argues (not conclusively) against random occurrence. 
I did some more testing today (see below) but still not convinced that it is a "hardware" Connection issue.

5 hours ago, Vakarian said:

Can you test this connecting the TCS base to another USB port (to a different hub if it's connected there) just to eliminate the possibility of a connection slowly dying? I've been flying with TCS Plus base with Apache grip since it released and never had a disconnect or any controller related issues in KW or any other module and I have 8-10 controllers connected at all times

 

 

I will certainly try that as all data will help someone figure out the issue or get in the computer HOF for weird computer problems.  And it's nice to know that someone else has a ton of USB devices.

I had an issue with the Rotor TCS Plua base a couple of years ago where it would be disconnected on startup and I had to unplug and plug it back it to get it to be recognized.  That issue has been solved for at least a year now.  The issue here is that it Windows will drop it and then pick it back up (sometimes).

--------------------------------------------------------

 

I should also noted that I first noticed this issue in early June (June 5th? June 6th) and posted a question in the Virpil Discord on June 7th.  

Testing on 6/11/2024

Version 2.9.5.55918

No disconnects while in the main menu or control menus.

Started with the Apache.  Flew for 3 - 4 minutes and got one disconnect AND reconnect. 

Flew the UH-1 next and got several disconnect/connects in a 3 minute flight.

Went to the KW and got an instant disconnect during the loading to fly screen (the others didn't do that)  Reconnected once and then stayed disconnected.

Went to menu screen and control setting screens.  VPC rotor base was connected and didn't get any disconnected.

 

Version 2.9.5.55300

Due to different reason, I have a backup copy of DCS v 2.9.5.55300, so why not give that a try.

Loaded it up and flew the Apache, UH-1 and KA-50 for about 30 minutes total.  The collective didn't disconnect ONCE.

This seems to point to an issue with the latest update.

With that said, there are at least 2 people that aren't having any issues. Wish I could be the third on that bandwagon.

Thanks for the responses.


++++++++++++++++  UPDATED AS of 1700 Pacific Daylight Savings Time +++++++++++++++++++++++++++

 

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

 

 

 

[Vakarian]

Hey @AKA_Clutter glad you sorted it out. It's a good rule of thumb that if you have multiple USB peripherals and they have LED lighting in it, it's best to plug them in to a powered USB hub as the USB port by itself might get into trouble supplying power to all of those LEDs. 

Those powered USB hubs nowadays are not that expensive and they really are worth it if you have multiple devices (like we tend to here )

[AKA_Clutter]

@Vakarian

 

Thanks for the response.

Yeah, I have 3 powered USB hubs, some newer than others.

 

The AH-64D grip does have a t0one of leds, sop that might be why it wasn['t working when plugged directly into the motherboard.

 

However, I first had it plugged into a add-in board with 5 usb ports powered by a molar plug directly from the psu.  and it worked fine up until this last patch.  Makes no sense that a patch would change that.

This mystery may remain unsolved, like so many "why did it do that" mysteries.