MAME4iOS
MAME4iOS copied to clipboard
yoshisuga
Virtua Racing issue
Using the MAME 0.234 core, Virtua Racing which should've been playable and working isn't working properly (and IIRC has the same issue the 0.139u1 had). Using iPhone 11
https://user-images.githubusercontent.com/49933793/132085885-b4f2e1f4-0421-4f90-82e3-b75be3c5d781.mp4
Sounds like a controller mapping issue, especially if it does the same thing in 139 too.
Summon the MAME Configure menu and look at how the inputs are mapped.
I will take a look too.
Virtua Racing gets input from a Paddle and Peddle, these should get mapped to the game controller triggers, will investigate
Dont think it has anything to do with the controller mapping (looks more like an emulation bug to me), but whatever
In fact, here’s a bit of the attract mode footage
https://streamable.com/u5um68
(Sorry for the external link. I’m not near my computer right now, so I have no means to properly compress the videos).
Dont think it has anything to do with the controller mapping (looks more like an emulation bug to me), but whatever
Yup those mappings look ok, on screen controls should work (might want to switch to analog in Settings > Game Input) but the INC and DEC will function.
In fact, here’s a bit of the attract mode footage
https://streamable.com/u5um68
(Sorry for the external link. I’m not near my computer right now, so I have no means to properly compress the videos).
Wow, that is messed up! I will check it out!
The same thing happens in baseline MAME 0235
this is NOT a MAME4iOS issue, please close and report to MAME
Wait, I played this on mainline MAME 0.234 and it was fine. I’ll give the direct capture from my laptop soon.
Hmmm I just built 0235 and ran, and had the same issues you had (spinning to the left in atrack mode etc)
Maybe it is a problem when built for arm64 (I built on a M1) so same problem for iOS and M1.
I will fire up a build on my old MBP and go see a double feature....
So this is still a mystery.....
Sorry @mywebsiteworks2 for the back and forth, thanks for isolating this....
Not sure if the problem's caused by the ARM64 build This is what it should look like on normal X86 MAME 0.235 (and 0.234 as well)
https://user-images.githubusercontent.com/49933793/132303429-a8ab4765-d68c-4916-bf41-b9ebc6898eec.mp4
My x64 build of MAME runs VR just fine. So it is a problem with the arm64 build, maybe DRC.
The input is a little strange, but that will be a issue later when we get the arm64 to build right.
