Trim won't work if "USB network joystick" controller is plugged out during flight!

[D4n]

Still a very annoying bug, trim wheels are moving in cockpit, but trim not working.

[Dagger71]

Still a very annoying bug, trim wheels are moving in cockpit, but trim not working.

 

Why didn’t you unplug the unused generic driver gamepad?

 

No offense Daniel but this is all on you because you forget to unplug something. ED is NOT going to be able to help you.

[Flappie]

Daniel, I may have found a solution for you: WhiteKnight allows you to associate one or several programs with your device, while all other programs won't be able to detect this device. You should give it a try.

[D4n]

ok thanks, but it's not open-source...

[Flappie]

It is, actually.

[D4n]

But that says "ViGEm / HidGuardian" and the github-commits are by "nefarius", and NOT "WhiteKnight Auto-Whitelister for HidCerberus" by "evilC"... So it seems to be something else? -.-

Edited October 3, 2020 by DanielNL

[D4n]

Also, I just had a chat with the developer of WhiteKnight, he warned me to not use WK as it can seriously break your windows installation with the tinyest user-mistake.

 

for those TLDR: ED, please fix this once and for all very soon!

[D4n]

updated trackfile attached below.

SpitfireRudderTrimNotWorking.trk

[Dagger71]

You have already been told they ate not going to fix something that they cannot fix. This is 10000% an issue with the gamepad developer. There is nothing for ED to fix.

 

 

You need to make yourself a checklist before you start DCS to ensure every is plugged in and any hW that is not need is unplugged.

 

If I fly sp in A10 i have to do the following

 

Start Track IR

Start joytokey

Start dynamic campaign

Start icontrol server

Start icontrol client on ipda

Unplug game pad

Unplug wheel and pedals

Plug in WH throttle and joystick

Plug in pedals

Start CH pedal software

 

 

And only then can i start DCS

If i forget to do any of the above, it will mess up the game and I’ll have to restart

.

Edited October 3, 2020 by Dagger71

[Dagger71]

By the way everytime you have an unrecognized controller plugged in when you run DCS you run the risk of completely corrupting the controller/config files.

 

Just unplug any controller not used in DCS, it’s just not worth it!

[D4n]

You have already been told they ate not going to fix something that they cannot fix.

By you, yes, NOT by ED. Are you a software programmer? No. See, ED can fix it until we get their master-programmer to state here that they "can't fix it". It's SO easy, all they have to do is a "is a Gamepad plugged in?"-check, and "IF yes, THEN ignore all gamepad input". EZ as 123...

[Mars Exulte]

By you, yes, NOT by ED. Are you a software programmer? No. See, ED can fix it until we get their master-programmer to state here that they "can't fix it". It's SO easy, all they have to do is a "is a Gamepad plugged in?"-check, and "IF yes, THEN ignore all gamepad input". EZ as 123...

 

Why would they automatically disregard gamepads? Btw, you seem to lack understanding on the basic backend of game controllers.

 

Whether it looks like a stick, a throttle, a gamepad, a rudder pedal, or a control panel... THEY ARE ALL THE SAME. It's a DirectX compatible, generic USB gaming device. Even my $500 VKB Gunfighter Pro, the fancy software they provide emulates buttons and axises and all kinds of fancy stuff, but on the backend, the part Windows and games actually interact with, it's ALL THE SAME. There is NO difference between one of those fancy (Foxtrot?) usb A-10 UFCs and a usb CH Fighterstick. Exactly the same.

 

Unless they create a database of every controller in existence, they usually can't even be told apart. In many games, it doesn't even identify a specific controller, it just detects a button press or axis input you can assign.

 

That said, my system consisted at one time of something like a dozen USB systems for my simpit, making all that work smoothly is my problem... but a part of that process was unplugging anything that wasn't necessary. That or leave it plugged in and make sure all the axises are wiped so it doesn't give errant commands... but preferably disconnect. If a specific device is causing hangs/crashes/not playing nice with the other devices, you unplug. Preferably followed by a trashcan, as mentioned considering the generic level game controllers function on, there is literally no excuse for a device to malfunction in that way.

[D4n]

Why would they automatically disregard gamepads?

Because (most likely) nobody in DCS flies with a gamepad, as it wouldn't make any sense on earth to fly in DCS with a GAMEPAD (instead of a joystick)

 

Unless they create a database of every controller in existence, they usually can't even be told apart.

That's the good part, DCS already detects my Speedlink Thunderstrike gamepad as a "USB network joystick" instead of detecting it (for example) as "Thrustmaster T.16000 Joystick", so ED already implemented gamepad-detection!!

[Dagger71]

