Open riley-brandt opened 4 years ago
Note you forgot to mention the use of fade to black which is key to this issue. Related to a recent change i didn't thoroughly check, the fade is only applied on next vblank to avoid tearing on gbc, however the screen rerender is happening before that activates. Will need to test an extra wait vblank in scroll c, but that may not cut it, alternative force palette refresh as part of update, possibly optimise screen instant black to fill registers with 0 instead of calculating black.
Thanks @RichardULZ for the information. I'll update the bug report to include the Fade to Black option (which is a great new feature that I love!).
I hope you are able to find the solution. It will really open up possibilities in my game.
Thanks @RichardULZ for working on this bug! It's an important feature for my visual novel.
I can't wait till we get a stable release so I can start developing with the new features.
@terminaltux The v2beta branch has up to date builds with these fixes and more + performance as beta5.
Fade to black events changed to an Engine Field, which now has a settings page but can still be modified with an event.
There's some script runner changes coming soon that might change things, but for now it's pretty stable, I'd recommend picking one up from the v2beta readme file links.
Describe the bug When I create a large background (like 320x288px) and move the camera instantly, graphical glitches appear on the screen during the transition if Color Mode is enabled.
If COLOR MODE IS NOT ENABLED it works fine:
If COLOR MODE IS ENABLED, the graphical glitches appear:
To Reproduce
Easy Method:
Create Your Own Method:
Expected behavior The camera will move to the specified X,Y coordinate without flashing garbled graphics/tiles while doing so.
Platform (please complete the following information): -OS: Fedora 32, 64-bit -App version: 2.0 beta3 (sept 26, 2020 itch.io build)