VRR Broken after 11-04 update on ROG AllyX

Updated my ROG Ally X yesterday and now VRR is stuck in the disabled state regardless of what the toggle in QAM is set to, and regardless if there's a game running or not. Rolling back to Bazzite 40 restores functionality in that the toggle now reads enabled and Gamescope's "app" readout changes when toggled, but the image is still very stuttery, and updating back to current stable breaks it again. This didn't happen on my Win Mini on the same update, is this something I need to reinstall Bazzite to try to fix?
39 Replies
antheas
antheas6mo ago
But is the vrr working
Luciana Rothcall
Luciana RothcallOP6mo ago
doesnt appear to be, it does -something- but it's very much not smooth unlike on the WinMini with the same settings and same display
antheas
antheas6mo ago
Works on my ally tested it today but I think I'm not on the very latest
Luciana Rothcall
Luciana RothcallOP6mo ago
yeah, was good until updated to the latest yesterday cant seem to rollback to the version before that, only the july? Bazzite 40 image so guessing the next step is just wipe the drive and start over linuxstuff is out of my knowledge base but i feel like something coulda gotten messed up with my AllyX constantly sleeping itself mid-update the WinMini never did that Yeah, managed to rebase to oct releases and it remains, i think I need to reinstall everything :depressed: Okay... reinstalled from the bazzite 40 USB stick i had, seems it auto updated to 41 aaaand VRR still doesn't work
antheas
antheas6mo ago
we will figure it out in a few days but vrr should work even if the indicator is broken
Luciana Rothcall
Luciana RothcallOP6mo ago
Its odd bc it's just not smooth at all, regardless of framerate
antheas
antheas6mo ago
but do you see a difference in frametimes? i think it might be the game
Luciana Rothcall
Luciana RothcallOP6mo ago
I do nd the same game with the same settings on WinMini doesnt do this lemme know if there's any info I can try to provide from my end that might be of use, scatterbrained from lack of sleep today so have definitely been kinda incoherent with this @@
antheas
antheas6mo ago
me too its almost 3 am
Luciana Rothcall
Luciana RothcallOP6mo ago
Best I can currently describe the difference between the two is the AllyX is all microstuttery w/ "VRR Disabled" and the slider on or off, and the Frametime and App graphs in the lv4 QAM performance overlay are very different, with the latter being a sharp saw-wave of up down up down up down meanwhile on the Win Mini w/ the same display panel the image is super smooth, QAM says "Display State: VRR Enabled", and the two graphs in the lv4 performance overlay closely follow each other in shape
antheas
antheas6mo ago
ok so vrr is broken I think your ally might have one of the special display panels Check the framerate limiter if it has all the refresh tates
Cilantro Limewire
When I have vrr set to enabled and get overlay level 4, the bottom always says hz:120 regardless of games framerate. If vrr is working correctly should this be fluctuating?
No description
antheas
antheas6mo ago
Yes vrr works Should be 120
Cilantro Limewire
I see, so other than going by feel, what in perf monitor should I look for to determine if vrr is or is not kicking in? Both enabled and disabled both graphs fluctuate with output frames
antheas
antheas6mo ago
If you turn off vrr it will be obvious in the bottom graph It will dither
Cilantro Limewire
Ahhh yes I see it now
Cilantro Limewire
For anyone else’s ref if it helps:
No description
No description
Luciana Rothcall
Luciana RothcallOP6mo ago
mine only does 120hz in QAM Does special display panel mean I need to try buying another AllyX if want VRR? :Popowut:
antheas
antheas6mo ago
No mine has the same issue But we never fixed it for the special panel I have a file you can add to fix it
Luciana Rothcall
Luciana RothcallOP6mo ago
:Popo: :speed2: May ask for the file and how to use it when you have some time to spare?
Cilantro Limewire
Some have different hardware? Is there a way to check the model numbers or something in terminal?
antheas
antheas6mo ago
Yeah you can check your edid
antheas
antheas6mo ago
here, put it in ~/.config/gamescope/scripts/00-gamescope/displays/asus.rogally.lcd.lua
antheas
antheas6mo ago
youll have to make the dir
Luciana Rothcall
Luciana RothcallOP6mo ago
anything to do after its placed?
antheas
antheas6mo ago
reboot and thats it
Luciana Rothcall
Luciana RothcallOP6mo ago
kk, will get it checked soon as this install of what I assume is a bunch of gamestuff is finished think that fixed it, there's still little spikes here and there but now the "app" graph mostly follows the frametime graph in shape, and there's a lot less microstutter tysm on the help with this
Chronus
Chronus6mo ago
Is this added on the new update?
Rahzadan
Rahzadan4mo ago
@antheas I just tried this as well, and it fixed VRR on my Rog Ally X. VRR was not working before I added this file. I'm on Bazzite Stable (F41.20250106) - Do you have any more info on this supposed "special panel" and if this fix will be made permenant?
antheas
antheas4mo ago
@matt_schwartz you should fix this
matt_schwartz
matt_schwartz4mo ago
GitHub
[Script] - Add support for BOE-panel ROG Ally X models w/ `Alphanum...
There are actually two ROG Ally X panel models in use: the standard TMX TL070FVXS01-0 which is shared with the original ROG Ally, and an additional panel model that is only used on some ROG Ally X ...
antheas
antheas4mo ago
How do I merge this
matt_schwartz
matt_schwartz4mo ago
It breaks the existing configuration but here https://github.com/matte-schwartz/gamescope/commit/0fbe5847316c10fb30cf4af01f9d5d3c652167fd.patch Sharks suggestion didn’t change anything
antheas
antheas4mo ago
What do you mean it breaks the existing one Both need to work
matt_schwartz
matt_schwartz4mo ago
Read the issue 🐸
Rahzadan
Rahzadan3mo ago
Any update on this? Is there a way forward, or will this always be a manual fix?
doink
doink2w ago
I tested the latest release, does not seem to be fixed.
antheas
antheas2w ago
Try testing, that has the new vrr
doink
doink2w ago
I'll rebase and report back findings. Just rebased to bazzite-deck:testing and confirmed that VRR is enabled without using that workaround. This was a fresh install, then a rebase over to testing. The only modifications done were the initial setup script actions that launches when you go to Desktop for the first time. Rebasing back to stable reintroduces the issue. Will this make its way to stable soon, and will it matter if I have that lua file in there when the fix comes to stable?

Did you find this page helpful?