Keyboard Not Working

[Caps Lock]

Just recently my keyboard and streamdecks and one other additional button box are not being recognized by 

DCS. They work fine in windows though. I've been messing around with the graphics settings a little bit with the new multithreading but I cant see how that would have any effect on that issue. Does anyone have any ideas about what might be the problem?

TIA

[Rudel_chw]

Attach your dcs.log file, to gather more clues about this issue.

[Caps Lock]

Thanks for the reply Rudel_chw

I have attached the log files below.

Logs.zip

[Rudel_chw]

On 11/8/2023 at 3:01 AM, Caps Lock said:

my keyboard and streamdecks and one other additional button box are not being recognized by 

DCS

 

Hi,

On your log the keyboard seems to be recognized by DCS, but I don't see your stream decks. The devices DCS is recognizing are these:

 

INPUT: Device [Keyboard] created.
INPUT: Device [VPC Rudder Pedals {445E71D0-9001-11ec-8001-444553540000}] created.
INPUT: Joystick created[VPC Rudder Pedals {445E71D0-9001-11ec-8001-444553540000}], ForceFeedBack: no
INPUT: Device [Joystick (Razer Tartarus V2) {2B8DC4D0-E69C-11eb-8002-444553540000}] created.
INPUT: Joystick created[Joystick (Razer Tartarus V2) {2B8DC4D0-E69C-11eb-8002-444553540000}], ForceFeedBack: no
INPUT: Device [Throttle - HOTAS Warthog {393FC3D0-7A08-11ec-8002-444553540000}] created.
INPUT: Joystick created[Throttle - HOTAS Warthog {393FC3D0-7A08-11ec-8002-444553540000}], ForceFeedBack: no
INPUT: Device [LEFT VPC Rotor TCS PLUS {9F0F2130-9013-11ec-800C-444553540000}] created.
INPUT: Joystick created[LEFT VPC Rotor TCS PLUS {9F0F2130-9013-11ec-800C-444553540000}], ForceFeedBack: no
INPUT: Device [Joystick - HOTAS Warthog {0043C090-7A08-11ec-8001-444553540000}] created.
INPUT: Joystick created[Joystick - HOTAS Warthog {0043C090-7A08-11ec-8001-444553540000}], ForceFeedBack: no
INPUT: Device [Mouse] created.
INPUT: Device [TrackIR] created.
 

I don't know what may be causing DCS to not see the other devices, and you dont seem to have any user Mods on your setup. Maybe you should try to open a support ticket with ED.

[Caps Lock]

I figured it out. I was following some youtube tutorials about graphic settings and one user suggested running DCS as an admin to boost performance. For some reason by doing this it didn't allow DCS to work with the steam decks. When I went back and unselected "run as admin" it worked again. Not sure why, but it does.

Just out of curiosity if anyone can explain why this is so I'd love to learn why. Thanks again.

[Flappie]

Thanks for your feedback.

Never run an app as admin, unless you're doing an administrator task.

[silverdevil]

9 minutes ago, Caps Lock said:

I figured it out. I was following some youtube tutorials about graphic settings and one user suggested running DCS as an admin to boost performance. For some reason by doing this it didn't allow DCS to work with the steam decks. When I went back and unselected "run as admin" it worked again. Not sure why, but it does.

Just out of curiosity if anyone can explain why this is so I'd love to learn why. Thanks again.

hello. this is not an explanation but another facet of the same issue. it depends on how the app is setup to use APPDATA. we have some old programs to install at my office and when it is run as admin, each time the normal user uses the app, it has to be configured again. we have to make the normal user an admin, install the app and then remove the user from the admin group.

so i am surmising that the stream deck install puts the config data on whatever user's appdata you used as the admin.

https://learn.microsoft.com/en-us/answers/questions/794169/installer-access-to-appdata