Because (most likely) nobody in DCS flies with a gamepad, as it wouldn't make any sense on earth to fly in DCS with a GAMEPAD (instead of a joystick)

 

 

That's the good part, DCS already detects my Speedlink Thunderstrike gamepad as a "USB network joystick" instead of detecting it (for example) as "Thrustmaster T.16000 Joystick", so ED already implemented gamepad-detection!!

 

 

You cannot ask ED to ignore all gamepads because YOU forgot to unplug yours. That's insanity!!!

 

 

 

 

 

Also ED didn't detect anything. Windows detects USB peripherals. Your gamepad is of lower quality that uses generic drivers. There is nothing ED can do. just unplug it.

 

 

 

Remember what I said, everytime you start DCS with unrecognized device you run the risk of corrupting your config files.

[erniedaoage]

Unplug your controller or deactivate the usb device in the device manager. I have to unplug or deactivate every controller for any game that runs on unity engine just to be able to play the damn game with the gamepad. If it's to much trouble to unplug that thing everytime, invest in a proper controller with a driver.

 

There are enough people using dcs with a gamepad in some way.

Edited October 4, 2020 by erniedaoage

[Dagger71]

Unplug your controller or deactivate the usb device in the device manager. I have to unplug or deactivate every controller for any game that runs on unity engine just to be able to play the damn game with the gamepad. If it's to much trouble to unplug that thing everytime, invest in a proper controller with a driver.

 

There are enough people using dcs with a gamepad in some way.

 

 

 

 

He refuses to unplug his unrecognized controller which is using a generic driver because the manufacturer do not provide one.

 

 

 

One day, he will be posting a bug report about how is entire config library is corrupt.

[D4n]

Why do you worry about some "config library" on my PC? xD

[Dagger71]

Cause it happens all the time. It usually happens during an update and you’ve got The wrong controller plugged in , it can mess up a ton of bindings.

You are better off unplugging all non DCS controllers before starting it. What do you do when you run unity engine games? They will notoriously cause problems with the wrong controller plugged in.

[D4n]

On 8/7/2020 at 4:48 PM, DanielNL said:

Maybe not even before the game is started, but definitely before a player joins a slot to spawn.

@NineLinedid you even read this reply from me to your last post in this thread?

Unplugging the controller while flying in the air won't make the joystick trim work! Players will have to despawn from in-flight and then respawn to fix it, so a frustrating thing in multiplayer-servers with aircraft-lives systems.

 

dcs.log in this post: https://forums.eagle.ru/topic/233798-trim-wont-work-if-usb-network-joystick-controller-is-plugged-in/?tab=comments#comment-234539

 

Edited January 1, 2021 by DanielNL

[NineLine]

The solution was to unplug it before you start. I have a small hub on my desktop, it has power switches, I simple can switch something off if I don't want it to conflict, I have this issue in other games where I don't want my HOTAS interfering. This is not a DCS issue.

[D4n]

On 1/1/2021 at 10:52 PM, NineLine said:

The solution was to unplug it before you start.

Before I start flying a helicopter or YaK-52 or TF-51, yes. No issue at all in any other DCS aircraft.

 

On 1/1/2021 at 10:52 PM, NineLine said:

I have this issue in other games where I don't want my HOTAS interfering. This is not a DCS issue.

Interesting, I don't have it in any other game, that's why imo it is a DCS issue.

[Dagger71]

10 minutes ago, DanielNL said:

Interesting, I don't have it in any other game, that's why imo it is a DCS issue.

 

You should never plug or unplug a USB controller regardless of the game engine while the game is loaded and running. Always do it prior to loading  while in an options menu. 

Hotplugging USB controllers is not really supported by any sim/game that I know of.   Even if some do allow it  without causing issues, you just should not do it.

Edited January 3, 2021 by Dagger71

[D4n]

On 1/3/2021 at 3:45 AM, Dagger71 said:

You should never plug or unplug a USB controller [...] while the game is loaded and running.
Hotplugging USB controllers is not really supported by any sim/game that I know of.

DCS supports it...

 

 

Still very frustrating... Would highly appreciate a fix.

[Dagger71]

12 hours ago, D4n said:

DCS supports it...

 

 

Still very frustrating... Would highly appreciate a fix.

No they do not. Not even the manufacturer of the controller supports it since they only provided a generic usb  driver!!

Edited March 1, 2021 by Dagger71

[D4n]

17 hours ago, Dagger71 said:

No they do not.

You are aware that when unplugging any USB-controller device while in a DCS-mission makes the controller-name and an ID appear in the top right (with the "disconnect"-message), or didn't you know?? That indication clearly is a sign that DCS supports hotplugging...