investigating USB Issue with 9 or more devices connected

[Ala13_Kokakolo]

Same result, different log. Now the error is in line 52 Utils.lua.

dcs.log

Edited December 21, 2020 by Ala13_Kokakolo

[Ala13_Kokakolo]

OK. i made it work disconecting all joys. I will connect back by one to see what the conflict is.

[Flappie]

Thank you. It points to a different file this time: Utils.lua, which seems to be used for devices management (joysticks, keyboard...).

 

2020-12-21 17:09:15.182 ALERT   Dispatcher: Error starting Game GUI: [string "./Scripts/Input\Utils.lua"]:52: invalid order function for sorting

 

Here is the line from Utils.lua:

 

 

Let's try to find which devices you have in common (I don't take mice, keyboards nor TrackIR into account because other users don't have such issue):

 

Ala13_Kokakolo

2020-12-21 17:08:52.916 INFO    INPUT: Joystick created[Flight Rudder Pedals {88FFAA30-B165-11e8-8001-444553540000}], ForceFeedBack: no
2020-12-21 17:08:52.918 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {B1860A60-B211-11e8-8001-444553540000}], ForceFeedBack: no
2020-12-21 17:08:52.921 INFO    INPUT: Joystick created[Flight Throttle Quadrant {2E85E520-B15A-11e8-8007-444553540000}], ForceFeedBack: no
2020-12-21 17:08:52.932 INFO    INPUT: Joystick created[LEFT VPC MT-50 Throttle {17064ED0-49AD-11e9-8001-444553540000}], ForceFeedBack: no
2020-12-21 17:08:52.945 ERROR   INPUT: Joyctick vJoy Device {3FD19690-49B1-11e9-8002-444553540000} set spring autocenter failed!
2020-12-21 17:08:52.952 INFO    INPUT: Joystick created[vJoy Device {3FD19690-49B1-11e9-8002-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}
2020-12-21 17:08:52.953 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {B1863170-B211-11e8-8002-444553540000}], ForceFeedBack: no

 

Mustang25

