Hello Ciaran,
I have downloaded version 0.29 and works great.
I will give a try to the 6309 option one of those days.
By the way, I own a Thrustmaster joystick connected to my PC and I have not been able to configure XRoar to work properly with it.
It has the two normal axis (X-Y) and a third one for throttle (it appears in the Windows device configuration as axis Z).
When I start the emulation, axis X is OK, but axis Y is always tied to the throttle (axis Z and inverted).
Any advice to put the right parameters?
I use these:
-joy-right 2,3:1:1 -joy-left 0,1:0:0
But with other values (that I don't remember right now) I couldn't get it work properly
Thanks in advance
Pere
pser1 wrote:
By the way, I own a Thrustmaster joystick connected to my PC and I have not been able to configure XRoar to work properly with it.
It has the two normal axis (X-Y) and a third one for throttle (it appears in the Windows device configuration as axis Z).
When I start the emulation, axis X is OK, but axis Y is always tied to the throttle (axis Z and inverted).
Any advice to put the right parameters?
I use these:
-joy-right 2,3:1:1 -joy-left 0,1:0:0
You'll need to know which axis index the proper Y axis is. If it was axis 2 instead of the default axis 1 for examine, you could do:
-joy-left 0,0:2:0
The first 0 is the joystick device number, then the colon-separated values are X-axis:Y-axis:Button.
Once started, Ctrl+Shift+J will swap left & right joystick mapping. Nowadays I'd want that to just be Ctrl+J but I allocated that to cycling through virtual joystick configurations early in XRoar's lifetime. Ho hum.
Looks like -cart-becker is ignored, for now try enabling it globally with -becker instead (they are supposed to do two subtly different things, but I screwed up the logic for one of them).
Hm substituting "-cart-becker" for "-becker" is definitely working for me under Mac OS X, so long as I have Drivewire (4) started first, and configured to listen on the "becker" interface ("Emulator or other TCP/IP" in the config wizard).
XRoar defaults to connecting to localhost (127.0.0.1) on port 65504 - can you check DW4 is listening there? Under other OSs "netstat -a" will list listening sockets, I'm sure there would be a Windows equivalent.