Screen tearimg
-
@greenhawk84 but it's fixed in kms, no? fkms is being depreciated so at some point, kms will be the only choice. that's the fix.
-
@dankcushions even though mine is Intermittent, I typically always get it at some point on Mortal kombat on FBNeo, and the Kodi menu. Other games not really an issue.
-
@lostless yep, that sounds like the intermittent one that is fixed as per https://retropie.org.uk/forum/topic/25370/good-news-regarding-tearing-and-low-emulationstation-performance-on-pi-4
i would only get it on random screens of super metroid. i think it may be triggered by a certain bandwidth demands or something like that. in any case, the fix is known and works :)
-
@dankcushions true there is a "fix" but it doesn't feel complete since ES is not 100% working as it would with fkms, such as the colors in carbon seem darker, the videos must be re-encoded, are things I know of off the bat. If perhaps I updated my setup and the kms transition occurred, along with everything in ES working as before, I would consider that 100% fixed. I am not sure if there will ever be a transition to kms without some significant work on my end to make things right in ES.
-
@greenhawk84 i don't know about screen brightness (maybe the two drivers have slightly different default gamma, but i don't know which is 'right'), but the video encoding thing, note:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=269769
Note: kms won’t ever support applications that use firmware apis for display like dispmanx, or mmal/openmax video_render, including omxplayer, raspivid and non-gbm kodi. Similarly tvservice is not useful in this environment.
and also note an old comment:
https://www.raspberrypi.org/forums/viewtopic.php?p=1688863#p1688863
FKMS covers the majority of use cases already, but yoyu are right that the main ongoing development effort is now on full KMS.
Other than the issue over vsync timing, we will investigate any major issues within FKMS still.so fkms is a dead end for this tearing issue, and kms is the future, so we just have to accept that.
-
@dankcushions thank you for the info, your support here has been great over the years. So until kms is fully tested and an official update on Retropie is implemented, I will wait. Do you know if when this update drops, will the users have to go in and make sure all the videosnap .mp4 files are ready for the change ?
-
@dankcushions well i did the change and now the splash screen doesn't work and audio doesn't work over my HDMI and kodi just exits back into itself and not emulation station anymore. But at least the screen tearing is fixed . 😂 oh the joys of experimental stuff.
-
@lostless said in Screen tearimg:
@dankcushions well i did the change and now the splash screen doesn't work and audio doesn't work over my HDMI and kodi just exits back into itself and not emulation station anymore. But at least the screen tearing is fixed . 😂 oh the joys of experimental stuff.
kodi 19 should work, apparently. the splash screen stuff is known as it relies on the original firmware API. i don't know if there's a solution in mind for that, but it won't come from changes to the driver, presumably.
audio can be fixed - lots of details on that in the linked thread.
-
@dankcushions 🤔 to splash screen or not splash screen, that is the question. Thanks for your help.
-
@greenhawk84 said in Screen tearimg:
@dankcushions thank you for the info, your support here has been great over the years. So until kms is fully tested and an official update on Retropie is implemented, I will wait. Do you know if when this update drops, will the users have to go in and make sure all the videosnap .mp4 files are ready for the change ?
i don't use videos so can't answer this point. omxplayer will not work in kms as it relied on the old stack. what that means in terms of video capabilities i don't know.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.