Joystick and Throttle cannot be mapped with Oculus Touch

[rmndz]

Everything is working fine up until it is time to map the Oculus Touch controllers. The game does not detect the Joystick and Throttle axis outside the edit mode so This makes it impossible to input anything because I cannot even grab the Joystick or Throttle.

I have tried everything, not sure what to do.

[dantman]

I'm not clear on what you're saying is not working.

• In edit mode are you able to grab buttons/controls/panels and move them around?
• Using edit mode+menu mode if you select an axis and then press one of the -/+ buttons on the edit panel, does Elite Dangerous hear it and make it a binding?
• Likewise can you bind the POV buttons to button controls?
• Outside of edit mode do the joystick/throttle not respond when grabbed, or is it just that you cannot see them? If the latter have you disabled menu mode? If you have and are inside the cockpit of your ship could you screenshot the overlay's desktop view and post it here.

[rmndz]

Hello Daniel

Thank you for your quick response. I am able to grab buttons/controls/panels and move them around in edit mode as well as in Menu.

Elite Dangerous does not hear and make it a binding. Outside of edit mode (inside of the cockpit) I cant see the joystick/throttle even though I set them up in edit mode and I can see them clear as day in edit mode.

I will try to send a screenshot later today

[dantman]

Have you moved your Saved Games folder to a different drive? If so try 0.7.0, that's a recently fixed bug.

[dafaithz81]

Hi, ive exactly the same problem. Im using the latest versions of vjoy and vr cockpit. I can see the virtual joystick and the throttle, but i cannot bind them. Even when im using the edit+menu mode, i cannot bind any axis.

Edit: I dont have a clue why its not working, tested everything now... Im using a oculus quest with link, so i got touch controllers. The VR cockpit window gives no errors, it connects to the 2 vjoy devices, finds the elite dangerous instance and is ready to rock. In game within a training mission, i can see the throttle and the virtual stick. I can move other icons around and can push them. When i try to bind the yaw axis nothing happens, i tried to grab the stick to get a bind and i tried to use menu+edit to click on +1 or -1 yaw, it dont react. So i downgraded to vjoy 2.18, switched the vjoyinterface.dll from the vr cockpit, still doesnt work. I closed the VR cockpit, started the vjoy feeder and configured an axis input. After that i switched back to elite dangerous to bind the yaw axis and still nothing. Its like the communication between vjoy and elite dangerous doesnt work. What could this be ?

Edit2: I opened the vjoy monitor tool to look whats coming in. So ive started elite dangerous and the vr cockpit, grabbed the virtual stick and the monitor tool displayed correctly all axis. Why the heck wont elite dangerous recognize the vjoy inputs ?

Edit3: Its working now, after ive reinstalled windows.

[ShiftTGC]

I am unsure about the other two here, but I have a problem fitting the title.

Lets go over it, step by step.

I use an Oculus Rift. I run in Windows 7 compatibility mode on a Windows 10 machine. I use vJoy product version v4.0.1 and (JoyMonitor) file version 4.0.1.7.

What works: Buttons you can add to the cockpit. I can successfully move the application menu and interact with them. They successfully (for example) tell my ship to boost or put down the landing gears.

What does **not work: Virtual HOTAS. Now, when I attempt to add my throttle to Elite Dangerous, do Elite Dangerous not pick it up. However, vJoy monitoring program does. So there seem like there is something that makes the application or vJoy not interacting with Elite Dangerous (64-bit Windows 7 compatibility mode) Correction: Nothing on the "menu editing" panel for adding throttle control or the POV1 & POV2 doesn't interact with Elite Dangerous. (When hovering over the POV1 & 2 buttons, do they change colour tho, so it gets detected by E-VR-C. And vJoy.

[Hokage3211]

Same issue in terms of throttle and joystick not working, but everything else completely functional. Using index controllers and vive (actually pimax) headset.

[Hokage3211]

Promising update that may explain why the re-installing worked for that one guy; Setting the "support generic gamepad" option in steam to NOT be ticked, made my vJoy work to send the controls to ED. Generic gamepad support is turned off by default in steam, so reinstalling windows (and therefore steam) would appear to "fix" the issue. In case this jogs anyone's memory of this setting, this is that one setting you can only access via bigscreen and stuff, hopefully this helps!