Help Please.

[J37_Spyboy]

I run IL2-GB on PC with Intel i7-7700K CPU 4.20ghz. 16.0gb RAM,  NVIDIA Geoforce GTX 1060 card with 6gb RAM. I use TrackIR. I have VKB Gladiator Pro, VKB T Rudder pedals and Thrustmaster TWCS Hotas. I use Discord and the Push to Talk button is assigned to the orange thumb button on the side of the TWCS unit. This set up  has worked well for years.

This weekend, 25/26 Feb 2 min or so into flight the rudder went to the right hand side and was unresponsive. OOPs! At the same time the Discord button didn't seem to work, I couldn't tell my wingies what was happening. It appeared that the peripherals had become corrupted, still powered but yaw, guns, discord comms all were not working.

Rebooted PC....No change

Deleted peripherals and rebooted, Problem solved...for 2min or so.

Ran AV scans, MalwareBytes, and Avira still no change. Tried to fly in RoF (yes I still have it on HD) Same problem. Rudder starts to flutter then over to RH side and ...OOps again

Using VKBDevCfg software l I flashed updated firmware and recalibrated the joystick and pedals. I deleted TrackIR and reinstalled to a previous version. All good, test flight today and Rudder shifts left after couple of minutes. TrackIR stops. When I look at keymapping curves for pitch rolland yaw there is no response from moving joystick. Yet in VKBDevCfg the hardware is working. I dont therefore think VKB products are at fault. This is a problem that has been present for over 3 weeks now and I have just about run out of ideas. Can anyone think of any potential hardware clashes that could be present. I have installed new Nvidia drivers. Running Discord as admin has solved the comms problem.

[Thad]

Salutations,

 

Sorry for your problems.

 

If I remember correctly, Windows used to needlessly reassign controller ID numbers and cause such problems. One had to tell Windows not to reassign IDs.

 

Your problems may not be that at all. I just remember this causing such problems in the past. The fact that everything works for a couple minutes seems to indicate a software change and as I suppose, it is in Windows.

 

Good luck in correcting your problem(s).

 

P.S. Have you ensured that you don't have any conflicting key mapping assignments?

Edited March 20, 2023 by Thad

[J37_Spyboy]

Hi Thad

Thanks for the prompt reply.

I think it could be Windows. I am considering a restore point although I feel it is drastic and merely a postponement. I am not aware of any conflicting assignments. I may delete and rebind all the keymapping as a possible solution.

I am not a Windows expert so it may be a long job!

Salute

[Dusty_Steppes]

Are these devices plugged into a USB hub? If so, maybe it is starting to fail.

 

You might want to check your USB device settings and make sure Windows does not manage their power settings.

Edited March 20, 2023 by Dusty_Steppes

[J37_Spyboy]

Dusty_Steppes good idea! Thank you.