Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Wim Brul

Pages: 1 [2] 3 4 ... 19
16
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 26, 2022, 09:53:21 pm »
Hi Mark,

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.

17
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 20, 2022, 11:31:52 am »
Hallo Lars,
Hi Wim,
I suspect that you mean;
rc=RxFuncAdd('SysSetPriority','RexxUtil','SysSetPriority')

???
Yes. Just found out the hard way myself this morning. Thanks.

18
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 19, 2022, 07:29:54 pm »
Hi Mark,
Quote
I 'm wondering if it may be related to USB polling rate?

Both my Corsair keyboards (one a K70 and the other a K95) are modern USB keyboards which are very good for regular applications, but are designed and engineered for gaming purposes first, where response time is important. I haven't looked up the specs yet but I suspect they may poll faster than most keyboards. As the joystick is very old and also being connected in a non standard way, does that sound plausible?

I assume running xevents and noting, right in the window on the desktop, the various responses, that would not be affected by the keyboard polling rate, but, in a DOS VDM, the keyboard may be "hijacking" control from the joystick regularly, hence the effect I'm referring to as "loss of focus".

I'm a hardware geek, but I'm not an engineer so I'm not sure how I could test that hypothesis - I'm also assuming that there is nothing that could be done with your REXX xevents program that could compensate for that (or in the device drivers?).
I tried and reproduced the "loss of focus" problem on my desktop computer. It appears that xevents.cmd needs to run at fixed high priority.

So you need to modify your xevents.cmd as follows:

1. Insert the following line just after line 1:

rc=RxFuncAdd('SysGetMessage','RexxUtil','SysSetPriority')
rc=RxFuncAdd('SysSetPriority','RexxUtil','SysSetPriority')

2. Insert the following 2 lines just before the "do forever" line
 
/* set time critical priority */
rc=SysSetPriority(3,31)

Best regards,
Wim.

19
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 10, 2022, 08:27:08 pm »
Hi Mark,

Quote
I have ordered a new solely USB based Thrustmaster Flight joystick as one was available for a good price on Amazon. As that is not a legacy joystick being run through the Logilink Gameport to USB converter I should be able to see whether the same behaviour is present with that stick or whether it is endemic to the legacy joystick only, assuming I can use the same XEVENTS.CMD file for both - please advise if not.
You cannot use the same XEVENTS.CMD for both. For starters, their idVendor, idProduct and bcdDevice  will be different. And their input report will be different too. I advice you to use LSUSB to find out that information.

Quote
When I started the mission, I was only able to access the trigger (fire) button and joystick movement - however, when the joystick lost focus again I used the keyboard to establish control again ........... and after that I was able to use the hat to look directionally, use all four buttons for various control functions as well as the flight directional control of the joystick movement.
I am puzzled. False positive? Perhaps Mode switch on Link USB 2.0 to Gameport Adapter is not working reliably? Flaky ThrustMaster, cable?

Wim.

20
Games / Re: Storing DOS VMD Sessions settings.
« on: April 10, 2022, 10:41:56 am »
Hi Martin,

I remember that there was a way to export/import DOS VDM sessions settings. There is the famous "DOSGames.set", but I don't remember (or maybe I never learned) how to use it.

What is the procedure to import/export the DOSGames.set on a DOS VDM Session?  Or did I misinterpreted it and there is no way to import/export the settings?
Yes there is, see: How to export/import Dos Settings.

Regards, Wim.

21
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 07, 2022, 05:30:26 pm »
Hi Mark,

Quote
However I am curious - did you when you entered SET HARDWARE see the first item checked - just asking as I'm trying to determine whether a joystick in DOSBOX is being seen or not.
No, I did not. When you uncheck all items and then use SAVE CONFIG then that is what you get the next time you strart TMScope. This information cannot be used to determine whether or not a joystick in DOSBOX is being seen.

Quote
xevents attached - representing a single session. By my reckoning, the session lasted about 1 minute and 34 seconds before the joystick lost focus this time and I continued moving the stick and using both buttons and hat for an additional 30 or so seconds before terminating first TMScope and then Ctrl-C to terminate XEVENTS.
Thank you for that. Unfortunately it did not help me to draw any conclusion. I have no clue what is going on. So I have 2 more questions:

1. What does "lost focus" actually mean? I think it means that how hard you try, you do not see any changes on TMScope display occurring. In other words, you first see -RAW DATA- changing, and then after a while you see -RAW DATA- not changing anymore, and that is the so called "lost focus"? Please confirm.

