Just installed bazzite-deck with the testing branch on my OLED deck, and it's mostly working well. T
Just installed bazzite-deck with the testing branch on my OLED deck, and it's mostly working well. There's two bugs I've noticed so far:
1) In the mangohud display that's built into Steam game mode, overlay 2 doesn't show any frametime graph next to FPS. It appears in overlays 3 and 4. In addition, overlay is missing information on CPU power usage and temperature.
2) This is a bit more serious - when using the frame limiter in game mode, limiting the framerate to any number that doesn't divide into 90hz results in a very choppy frametime presentation, with the frametime fluctuating rapidly between a few ms (you can observe this using mangohud overlay level 3). You notice this in-game as microstutters during gameplay. This disappears if I set the refresh rate to anything that sets the panel to 90hz. This is a problem given 60 and 40 FPS values are a common target to hit for the deck.
2b) As an addendum to the above, setting the frame limiter to more unorthodox limits (such as 80hz) means the frame target fails to reach the target at all, and hovers at different values (in 80hz's case for instance, it tries to stick to 60 FPS for some reason).
1) In the mangohud display that's built into Steam game mode, overlay 2 doesn't show any frametime graph next to FPS. It appears in overlays 3 and 4. In addition, overlay is missing information on CPU power usage and temperature.
2) This is a bit more serious - when using the frame limiter in game mode, limiting the framerate to any number that doesn't divide into 90hz results in a very choppy frametime presentation, with the frametime fluctuating rapidly between a few ms (you can observe this using mangohud overlay level 3). You notice this in-game as microstutters during gameplay. This disappears if I set the refresh rate to anything that sets the panel to 90hz. This is a problem given 60 and 40 FPS values are a common target to hit for the deck.
2b) As an addendum to the above, setting the frame limiter to more unorthodox limits (such as 80hz) means the frame target fails to reach the target at all, and hovers at different values (in 80hz's case for instance, it tries to stick to 60 FPS for some reason).