2020-12-19 16:34:59.123 INFO    INPUT: Joystick created[Joystick V2.04 {DC018910-97BE-11ea-8001-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.128 INFO    INPUT: Joystick created[LEFT VPC Throttle MT-50 CM {3217F4C0-F9AD-11e9-8001-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.132 ERROR   INPUT: Joyctick vJoy Device {C0B90D70-F04A-11e9-8002-444553540000} set spring autocenter failed!
2020-12-19 16:34:59.138 INFO    INPUT: Joystick created[vJoy Device {C0B90D70-F04A-11e9-8002-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}
2020-12-19 16:34:59.140 INFO    INPUT: Joystick created[LEFT VPC Throttle MT-50 CM {81F813F0-F9B0-11e9-8002-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.141 INFO    INPUT: Joystick created[LEFT VPC Throttle MT-50 CM {81F83B00-F9B0-11e9-8003-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.141 INFO    INPUT: Joystick created[DSD Flight Series Button Controller {68C4F450-91CE-11ea-8001-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.142 INFO    INPUT: Joystick created[RIGHT VPC Stick MT-50CM {0E983F40-654C-11ea-8001-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.143 INFO    INPUT: Joystick created[Button Box Interface {CB9A0980-7A9F-11ea-8002-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.147 INFO    INPUT: Joystick created[FSSB R3L MJF SGRH {C50D81A0-9ABB-11ea-8002-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.152 INFO    INPUT: Joystick created[MFG Crosswind V2 {C2DD8CE0-E2DD-11e9-8008-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.154 INFO    INPUT: Joystick created[FSSB R3L MJF SGRH {C50DCFC0-9ABB-11ea-8003-444553540000}], ForceFeedBack: no
2020-12-19 16:34:59.159 INFO    INPUT: Joystick created[RIGHT Collective Helicopter {B478B850-E3A9-11ea-8001-444553540000}], ForceFeedBack: no

 

Ornithopter

2020-12-19 02:34:04.015 INFO    INPUT: Joystick created[MFG Crosswind V2 {8CAAE710-EFAD-11e6-8001-444553540000}], ForceFeedBack: no
2020-12-19 02:34:04.017 INFO    INPUT: Joystick created[Saitek Pro Flight Throttle Quadrant {B3B4AAE0-EFC0-11e6-8001-444553540000}], ForceFeedBack: no
2020-12-19 02:34:04.018 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {9DCAEF20-EFAA-11e6-8005-444553540000}], ForceFeedBack: no
2020-12-19 02:34:04.019 INFO    INPUT: Joystick created[CH Throttle Quadrant USB {E3CB8A10-F03C-11e6-8003-444553540000}], ForceFeedBack: no
2020-12-19 02:34:04.059 INFO    INPUT: Joystick created[Saitek Pro Flight Throttle Quadrant {84479800-F03B-11e6-8002-444553540000}], ForceFeedBack: no
2020-12-19 02:34:04.061 INFO    INPUT: Joystick created[CCP Controller {FE12A3D0-6964-11e7-8004-444553540000}], ForceFeedBack: no
2020-12-19 02:34:04.068 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {9DCAEF20-EFAA-11e6-8006-444553540000}], ForceFeedBack: no

 

It could be caused by "vJoy", although Ornithopter has a different name, "CCP Cotroller". Does it come from vJoy as well?

[Ala13_Kokakolo]

Ok, after disconecting all my devices, the "culprit" is the warthog throttle

 

[Flappie]

Let's wait for Mustang and Ornithopter's feedbacks.

[Ala13_Kokakolo]

I have launched the DCS with the Warthog joy disconected: It worked. I then conected the joy and it works! I could even launched the target software.

 

 

Edited December 21, 2020 by Ala13_Kokakolo

[Flappie]

Great. Thank you for your feeedback. That's a weird bug. Don't forget to cancel modifications in MissionEditor.lua.

[Ornithopter]

CCP stands for Custom Control Panel, and it is an Ipad App that creates a virtual touchscreen controller for the PC.  In the meantime, I'll see what happens when I start disconnecting things.

[Ala13_Kokakolo]

Once i did the steps explained above (run the game with the throttle disconected and connect it once in the game) it has fixed itself.  

[Ornithopter]

Ok, so I've done like everyone else and started disconnecting and re-plugging controllers.  Succesful load!  What I'm seeing here is that there appears to now be a hard limit on the number of controller devices.  More than 6 devices appears to be the problem.  On my end, it doesn't matter which controllers are connected, even the virtual device, just that 7 or more will cause it to hang at the loading screen.  

 

Great job, Flappie, and everyone else zeroing in on things like this!  Should we just wait for a hotfix now?

Edited December 21, 2020 by Ornithopter

[Flappie]

7 minutes ago, Ornithopter said:

More than 6 devices appears to be the problem.

Maybe "more than 9", because you also have a keyboard, a mouse ad a TrackIR.

I'm glad you can at last launch the game.

 

Don't forget to cancel modifications to MissionEditor.lua.

 

Once we have Mustang25's feedback (he has 16 different devices!), I'll warn BIGNEWY about this issue.

Edited December 21, 2020 by Flappie

[Flappie]

I see. And did you have to unplug some devices to make DCS work again, like Ornithopter and Kokakolo did?

[Flappie]

OK, thanks for your feedback.

[SouthernChap]

Just to throw my hat into the ring, I had exactly the same issues and here are my 'debugging' steps

 

Here's my log (I'd previously commented out the section in missioneditor.lua so got to the error)

 

My Virpil throttle is split into 3 virtual devices due to Elite Dangerous (yeah, thanks Frontier for using a version of the DirectInput API that wasn't even current when you started your kickstarter) so that adds to the number of devices. 

 

So in total (not including mouse and keyboard) I have 9 devices.

 

When I 'unsplit' the throttle (thus the throttle would be just the 1 device, rather than 3 devices) to see what would happen, I was able to get to the DCS main GUI.  

 

However, when I split it back into 3 devices again, I was still able to get in to DCS.

 

I then noticed I'd left my Virpil (3 axis) pedals unplugged (the Virpil software only likes configuring 1 Virpil device at a time) so I then plugged the pedals back in.

 

I restarted DCS and got the original problem.

 

So I unplugged my Azeron keypad as it seems to want to be 3 devices too for some reason (dunno why, it's built around a teensy controller board I think) thinking that if 1 device (the pedals) would push me over a limit then unplugging the Azeron, it being 3 devices would get me back under with the pedals plugged in.

 

But to my surprise, no joy.

 

Then I thought, "maybe it's total number of axes?".  So I unplugged my DIY button box (based off a Leo Bodnar board) that has 6 axes.  If the three axes on the pedals pushed it over, removing the 6 axes on the button box should get it back under yeah?

 

Nope.

 

I did also unplug my Gunfighter too for completeness but that had no effect.

 

So, if I remove either my Virpil pedals or ensure my Virpil throttle is just one unified device (not problem with DCS since it nicely respects the 128 button/8 axis DirectInput/RawInput limit) then all is fine. 

 

If I either have my Virpil pedals plugged in or have my Virpil throttle split into three virtual devices I get the error in utils.lua

 

Eh, I'm only a humble C#/Java programmer and this is beyond my wits to offer conclusions, so I'll let you clever chaps sort it out! ;)

dcs.log

[ZombiZarre]

Same problem after changing USB ports for my stick and throttle.

Unplugging worked but same problem on the following launch.

 

I had to plug it while the game was launched and remap some commands in the commands menu.

 

I don't have the log related but in my most recent one I noticed that I only have 4 inputs : 2 for sound and 2 for control (joystick and throttle). I'm only counting the devices with UID displayed in the log.

 

So maybe it's an UID related issue?

 

[JimC]

Have narrowed down my hanging at 100% issue to my number of controllers too.

Have Winwing HOTAS (3 x USBs) Logitech Rudder Pedals (1 x USBs) all connected to M/board. 

IR Track (1 x USBs) Headphones (1 x USBs) connected to M/board headers front of case.

Also I have a 5 port USB card on M/board, this has Logitech Throttles x 4 (4 x USBs).

 

So before the latest stable update, all was good, then after update it restarted and hung on 100%.

So Flappie (cheers mate) advised removing controllers and restarting which got it going, but as I added controllers I got to number 8 USB and that's when the hang at 100% came back.

I tried various combinations to make sure that no devices were the problem, and always at that number 8 USB it hangs. Have checked device manager etc but all is working and going fine with IL2 BoX, IL2 CoD, RoF. A bit frustrating but I hope the team would please look at this. Hope I'm not the only one.

And if anyone out there is running 8-10 devices and all is ok for you, any thoughts ?

 

Thanks Flappie, this at least cracked what the problem is. Hope it helps. 

[Flappie]

You're welcome, Jim. The yellow "Investigating" label next to the thread title indicates ED crew is already on it.

[Baldrick33]

In my case it isn't the number of devices but specifically the Warthog Throttle. I have a lot of devices connected and I normally leave my sim racing stuff on as well as DCS never seems to worry about it (I have removed any default control settings for them)

 

The first log file loads with success with everything turned on except the Warthog Throttle

 

2021-01-10 18:46:51.303 INFO    INPUT: Device [Keyboard] created deviceId = -1
2021-01-10 18:46:51.311 INFO    INPUT: Device [TPR T.Pendular Rudder {6603B770-40FB-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.311 INFO    INPUT: Joystick created[TPR T.Pendular Rudder {6603B770-40FB-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.322 INFO    INPUT: Device [Arduino Micro {42D97A40-DDEC-11e9-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.322 INFO    INPUT: Joystick created[Arduino Micro {42D97A40-DDEC-11e9-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.330 INFO    INPUT: Device [F16 MFD 1 {4065F5A0-36F6-11ea-8002-444553540000}] created deviceId = -1
2021-01-10 18:46:51.330 INFO    INPUT: Joystick created[F16 MFD 1 {4065F5A0-36F6-11ea-8002-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.331 INFO    INPUT: Device [F16 MFD 2 {37E2DA10-36F6-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.331 INFO    INPUT: Joystick created[F16 MFD 2 {37E2DA10-36F6-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.334 INFO    INPUT: Device [Arduino Micro {B98437C0-1FF5-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.334 INFO    INPUT: Joystick created[Arduino Micro {B98437C0-1FF5-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.335 INFO    INPUT: Device [Joystick - HOTAS Warthog {55603120-BB61-11e9-8010-444553540000}] created deviceId = -1
2021-01-10 18:46:51.335 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {55603120-BB61-11e9-8010-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.350 INFO    INPUT: Device [HE Sim Pedals V2 {555F1FB0-BB61-11e9-8005-444553540000}] created deviceId = -1
2021-01-10 18:46:51.350 INFO    INPUT: Joystick created[HE Sim Pedals V2 {555F1FB0-BB61-11e9-8005-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.351 INFO    INPUT: Device [Arduino Micro {C152B650-32EE-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.351 INFO    INPUT: Joystick created[Arduino Micro {C152B650-32EE-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.353 INFO    INPUT: Device [Pro-Race {412AD7D0-BAC2-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.353 INFO    INPUT: Joystick created[Pro-Race {412AD7D0-BAC2-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.363 INFO    INPUT: Device [Flight Throttle Quadrant {3D161CB0-5AF8-11ea-8005-444553540000}] created deviceId = -1
2021-01-10 18:46:51.363 INFO    INPUT: Joystick created[Flight Throttle Quadrant {3D161CB0-5AF8-11ea-8005-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.368 INFO    INPUT: Device [SymProjects JC32 {555FE300-BB61-11e9-800C-444553540000}] created deviceId = -1
2021-01-10 18:46:51.368 INFO    INPUT: Joystick created[SymProjects JC32 {555FE300-BB61-11e9-800C-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.369 INFO    INPUT: Device [Martin Ascher Racing Wheel {555FE300-BB61-11e9-800D-444553540000}] created deviceId = -1
2021-01-10 18:46:51.369 INFO    INPUT: Joystick created[Martin Ascher Racing Wheel {555FE300-BB61-11e9-800D-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.369 INFO    INPUT: Device [Flight Throttle Quadrant {8DC6F2A0-646D-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.369 INFO    INPUT: Joystick created[Flight Throttle Quadrant {8DC6F2A0-646D-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:46:51.370 INFO    INPUT: Device [Arduino Micro {C7514800-588C-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:46:51.370 INFO    INPUT: Joystick created[Arduino Micro {C7514800-588C-11ea-8001-444553540000}], ForceFeedBack: no

 

The second fails to load with my sim racing stuff turned off but Throttle turned on - so less devices but fails with Throttle connected. It gives the error:

Dispatcher: Error starting Game GUI: [string "./MissionEditor/MissionEditor.lua"]:86: invalid order function for sorting

 

2021-01-10 18:38:47.887 INFO    INPUT: Device [Keyboard] created deviceId = -1
2021-01-10 18:38:47.896 INFO    INPUT: Device [TPR T.Pendular Rudder {6603B770-40FB-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.896 INFO    INPUT: Joystick created[TPR T.Pendular Rudder {6603B770-40FB-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.906 INFO    INPUT: Device [Arduino Micro {42D97A40-DDEC-11e9-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.906 INFO    INPUT: Joystick created[Arduino Micro {42D97A40-DDEC-11e9-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.914 INFO    INPUT: Device [F16 MFD 1 {4065F5A0-36F6-11ea-8002-444553540000}] created deviceId = -1
2021-01-10 18:38:47.914 INFO    INPUT: Joystick created[F16 MFD 1 {4065F5A0-36F6-11ea-8002-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.915 INFO    INPUT: Device [F16 MFD 2 {37E2DA10-36F6-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.915 INFO    INPUT: Joystick created[F16 MFD 2 {37E2DA10-36F6-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.917 INFO    INPUT: Device [Arduino Micro {B98437C0-1FF5-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.917 INFO    INPUT: Joystick created[Arduino Micro {B98437C0-1FF5-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.918 INFO    INPUT: Device [Joystick - HOTAS Warthog {55603120-BB61-11e9-8010-444553540000}] created deviceId = -1
2021-01-10 18:38:47.918 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {55603120-BB61-11e9-8010-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.934 INFO    INPUT: Device [Arduino Micro {C152B650-32EE-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.934 INFO    INPUT: Joystick created[Arduino Micro {C152B650-32EE-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.946 INFO    INPUT: Device [Flight Throttle Quadrant {3D161CB0-5AF8-11ea-8005-444553540000}] created deviceId = -1
2021-01-10 18:38:47.946 INFO    INPUT: Joystick created[Flight Throttle Quadrant {3D161CB0-5AF8-11ea-8005-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.950 INFO    INPUT: Device [SymProjects JC32 {555FE300-BB61-11e9-800C-444553540000}] created deviceId = -1
2021-01-10 18:38:47.950 INFO    INPUT: Joystick created[SymProjects JC32 {555FE300-BB61-11e9-800C-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.951 INFO    INPUT: Device [Flight Throttle Quadrant {8DC6F2A0-646D-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.951 INFO    INPUT: Joystick created[Flight Throttle Quadrant {8DC6F2A0-646D-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.952 INFO    INPUT: Device [Arduino Micro {C7514800-588C-11ea-8001-444553540000}] created deviceId = -1
2021-01-10 18:38:47.952 INFO    INPUT: Joystick created[Arduino Micro {C7514800-588C-11ea-8001-444553540000}], ForceFeedBack: no
2021-01-10 18:38:47.974 INFO    INPUT: Device [Throttle - HOTAS Warthog {555F46C0-BB61-11e9-8007-444553540000}] created deviceId = -1
2021-01-10 18:38:47.974 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {555F46C0-BB61-11e9-8007-444553540000}], ForceFeedBack: no

 

It does seem intermittent though, it worked fine earlier today with nothing changed control wise.

 

I first noticed it a week or so ago when I had a CH Flightstick connected. I disconnected that and cured it for a while, now the Warthog Throttle is the issue

 

 

Edited January 10, 2021 by Baldrick33
spelling!

[SouthernChap]

Yep Baldrick33 has it right.  It doesn't seem to be the number of HIDs or the number of axes or even the number of bindable button (my Virpil pedals only have axes of course) but something about the devices themselves; or rather something about the specific instance of the device and how it's configured.

[JimC]

Just interested in a fix, no flying for over a week very frustrating.

 

[Baldrick33]

31 minutes ago, JimC said:

Just interested in a fix, no flying for over a week very frustrating.

 

It works for me if I unplug the offending device (TM Warthog Throttle in my case) and plug it back in once DCS has loaded. Fortunately it is plugged into a USB hub with individual switches!

[JimC]

Hey Baldrick, glad you got a work around mate, but when I do that it wipes all text off the Devices settings page, everything from the Commands to Keyboard Commands and Device Settings columns are totally empty, weird, and I have to set set up again, then next start up same thing. Not doing that everytime, I have a few modules so it is a real pain.

For me it is number of devices, as I can run them all fine in various combos but not all at once, only 9 devices are working. When i add the 10th device back in the mix it hangs on the loading screen again.

Honestly was working fine before the last stable version update, and I'm not beating up DCS either I understand these things happen, just can't find exactly what has changed to move towards a fix. 

Am going to try the autoexec.cfg file as I'm starting back with a totally clean install, will post back with result.

Will try without IR Track too but as a separate test so as not to muddy the waters. Though they are pretty murky at the moment lol.

 

[Baldrick33]

Yeh, don’t think I would wish to remap all my controls each time!
 

To add to the murkiness when it stops working in vr I can load DCS to monitor, then it stops working altogether. I have lost count of the number of repairs and reloading video drivers I have done before finding this thread. The odd thing is I was convinced one of them fixed it as it started working again with all input devices connected for a while before going through the same process all over again!

[Baldrick33]

The plot thickens.

 

Now if I enable the Warthog throttle with DCS loaded, the control sections completely blanks out. No grid, no controls, no option buttons, nothing.

 

If I enter an aircraft and press Esc and Adjust Controls nothing is displayed plus the throttle is not working.

 

If I disconnect the throttle then the controls options come back.

 

The only thing I have done is to restart my PC since my previous post.

[Baldrick33]

Some more playing around with this.

 

Warthog plugged into:

 

Non powered USB Hub with individual switches - doesn't work at all. Can only start DCS with Throttle USB switch off. Switch it on but get blank controls screen and throttle doesn't respond in aircraft

 

Replaced USB Hub with non powered one without individual switches - Can only start DCS with Throttle USB switch off. Plug it in and it works

 

Plugged Throttle into a powered USB Hub - works fine, can start DCS with it plugged in.

 

So in my case it seems to be narrowed down to which USB hub the Warthog Throttle is plugged into. Will see if that is still the case after the PC is restarted