2. When TMScope is in the "lost focus" situation, and you switch away from that session so you can see the xevents command window, do you still see live events occurring in that window when you manipulate your joystick? I am asking because I want to pinpoint where to look next.

Cheers, Wim.


22
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 06, 2022, 09:54:34 pm »
Hi Mark,

Quote
In the DOS VDM, after using TMScope to test a few of the controls, the joystick seems to lose focus - I can push a couple of buttons, or move the joystick, or activate the hat a few times and then none of the Joystick inputs function. Using reset TMS I was able to get the controls functioning again, once, but then had to use the mouse pointer to exit the program and reenter.
I don't understand what you mean by "Using reset TMS". There is no button for that on TMScope display. What did you actually do to get the controls functioning again?

Quote
As to DOSBOX, I have got TMScope functioning and if I have a a look at the SET HARDWARE screen it reports a "Top Gun USB" joystick present, so it is seeing the joystick, but again I am unable to get DOSBOX to recognize any of the joystick inputs.
It is my understanding that the SET HARDWARE screen does not show which joystick is present. It merely shows how it has been setup. I have it currently setup as Std Joystick and 2nd Joystick. Therefore it thinks it has 2 joysticks attached to the game port and displays data accordingly.

Quote
So I don't know if the focus problem in a DOS VDM is somehow related to xevents or not. I was also curious, Wim - are all the versions of xevents.cmd in each of the folders you provided the same, or is the game pad version different from the one provided for my joystick?
Somehow you are not getting a steady stream of joystick events into e.g. TMScope. What you can do: Start xevents.cmd and run TmsScope. When you don't get input data anymore, keep using the joystick for another 30 seconds. Use Ctrl+C to cancel xevents.cmd and note the time that you did that. Append xevents.log for me to inspect. I am curious to see what happened during those 30 seconds. And no, not all versions of xevents.cmd are equal. Yours does not have the swap axis functionality. You were doing that yourself.

Happy motoring, Wim.

23
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 06, 2022, 05:56:45 pm »
Hi Lars,

How does this all relate to :
https://github.com/OS2World/DRV-USBLib/tree/master/drivers/src/usbjoy
Markus Montkowski created USBJOY.SYS (USB Joystick Client) and GENGAME.SYS (Gamedevice Manager) back in 2001 and it's source ended up in the above repository. This is yet another way to have gamepad/joystick support in our favorite operating system. It obsoletes GAMEVDD.SYS and replaces GAMEDD.SYS such that GAME$ provides enhanced fuctionality to OS/2 applications while maintaining backward compatibility. This is the good news. The bad news is that in its currend state it does not work at all.

Quote
Is the gamepad a USB device ? If yes, should we not modify those USB joystick drivers to interface with GAMEDD.SYS ? That's at least how it was solved for the USB mouse:
we have USBMOUSE.SYS and that interfaces with AMOUSE.SYS / MOUSE.SYS.
Yes, this is about USB gamepad/joystick devices. But I am not so sure what should be done. Perhaps it is better to start with cloning the currently working USBKBD.SYS into a new USBJOY.SYS rather than trying to fix that not working ancient version. And then the question arises: does it has to interface to my new GAMEDD.SYS or to GENGAME.SYS and go all that way? I think there is a lot of work involved. May be too much...

Regards, Wim.         



24
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: April 06, 2022, 11:27:51 am »
Hi Martin,
Quote
Now when I run Wolf3d and ask me to press a key, I can press the gamepad button and will continue (means the USB Gamepad is being recognized in some way by the DOS game).
When I go to the WolF3D menu and select "Jostick", it asks me to calibrate the joystick. Now the buttons works, First it ask me to press "Upper Left + Button 0", and Later "Lower Righ + Button 1", it works ,but when I finish the Joystick "yellow light" does not turn on and I keep on the same configuration loop.
I tried and reproduced your wolf3d calibration problem. You need to press select button once and then do the calibration. That will work. Apparently you became victim of xevent.cmd builtin joystick axis swap function. In hindsight I think it is better to remove that function altogether. Will do so in the future. You could use TMScope Setup Utility (thank you for finding) to see what your gamepad delivers. See tms0.png for hardware setup, tms1.png for upper-left position, tms2.png for lower-right position.

Regards, Wim.

25
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: March 29, 2022, 10:56:46 am »
Hi Mark,
Quote
2Wim - one new question - looking at the documentation in the gamedd2 package that I downloaded from Hobbes - is your version of gamedd.sys based on that package, and do the possible switches that are itemized in the .TXT file in that package apply to your gamedd.sys driver?
No, not at all. My version of gamedd.sys originates from joystick source code present in IBM Device Driver Kit (DDK) for OS/2.
Apart from modifications to interface with my new gamepad.sys device driver I had to add missing bios joystick functionality.

