Has anybody got to use the SpaceMouse as a joystick with car simulators such as "City Car Driving" or "Euro Truck"?
I've tried by installing sx2vjoy and selecting vjoy on the game as input, this program detects when I move the buttons but the game doesn't work wit the Spacemouse.
I have also tried creating a Sarter.xml file with this section. (the executable is called Starer.exe)
I don't know what sx2vjoy expects, but if you want the SpaceMouse to output joystick events, you have to tell the driver to do this.
See 3DxWinCore64/Cfg/JoystickTemplate.xml. Each 3D mouse axis is mapped to a 2D joystick axis.
jwick wrote: ↑Mon Feb 25, 2019 1:32 am
I don't know what sx2vjoy expects, but if you want the SpaceMouse to output joystick events, you have to tell the driver to do this.
See 3DxWinCore64/Cfg/JoystickTemplate.xml. Each 3D mouse axis is mapped to a 2D joystick axis.
How I force the SpaceMouse to use that profile for all programs?
Doing that for all apps is a little harsh.
You can put those assignments into the global cfg, or do a Grab in a game cfg.
If you want to use the 3D mouse in another programs, create a single "game/joystick" cfg and put all the ExecutableNames for your games in it. The driver will use that cfg for those programs but still switch to other cfgs as other applications come in focus.
BUT, why are you running our software? It looks to me (quick read of some FAQ on some forum linked to by the sx2vjoy GitHub page) that it reads our devices directly using a native API (that's the way I would do it). If that is the case, you don't need our software running. There is no point in having our driver convert to Joystick events, and also have sx2vjoy do the same conversion. I'd think they would get in each others way.
If you want to use the 3D mouse in 3Dx-supported apps AND with sx2vjoy that's a different story. You have to tell the driver when to get out of sx2vjoy's way.
jwick wrote: ↑Mon Feb 25, 2019 9:38 am
Doing that for all apps is a little harsh.
You can put those assignments into the global cfg, or do a Grab in a game cfg.
If you want to use the 3D mouse in another programs, create a single "game/joystick" cfg and put all the ExecutableNames for your games in it. The driver will use that cfg for those programs but still switch to other cfgs as other applications come in focus.
BUT, why are you running our software? It looks to me (quick read of some FAQ on some forum linked to by the sx2vjoy GitHub page) that it reads our devices directly using a native API (that's the way I would do it). If that is the case, you don't need our software running. There is no point in having our driver convert to Joystick events, and also have sx2vjoy do the same conversion. I'd think they would get in each others way.
If you want to use the 3D mouse in 3Dx-supported apps AND with sx2vjoy that's a different story. You have to tell the driver when to get out of sx2vjoy's way.
I have no idea. I read that was the proper way.
I want to use my SpaceMouse as a joystick with a car simulator.
How do I need to proceed then?
What name should my cfg file have?