#Racing profile in BeamNG drive
1 messages · Page 1 of 1 (latest)
hi @glass wing I found you made a BeamNG.drive setup in wooting.
I got this problem where it doesn't see the key when pressing? How did you manage to get it connected.
Hope you know what problem I am having.
i have removed the arrow keys at mine, so it is not the same code (was made at a time, there the Wooting 60 was not launched)
e57770438d96f4fefb66404063b086b5d96c
But this was at a Wooting two there are Arrow keys, as BeamNG normaly uses the Arrow key
it would be easy to change the keys to WASD, but i am unsure, if this will break the game, as control + W is the shortcut to the "Parts Selector"
so with them moved it would be
7d5d37fa9188aeea1656e9539197340681ba
as the keys already are used i would not remove them, but it could make some Problems if for example control is pressed
okay wasd is used relative often, but i think for the most, part, you could Switch Profiles, (around 10 Places, there wasd is used), i think the most likely place to make problems while driving will be the three options under "controls -> bindings -> vehicle" seen at the Picture (could also be activated with a mouse)
My problem was that it wasn't detecting. had to install the wootility and do this bit
It has the keys now. https://redacted.coolsquad.xyz/u/79qrSI.png
okay, normaly this should work with the web version too, but in the end, i am Happy to hear, that you can play now 🙂
Thank you very much to find a solution as well.
do you have analoge at that point? as the W S makes me wonder, seems like binding without
at the second code i have moved them
nah it was all about the setting of the keyboard not detecting as a xbox controller.
tbh now im unsure
but it works\
It works now, Im happy.
i would remove wasd if possible, had some issues like, i pressed for left, and for a small second, the car turned right,then both signals are send
but could never really reproduce the problems as it only happends once at many trys
Aight. Thanks, I'll check it out too.
0b0264c3c456c50805a25197d61de07b9c47 <- with activation points for wasd at the lowest point
d2ab9ab908291025a7ae83bd3b23696e57e4 <- with wasd removed