Wim

26
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: March 24, 2022, 05:40:30 pm »
Hi Mark,
Quote
- I am curious - do the results in xevents affect the device drivers themselves, or just monitor what is happening?
Strictly speaking, the results reported and logged by xevents.cmd reflect what it is about to write to the gamepad.sys driver. No error means success!

Quote
I suspect its the device drivers are not addressing the programs - I think usbecs is finding the joystick but it  is not passing on the info to first the native operating system, then the virtual operating system, through first the native and then the virtual device drivers. Is there someway to test that, and Best!
I don't think so. I have used JOYS_DOS.EXE from GAMEDD2.ZIP which is a DOS executable to test gamepad/joystick functionality and that works.
Perhaps the best way for you to proceed is getting DOSBOX_WOLF3D.ZIP and install that. I am able to run that DOS game over here.
For that particular game I used GAME_DIRECT_ACCESS = OFF and GAME_DIGITAL_RESPONSE = OFF settings.

Wim

27
Hardware / Re: WebCam Driver Question
« on: March 24, 2022, 12:22:02 pm »
Hallo Igor,
Hi Wim,

Thank you for your work. This version earned. The first launch was with a video stream error. The second launch was with an audio stream error - the sound looked at one repeating click to which I tried to check the microphone.
You could try various sample frequencies. For example use /a16000 or /a44100 ' dependent upon what sampling frequencies your audio drivers support.

Quote
However, from the third launch - everything worked correctly and there is sound. The fourth launch also showed excellent results.
However, the sound disappears after a few minutes of using the camera. Video - continues to work.
You told me earlier that you were using webcam.exe version "W.M.Brul:00.20210214" but that version is not the latest.
The one that I have sent you, is based on the latest version from WebCam10.zip on my website, which is "W.M.Brul:10.20220127".
So perhaps your wmaudio.exe and wmvideo.exe  are not the latest version too.
See here: UVC Webcam Server for OS/2 (ArcaOS,eComStation).

Quote
To restore audio, a restart of the receiver program (wmaudio) is required.
Right. After a restart of webcam.exe a restart of wmaudio.exe is always required.

28
Hardware / Re: WebCam Driver Question
« on: March 23, 2022, 05:08:47 pm »
Hallo Igor.
Hi Wim,

There is an assumption that the program lacks delays. Or the device cannot be immediately connected by the program. Because after initializing the device (after connecting to the connector), it does not work. When restarted, the video works, but the sound also does not connect. I assume that somewhere a waiting cycle is required or a retry of the connection is required.
You may be right about this. But I noticed that - set audio mike volume - resulted in error [00008040] which I think needs to be resolved first.
So this time I disabled that function to see if that makes a difference. Hopefully both video and audio streaming start working that way.

Wim

29
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: March 23, 2022, 04:34:16 pm »
Hi Mark.
Quote
Just one follow-up question - was the GAME$ device what was used previously in the original incarnation of GAMEDD.SYS? I ask because obviously if I can find a native OS/2 program that used the original GAMEDD.SYS to access a Joystick, I assume it should conform to your native driver as well.
Yes. The original one as in joystick.zip from IBM.

Quote
The log indicated that the joystick was identified by xevents.cmd and was generating output hex lines while I had Comanche 2 open, but it looks like nothing was being passed at all to the virtual DOS session. I will try a number of other programs, if I can get them running through the virtual DOS framework in ARCAOS, as opposed to DOSBOX, but I suspect I will achieve the same result. I would suggest that the DD driver is not passing the information we are seeing in xevents on to the operating system.
Perhaps it is necessary to swap the joystick axis in xevents.cmd. Make lines 94 thru 97 be as follows:

Ax = substr(oiBuffer,8+6,1)||x2c(00)
Ay = substr(oiBuffer,8+7,1)||x2c(00)
Bx = substr(oiBuffer,8+4,1)||x2c(00)
By = substr(oiBuffer,8+5,1)||x2c(00)

Wim

30
Hardware / Re: WebCam Driver Question
« on: March 23, 2022, 11:25:17 am »
Hallo Igor,

I think I know now where the problem is. It is in the scanning of the usb descriptors.  Please send me the "lsusb -d 09da:2695 -v" report of your camera.

Wim
Hi Wim,

See attache.
Thank you Igor. Try the attached. This patched version enables audio for your A4tech FHD 1080P PC Camera only. It should not be used with any other webcam.
 

Pages: 1 [2] 3 4 ... 19