PD opening

[olivieryuyu]

ares-emulator/ares@25d49fc

fixed here

[Jj0YzL5nvJ]

On real hardware, that screen is only visible after a reset... It isn't clear to me if "that correction" shows the copyright screen when turning on the console or if it stops showing it.
My hardware is not compatible with Ares, can you clarify that for me?

For me the correct behavior is not to show that screen when starting the emulator. Showing it after a "hardware reset" would be correct.

[olivieryuyu]

it shows at boot, not at restart

[Jj0YzL5nvJ]

If they are trying to create an emulator that fixes hardware defects, it should also show that screen after the reset and run the game to 60fps.

Seriously, are they recreating EverDrive (or whatever) behaviors and throwing cartridges behaviors to the trash?

[olivieryuyu]

https://www.youtube.com/watch?v=a6Ee4VFp3OM

here capture on real n64

[olivieryuyu]

I have the same on my N64

[Jj0YzL5nvJ]

Nice Mandela Effect, that no happens in my hardware at boot. Only at restart.

Like here: https://youtu.be/MX_QoNfCNKY?t=52m51s

[Jj0YzL5nvJ]

Very similar to the SM64 intro glitch, many people claim to see it on real hardware, others claim not to be able to reproduce it. I can't reproduce that glitch on my hardware, but I have seen it on other consoles. But usually on such consoles you can see similar glitches with all cartridges, not just SM64.

I have always attributed this difference to the fact that the owner removed the cartridge with the console on and ended up damaging a portion of the console's memory.

[gonetz]

Fixed with commit ff47414.
@olivieryuyu thanks for the link! It helped.

[gonetz]

Nice Mandela Effect, that no happens in my hardware at boot. Only at restart.

I tested with Project64. It sends the necessary data right on the first run, without need to restart. The problem was in VI register data, when vEnd < vStart. The plugin treated that situation as an error and set screen height to zero, so nothing was rendered.

[olivieryuyu]

super :)