Open dr0id123 opened 1 year ago
im not sure of any fixes at the moment but i have noticed that whatever changed in the opengl renderer in 0.9.5 and the builds before it seem to have brought many issues , seems that many people have been encountering various problems when using the new opengl renderer
im not sure of any fixes at the moment but i have noticed that whatever changed in the opengl renderer in 0.9.5 and the builds before it seem to have brought many issues , seems that many people have been encountering various problems when using the new opengl renderer
Thanks for the thoughts on this. I went back and I tried different versions, even all the way back to the v8 releases where OpenGL support was introduced -- same issue. Software rendering works however -- however no upscaling.
im not sure of any fixes at the moment but i have noticed that whatever changed in the opengl renderer in 0.9.5 and the builds before it seem to have brought many issues , seems that many people have been encountering various problems when using the new opengl renderer
Thanks for the thoughts on this. I went back and I tried different versions, even all the way back to the v8 releases where OpenGL support was introduced -- same issue. Software rendering works however -- however no upscaling.
huh , thats interesting ... ive never encountered the issue in your screenshot in any of the previous versions , now this is really confusing . i really do wonder what the issue is then , if its persisting across all versions
I believe the latest APU driver for the Steam Deck is the cause, as it worked perfectly fine with the previous version of the driver.
I believe the latest APU driver for the Steam Deck is the cause, as it worked perfectly fine with the previous version of the driver.
^ This. ^
I downgraded to the previous APU drive and it works (technically). However, it's a mixed bag. According to a number of articles, including:
AMD re-wrote their driver for a massive performance gain in OpenGL. When I downgraded -- while the glitch is gone, performance massively suffered -- to the point where trying to move around the map was in the 40 fps range. Needless to say, upgraded back to the latest since this impacts the ability to play other opengl emulators with good framerates.
I'm left wondering, is this glitch consistent with all AMD cards (non steam deck) running the improved OpenGL? (Anyone out there willing to test?).
I believe the latest APU driver for the Steam Deck is the cause, as it worked perfectly fine with the previous version of the driver.
^ This. ^
I downgraded to the previous APU drive and it works (technically). However, it's a mixed bag. According to a number of articles, including:
AMD re-wrote their driver for a massive performance gain in OpenGL. When I downgraded -- while the glitch is gone, performance massively suffered -- to the point where trying to move around the map was in the 40 fps range. Needless to say, upgraded back to the latest since this impacts the ability to play other opengl emulators with good framerates.
I'm left wondering, is this glitch consistent with all AMD cards (non steam deck) running the improved OpenGL? (Anyone out there willing to test?).
while i cant help with amd cards , i think i should mention that im using an nvidia card and still getting opengl glitchiness , so either its an issue with all cards or its an issue with the opengl version used in the latest melonds update
This is related to:
https://github.com/melonDS-emu/melonDS/issues/1578
The Steam Deck uses AMD processor with Zen 2.
Any work on progress on this?
i have the same issue!
i have the same issue!
Download the latest build and enable the "OpenGL (Compute Shader)" render in "Video Settings", the old/classic OpenGL renderer doesn't work well with modern drivers.
Hi All,
https://ibb.co/82Z9th4
Setup: Windows 11 on Steam Deck Version: MelonDS 0.9.5 ROM: New Super Mario Bros (tried both USA, EURO) Issue: Map screen is glitched out, see screenshot. When in a level (not on the map screen, no issue). Other comments:
Therefore, whatever the issue is, appears to be a specific to this hardware-driver-MelonDS-Game combination.
Is anyone aware of what could be causing this and potential fix that I may try?