-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Babypacman rom does not work with VPinMAME 64 bit #80
Comments
Seems like 32bit also has a similar issue, but for whatever reason it works fine the 1st time started. The following times, it fails, too. |
To be honest 32bit seems to work and is playable for me, but I do notice
when I close out of the table VPX will crash as well, so maybe it's related.
…On Sun, Nov 20, 2022, 16:21 toxie ***@***.***> wrote:
Seems like 32bit also has a similar issue, but for whatever reason it
works fine the 1st time started. The following times, it fails, too.
So somehow the 32bit version is more lucky with some uninitialized mem
maybe?
—
Reply to this email directly, view it on GitHub
<#80 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPTQP5HLJE75RNSSNA7GX3WJKW7BANCNFSM6AAAAAASE7K7JE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ROM works presently with both 32 and 64 bit builds |
Thanks! This points once more to some instability/uninitialized memory, i guess. |
@toxieainc if it is any consolation |
Are you sure it works for you in 64 bit? I've update and reinstalled vminmame for 64 bit on different computers and it doesn't run. Audio works but graphics are garbled. |
yes, works fine far as i can tell here |
I'm also getting this problem, using VPinMAME/libpinmame/PinMAME version v3.6-573-5d6459d on Windows 10 Pro (64-bit). I have no clue if VPinMAME has any way to create a verbose log file of a game; if it does, I'll happily provide one. ADDENDUM: I just tested and this still happens as of the latest commit: aaa6676. Here's a video I recorded showing the garbled graphics, but otherwise functional game. (note how the graphics change later in the recording; I believe this to be further proof that uninitialized memory is the cause of the problem). 2023-10-24.16-31-21.mp4Some observations:
|
Since This game has a display type of
For the heck of it, I modified
And indeed the screen is there: I'll look into this some more to see if I can add support in |
If its 'only' the 64bit display code of VPM, then hopefully this is easier to fix. Lets see how testing goes if libpinmame eventually get support. Thanks! |
I did some more digging (namely by trying to find a bisect, albeit with limited resources as I'm relying entirely on Github Actions artifacts) and determined that |
Same for me, Babypac show garbled screen with 64 bits vPINMAME only, 32 bits work properly. |
The last working version of Babypac in 32bit was 10.8.0-925. All the releases after, the drop target in front of the captive ball is up when the game begins. The drop target should be down so you can hit the captive ball and transfer it to the other side. |
Ok it is a vpx issue. sorry, my post is at the wrong place. |
Something is pretty strange with Baby Pac-Man... |
Pereaps it’s a rom initialisation issue. |
Steve Ellenoff owns a Baby Pac-Man, and he did the emulation back then. |
@volkenborn |
Well. I could fix at least the reset issue; that was due to some uninitialized sound latches. |
@volkenborn |
@volkenborn .Games(cGameName).Settings.Value("rol") = 0 |
Maybe also related to #129 ? |
Babypacman rom does not work with VPinMAME 64 bit.
Images is scrambled. 32 bit works fine.
The text was updated successfully, but these errors were encountered: