16
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 26, 2022, 09:53:21 pm »
Hi Mark,
I also prepared oinputF1a.cmd for you to use to find out what input record is produced for what user action. So you will have to push each button in succession and report back the results like you did before. Same for moving the joystick and slider and so on. You know the drill.
Moreover I need you to attach the lsusb report. Use "lsusb -d:044f:b106 -v > 044fb106.txt" to get that.
Best regards, Wim.
Quote
Got the new USB Joystick yesterday - it is a Thrustmaster T.Flight Stick X, and seems to be a hybrid between a HOTAS Joystick, and a Game Pad, with the typical 4 buttons, Hat, Trigger mechanism and movement with the Joystick and 6 additional buttons on the base, as well as a slider control. It is programmable in addition to having pre-set settings. It is designed for use with both a PC and a PS/3 system (using a slider switch at the front). I'm still assessing the intricacies of this Joystick, and may need to do so under Windows for more detailed tests of the equipment.Nice. Let us see if we can get this to work. You did already successfully do the first necessary steps. You wrote earlier:
Quote
I've attached the edited xevents2.cmd below, if you want to see if the edits were done correctly and Best!Unfortunately line 2 was replaced whereas line 2 had to be inserted. Applies to xeventsF1.cmd too. See below.
Quote
Based on the results of the current tests with the new Joystick, you may see other changes that need to be made - scanning through the rest of the .CMD files, I thought that may be sufficient but perhaps not.Looked into xevents.log and prepared xeventsF1a.cmd and xeventsF2a.cmd to be used for now.
I also prepared oinputF1a.cmd for you to use to find out what input record is produced for what user action. So you will have to push each button in succession and report back the results like you did before. Same for moving the joystick and slider and so on. You know the drill.
Moreover I need you to attach the lsusb report. Use "lsusb -d:044f:b106 -v > 044fb106.txt" to get that.
Best regards, Wim.