Scroll back to
post 16

I know about it, but did that fix the waitandhid utility? AFAIK that one had the same issue as the plugin.

It does work in waitandhid.

It wasn't clear the posts that the 3D stick support fixed Kazuki's gamepad. He didn't confirm it either, so I thought this was just a missing feature, rather the solution to his problem. I'll add the 3D stick support to the plugin later, but be aware that I can't test it myself at the moment.

Quote:

Seems that jacadcaps bought the Manta game pad that Solo Kazuki has, but it was dead on arrival, and when they sent him a replacement, it was a different pad from a different manufacturer, so jacadcaps can't test anything for Solo Kazuki. Solo Kazuki just needs to get rid of the faulty game pad, or buy a 2nd game pad for MorphOS use, IMHO. jacadcaps can speak for himself, but I'm hoping that he doesn't need to spend his valuable coding time answering these kinds of questions on forums.

Now I'm more confused about whether or not the 3D stick support will fix Kazuku's gamepad or not. Either way I'll get to adding it to the plugin eventually, but if this won't solve his problems, then I can't help him either with the incompatible gamepad either.

It's not faulty pad, everything other working fine. Moreover i bought second and it's still same ID as first one. Probably Manta have few part suppliers.

3D stick is working proper in jacadcaps util, so it's probably this case.

I mention once again: Every other apps working fine, system recognise pad correctly (except classifying as 3D stick), just FPSE plugin don't work.

Quote:

This is how the pad classifies the input in its hid descriptor.

This is the only thing I was confused about, so thanks for clarifying. I also have to say this again: classifying a a D-pad with no Z axis as 3D input means the pad is faulty, regardless of if "Every other apps working fine". D-pads are supposed to be 2D input (digital or analog) this is what the plugin supports currently.

Quote:

Welcome to the beautiful and well thought through world of Device Class Definition for Human Interface Devices (HID) version 1.11.

There's quite a lot of devices that ship with totally bogus descriptors which are then overloaded by Windows drivers. Microsoft even provides cool samples explaining how to do this (see Microsoft's github)

[ Edited by jacadcaps 18.09.2019 - 11:03 ]

What a mess. I assume the situation is no better on the audio side either. If I add sensors.library support to anything again, I'll be prepared for the worst.

Quote:

There's good reason why games all let you re-map inputs. Just don't assume that if something says is a 3D joystick always provides all possible inputs. Or that an analogue joystick provides values other than 0 and 1 ;)

If I find the time (ha ha) I'll add a mode that always maps inputs onto a xb360 pad. The missing inputs would simply always read as neutral (0.0).

Let me also reiterate that I recommend using either a XBox 360 or the 360 wireless pad with PC adapter, XBox One pad or the Playstation4 pad with MorphOS.

[ Edited by jacadcaps 18.09.2019 - 12:19 ]

I put the sources in a git repo for easier handling. When you have time, could you check this commit? If it looks good I'll compile a new dll and upload it for Kazuki to test.

Looks fine at a first glance.

Alright, thanks. Here's the new dll. I didn't replace the old one as this is completely untested.

Thank You

I'll test it today later.

That's weird. Now directions works... but only in config. When i try to use directions during emulation only [LEFT] and [UP] directions works, even when using [DOWN] or [RIGHT] directions during configuration.

It's even more weird that in ACE (which is now using sensors based on Your sources) all is working fine.

Edit: Should i delete preferences file and re-config FPSE?

[ Edited by Solo_Kazuki 23.09.2019 - 15:52 ]

I have no idea, feel free to try anything that might help.

Old ini was deleted and new one made. Still same problem. Don't know why it's working as mentioned above.

Maybe it's something with "calibration" and only get one side of each axis?

In case you want to compare to better understand, source code of ACE joysticks plugins is included in "ACE/Bonus/Plugins SDK/Joysticks" drawer.

I already saw it, both poll the input with GetSensorAttrTags. The source code of my plugin is available here, including the build instructions:
https://bitbucket.org/BSzili/joysensors/src/master/

[ Edited by BSzili 06.10.2019 - 08:12 ]