Problems with AmigaInputAnyware

@LiveForIt

Quote:
You *must* query for offsets for every controller. The struct that contains the data from all the controller's inputs varies in size depending on the number of axes, hats and buttons it has. Without querying it, you're assuming a certain layout, which is probably why your buttons are getting swapped and why I have buttons that correspond to axes on my controller. It's additionally risky if the controller is simpler, because then you could be accessing data beyond the end of the struct.

Quote:
That would be nice, but I've started work on my own fixed alternative anyway that's implemented as a commodity.

Quote:
True, it's not an event you're looking for. But to read an event, you need a valid context, so you need to be sure your device is connected before you use GetEvent()

Quote:
True, but you don't query a device if you don't have context so that should never happen. Once you find out that the device is disconnected (while you still have context), you drop the context and don't carry out any more reading of the device. Instead, you start from scratch with a new context, repeating if necessary until a suitable device is found.

Quote:
Which is fine in theory, but in reality your program doesn't own the device, the user does. And the user can take away that device no matter what your program thinks.

Quote:
I agree, any accesses when the context is no longer valid should return an error code to that effect so that you know it's no longer valid (and out-of-context queries should not be forwarded to the USB stack), but unfortunately this isn't the case. As with obtaining the device, the context is at the mercy of the user, not just your program. If the user changes the context, it can't be valid any longer and must be refreshed.

Quote:
This might be a good idea, though it shouldn't be necessary. What might also be a good thing to do, is to query if the controller is connected before AIN_GetEvent().

@Daedalus

Quote:

Yes that should like the best way to do it.

Quote:

Amiga Input anywhere is reading events it does not poke the device memory, so there is no rick here.

Quote:

But it wont be atomic, the user might unplug it between checkng if its connected and AIN_GetEvent,

player can also unplug it while program is event loop, reading the queue



Amiga Input is broken but I agree I can make my code safer maybe.

@LiveForIt

Quote:
Fair enough, in which case it would appear that AmigaInput itself is misaligning the struct contents. That would mean the risk is still there of course, just not directly from your code. In that case, perhaps polling it once per frame (the old-fashioned Amiga way of doing things) would be a better option all round? At least supported controllers would be properly recognised.

Quote:
Yes, that's true, but the time between the check and the event fetch should be very small compared to the rest of the game loop, which minimises the risk. As for the event list, you can check for connection before each read of the event, or copy the event struct contents to a dummy struct so that each check in the event loop isn't reading the event again.

Quote:
Yep, it is broken, but a lot can be done to avoid the issues or greatly reduce the risk of them occurring, rather than just shrugging them off.

@LiveForIt

AmigaInput or AmigaInputAnywhere related i dont know!

But here goes anyway!
Last week I tried my Retroflag SNES joypad with no succes at all with my X5000 until I RTFM! I press Y while connecting the USB and it works nicely.

I have an old Logitech Rumblepad2 which have worked now and then through the years with AmigaInput but always at some point crashed/destroyed EnvArc:Sys/AmigaInput..

But since I've switched to the SNES joypad no more crashes/corrupted prefs!

Which leave me to believe that USB stack is the guilty one,
what is the max ampere drain allowed by AOS4.1 USB stack and/or AmigaInput?

I know the X5000 has much weaker ampere on USB ports than my A1XE had but worth checking!

@khayoz

These problems are not related,

AmigaInputAnywhere is tool to fix game and programs that don’t support joypads, I was kind of making fun of AmigaAnywhere at the time, this where name comes from.

The only problem I know of in AmigaInput is that it crashes if PCI is enabled, and that no gamepads are found unless they are calibrated.

Other issues your describing can be result of updating OS, or file corruption in the OS, the filesystem your using and how careful you are when powering off, or rebooting your computer.

Don’t think you have hardware problem, but you always check in Linux if your USB devices are losing connection.

@Daedalus

If there is any issue, its most likely when the event is pushed into input.device, this where I think Amiga Input Anywhere might fail, it use to work ok, something might have changed in the OS, that I do not control.

Not I had similar problems with vkeyboard as well, of freezes issues. way it never got released.

AmigaInputAnywhere now open sourced.

https://github.com/khval/AmigaInputAnywhere

@LiveForIt

Awesome, thanks very much for that! I'll check it out at some point when I have time.

I'm beyond confused trying to use AmigaInputAnyware on OS4depot

Is there a newer version? Would love to play keyboard only game susing either my USB gamepad or my old school jpytsick via my Catweasel Mk4+ if possible

update:
some success...by keeping AmigaInput open on workbench somehow I got the gamepad directions to work but no luck with any buttons..well when playing the game as some buttons only work on game screen??

Here's the info you need to make sense of AmigaInoutAnyware aka watch walkero's Twitch video on July16-24

walkero wrote:
Quote:

Thanks

I still can't get any of my gamepad buttons working with AmigaInputAnywhere??? Up, down, left and right on gamepad working but useless if I can't get any buttons working

@328gts
I got the same problem aswell..
Try to use the ADoom.
Then bullets works for me. But i can't get the bombs working with the pad.

@328gts

Hi for example I created a new entry and renamed frikingshark and just changed wher the fire buttons (CTRL and leftALT keys in game) are mapped to my gamepad buttons.
So I set/remap to may gamepad (has 12 buttons):
...
Button 1 -> CTRL
...
Button 6 -> LALT

no other entry was changed. Then just laucnhing frykinshark in AmigaInputAnywhere's GUI O keep the frikinshark entry selected.
So during game when on my gamepad a push Button 1 is like I was using CTRL key and same with Button 6 (leftALT)