After the 5.3.8.0 update, has anyone else noticed that the app graphics (not the ride videos) seem to be fuzzy, like a low quality resolution. Even the home page is like it.
@Klem (FulGaz) : This shouldn’t be marked as completed - it’s not the video that’s fuzzy - it’s all the non-video text. Here are some examples:
Moray Taylor
•
Apr 3, 2025
@Wesley Smith It’ll be in the next release, it’s fixed internally.
BadgerM
•
Apr 1, 2025
It’s not the ride video, like before the 5.3.8.0 update, it’s the app graphics, like the HUD and the terrain map at the top of the page.
Klem (FulGaz)
Team•
Apr 1, 2025
The video issue on Windows you are experiencing is the "zoomed in" video, where FulGaz is only displaying a small portion of the video like it has been zoomed right in closely (which is why it looks pixelated). It seems to be affecting downloaded rides more than streamed ones.
In most cases, ending the ride (not exiting FulGaz, just ending the ride) and then starting the ride again, tends to get the full video displayed.
Our team are looking into why this is occurring and should have a proper fix released in an automatic update shortly.
Log in to comment and vote
Comments4
Wesley Smith
Apr 2, 2025
@Klem (FulGaz) : This shouldn’t be marked as completed - it’s not the video that’s fuzzy - it’s all the non-video text. Here are some examples:
Moray Taylor
Apr 3, 2025
@Wesley Smith It’ll be in the next release, it’s fixed internally.
BadgerM
Apr 1, 2025
It’s not the ride video, like before the 5.3.8.0 update, it’s the app graphics, like the HUD and the terrain map at the top of the page.
Klem (FulGaz)
Apr 1, 2025
The video issue on Windows you are experiencing is the "zoomed in" video, where FulGaz is only displaying a small portion of the video like it has been zoomed right in closely (which is why it looks pixelated). It seems to be affecting downloaded rides more than streamed ones.
In most cases, ending the ride (not exiting FulGaz, just ending the ride) and then starting the ride again, tends to get the full video displayed.
Our team are looking into why this is occurring and should have a proper fix released in an automatic update shortly.