VKB-SIM

Hi,

I currently have a FSM-GA, THX and SEM paired together on one controller. To get around the Elite Dangerous button limit, I want to separate the FSM-GA into its own virtual controller. What would be the be the correct course to take to do so?

Thanks

There's no gain in having only one module to act as a virtual device in E:D. Just split the whole unit, following this guide.

Thanks, I did this now, I split the FSM-GA buttons into their own virtual controller. The issue I'm having now is that Elite Dangerous registers all the GA buttons as all the preset joystick buttons (button 1 is fire, button 2 is listed as alt fire). Will I just have to remap everything, or is there an easy fix in the software?

You'll have to bind all the buttons you need in game. I suggest to start from scratch and not using their templates.

Thanks!

fallout9 wrote:You'll have to bind all the buttons you need in game. I suggest to start from scratch and not using their templates.

New issue: IN MS Flight Simulator, it detects both virtual controllers as the same name (VKBSIM NXT SEM THQ FSM.GA). This was fine, I was able to set up button profiles for each virtual controller (1 being the SEM and THQ, the other being just the GA) but now occasionally on load, it will override one of the controller's button profiles with the other. Im assuming because they both have the same name. '

Is there a way to re-name the virtual controller something separate, so that its recognized as a different name by Flight Simulator?

Don't have MSFS installed to test it, but you could remove the virtual devices feature through VKBDevCfg when playing MSFS and activate it when you play E:D.