-
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
Opening OSD Menu Breaks Games/Core #175
Comments
Having same issue on the latest versions in Donkey Kong 94 with “Pause when OSD is open” enabled. First I thought it’s hardware/memory issue, but memtest result is fine |
@HiroiSekai could you try this test - https://github.com/antoniovillena/MiSTer_DB9/blob/master/Old/SDRAM.zip? I have fail on jtcps1_-520ps.rbf with "rom no good", so it could be problem with SDRAM v2.5 on my side. |
Thanks for posting the test. I ran all 8, and they all say OK with just "ROM" at the end and it loads the Ghouls demo. Looks like mine is okay. |
@RobertPeip This seems to happen when the core is paused when I made the trace in the first level in Donkey Kong Land 2 and just toggling Pause when OSD is open. |
Looks like it gets stuck here waiting for Gameboy_MiSTer/rtl/speedcontrol.vhd Lines 62 to 66 in dd03f9a
Changing it to below makes it still generate if (pause = '1' and clkdiv = "111" and cart_act = '0') then
state <= PAUSED;
unpause_cnt <= 0; |
Yes, that should be the prefered way: don't go into paused state as long as cart_act is high. I cannot remember why I have not put cart_act directly into the if clause as you did now. |
Thanks Robert. I will send a pull request. |
This should be fixed now with release 1107. |
Hello, I've been having a great time with the MiSTer, but this one core has been having some weird issues, wanted to know if it was known or if something was wrong on my end. It's a bit of a multi-symptom issue so I'll do my best to describe it.
The core works really well as is. However, when I open the OSD to pause the game or adjust some settings, sometimes when I exit, either the core will crash completely forcing a reboot, or the game will exhibit weird changes that slowly make it literally unplayable. This usually occurs when the OSD is left open for longer. Some examples I came across so far:
In General
Donkey Kong Land II
Pokemon Trading Card Game (1 & 2)
That's just the examples I've come across so far, but it only happens on this core. I can leave the OSD menu open for days if I wanted on the other cores with no problem, but if I even leave it open for something like 10-15 minutes on this core, these problems may or may not happen, either immediately or slowly over time afterwards. It's really weird.
I'm really hoping someone can provide a fix or an answer as to what's happening at the least. I never really experienced anything like this on my software emulators so it's new to me. I hope it's something simple, otherwise if it's a known issue, I know I can do my reboot workarounds until it is fixed.
Thank you!
The text was updated successfully, but these errors were encountered: