Hi Wim!
Hope you are having a fine day!
Hi Martin and Mark,
I am a little bit disappointed. What you are doing is not the way to go. The "PlayStation 3 controller (USB Connected)" and the "Genius MaxFighter F-31U Vibration" are controllers not yet tested at all. Remember the method we used in the past. You need to follow the step by step approach as outlined in the "testing.txt" files that are part of the package. For the huskee device that procedure starts as follows:
Installation Instructions - Part A
==================================
A1. Ensure that USBECD.SYS has been installed.
A2. Put the following line in your CONFIG.SYS file:
(Use the proper drive and directory for your system).
DEVICE=H:\OS2\BOOT\USBECD.SYS /D:0C12:0005:0001 /N:$HUSKEE$ /V
A3. Reboot your system.
A4. Run OINPUT.CMD and watch gamepad events in hexadecimal format.
Use Ctrl+C to end this procedure.
Once this is working I would like you to do the following:
---------------------------------------------------------
A5. Run OINPUT.CMD > BUTTON.LOG and press available buttons
(one at a time, after each other, and tell me which ones)
Use Ctrl+C to end this procedure.
A6. Run OINPUT>CMD > STICK.LOG and press stick to different positions
(one at a time, after each other, and tell me what positions)
Use Ctrl+C to end this procedure.
Send me files BUTTON.LOG and STICK.LOG for me to inspect.
--------------------------------------------------------
Since you are preparing oinput.cmd yourself for these new devices, you have to prepare the corresponding testing.text accordingly. It is waste of time and effort to skip these steps.
I am currently investigating what needs to be done to provoke the "PlayStation 3 controller (USB Connected)" to send event records so step A4. can be completed succesfully.
I understand that for the "Genius MaxFighter F-31U Vibration" step A4. has been completed successfully. Why not append some of that output for me to inspect?
Best regards, Wim.
I deeply apologize as well if you feel we are jumping the gun, Wim as I consider you a friend and as that was not my intention. I am probably more to blame than Martin in this.
However, here is a perspective for consideration - as this testing is being done in a public forum, there is a lot of interest being generated, and a lot of people are watching what is happening. Since publishing the Testing Guide I have received private e-mails from others wondering if they can participate, as they feel we are actually carrying on a private conversation between ourselves, in public, and they are simply watching.
As we are also releasing the gamepad-xxxxxxxx,zip files in public, they are wanting to try these drivers for themselves and are looking for a path to do so. IOW there are a lot of potential testers out there that can help - but we need to enable them to do so.
Since the original gamepad package was released, the additional packages have not contained the original sub folders, for the equipment we started with (ie. Marttins and mine), which were actually the items that contained the testing instructions. If we want to keep this more structured, and possibly generate more data from others and their game controllers, I would propose the following:
1) Can we create a new gamepad package, with the most current drivers, and two folders - simply gamepad, and joystick, if the instructions need to be different for the two, and Include the necessary files in each to stay to the structure you specified. They should simply contain the files necessary to test the device, and generate the necessary information for you, to be posted here.
2) I will modify the Testing Guide to stay strictly to the program you specify there in testing.txt, plus the additional information that will allow them to test game controller function once an xevents file is created, that either we or they can test. I would also suggest adding some information on generating lsusb reports, and how to do that to the guide as well.
I will send the draft version of the guide to you privately first, so you can approve the testing info in it, so we can run these tests properly.
The only problem I foresee with that, Wim, is that you may be literally inundated with data from all sides, and it may overwhelm in that sense. You have already done a lot for this project, and being overwhelmed is the last thing we want, because, strangely you also have a life.
Best as always, Sir
M