Page 1 of 1

Testing the scaler fix

Posted: Thu Jan 28, 2021 6:05 pm
by pgimeno
Quoting from the release notes, as we're not allowed to post in that thread anything that aren't release notes:
Sorgelig wrote: Wed Jan 27, 2021 4:21 pm So, i need feedback if this build fixes the problem. But you have to strictly follow following rules or fix won't work for you:

- Start any core ONLY from Menu core (so go back to Menu core if you want to start other core. Better to use HW reset to go back to Menu).

- Use HDMI video (VGA output doesn't show this problem clearly and doesn't allow to identify the issue).
I have been affected by this issue and been waiting for this fix since the first day I got my MiSTer, so I'm eager to test. My question is, how bad is it to use soft reset (e.g. Shift+Ctrl+Alt+AltGr) instead of hard, in order to test this? I ask, because for me, a hard reset means that I have to walk to the computer, which is in a different room, in order to reboot via SSH, otherwise the SSH connection does not finish cleanly and I have to wait minutes until it's back to functional. In fact, that's the very reason I want it fixed so badly.

Re: Testing the scaler fix

Posted: Thu Jan 28, 2021 7:17 pm
by pgimeno
I think I've found out myself. I got the issue when going from the QL core to the menu, when pressing the soft reset key combo. I guess that doesn't count, right?

Re: Testing the scaler fix

Posted: Fri Jan 29, 2021 6:05 am
by Sorgelig
Long press of Shift+Ctrl+Alt+AltGr combo provides a hard reset.
Short press doesn't do any reset, it just loads Menu core, but if you use a wallpaper and it displays correctly after combo then you can count it. If wallpaper is broken, then you have to do a hard reset (combo or HW button).

Re: Testing the scaler fix

Posted: Mon Feb 01, 2021 8:36 pm
by pgimeno
I've made the following test:

- Go from menu to core by selecting the core in the list, check if the screen is broken (can be checked only with cores that display something meaningful on boot, like Amstrad or ao486 or GBA).
- Go from core to menu by pressing Shift+Ctrl+Alt+AltGr, check if the screen is broken.
- If the screen is broken, take note of whether it happened when going from menu to core, or from core to menu.
- Repeat indefinitely until the screen gets broken 10 times (with subsequent reboot, of course).

When I finished, the screen got broken 0 times when going from menu to core, and 10 when going from core to menu.

From these results, I think the patch does cure the issue.