When bl3 is finally done downloading. I will check mangohud for the frequency stuck. Nobrara, i think it’s 40. AMD 3600 CPU, 32 gb ram and 7900GRE. I use vrr on the main screen and have not seen anything weird.
There is the video.
I did add memory clock in Mangohud.
Also, if anyone knows how to get rid of the screen tearing it would be nice.
It something set in OBS that is making streaming and recording not that good.
I’ve found out that switching to X11 has resolved most if not all of the issues pertaining to what I described in this thread. Moreover, I’ve noticed that if your display fps is set to 120 and you exceed that fps in games you get screen tearing. Even if you set fps to 120 display and 120 in-game, there are instances, even on Windows, where fps goes 1-10 fps above the cap and causes tearing.
So I suggested following MangoHud configuration editing to make a profile for game you’re having issue with and cap the fps, via Mango. Set display hz to 144hz if you can (with 120 fps cap) if you can. If you can’t set your fps cap to 110-118.
Ok, I don’t know how to configure Mango. But I guess I can set the screen refresh rate to 165 and then limit fps in games to 120Hz?
Yes, that would work too. But keep in mind that fps limiters are software and thus one can be better than the other. Not saying you can’t use in-game caps but just keep in back of your mind, try experiment see which one feels smoother; MangoHud or the game’s cap. Some games don’t have a cap, others don’t allow you to turn off a cap (have to choose a fps to cap).
But just in case you may need to cap your fps and the game has none or a bad one. Go here to MangoHud github:
- Go to “Hud configuration” part
- Follow the #2 “Per-appication configuration” instruction
- If game you want to create specific MangoHud profile for is native you follow i. If it’s with WINE/Proton you follow ii.
MangoHud global and game specific (native or Proton) profiles are located at: ~/.config/MangoHud/
If you’re not familiar ~ is your user’s home location.
Try set a specific profile up, I will help you if you need.
1 Like
Thank you.If Mangohud does it like rivatuner, then I would rather do it with the program. I know inquisitor martyr does not have built in fps limit.
MangoHud is supposed to be a replacement for Afterburner (including rivatuner), even though it may not have all feature sets rights now. You can log your fps and upload csv file to here and get frame time and fps graph for analysis of your hardware and game performances. MangoHud is a must. Github page has all the info on rest of features of it.
1 Like
It worked. It kept the games at 120Hz even with the screen set to 165Hz and vsync off. Will test to see if I get tearing in obs recordings, still thank you.
Please don’t use X11 as a long-term solution to anything.
I know it is tempting, but you are actually trading a smaller pile of annoyances now to a metric shit-ton of actual issues (such as the guaranteed lack of HDR support and more and more things breaking as X11 support slowly wanes) for tomorrow.
X11 should be a last ditch effort at this point. If it works, by all means, use it. But do everything you can to walk away from it. Even the X11 devs don’t wanna do X11 dev anymore…
This with MangoHud or ingame cap and refresh rate at 165Hz? For Obs recording I don’t know, perhaps you need to set Obs fps to 120 too or 60 (120/2 = 60).
It’s only a temporary solution til I change distro.
So my idea is leave the monitor on 165Hz.
The games capped by mangohud to 120Hz.
The stream on obs to 60Hz.
Then see if there is tearing on the stream.
I had this whole VRR/Stuck mem clock issue with my 7900XTX (Dual DP monitors Samsung OLED G80SD + Dell u2723qe), was crazy since it also caused my CPU to run hotter since the GPU was constantly pulling ~80-90W at idle. If I could turn on VRR it would run at sensible power until the VRR monitor got disconnected for any reason (like display sleep), then it would revert to max clocks.
https://gitlab.freedesktop.org/drm/amd/-/issues/1403 (only been 4 years…)
Also the screen would randomly flash black with VRR enabled.
Occasionally it would get stuck in min clocks too, I thought the system was locked up the first couple of times it happened and just rebooted.
I tried using an EDID to fix it but that just disabled VRR completely. I could also not get the monitor to run at full refresh rate 240hz, max I could get was 120hz with no VRR.
Fix AMD GPU high idle power MCLK (vram / memory clock) stuck at 96 MHz / 1000 MHz for high refresh rates on Arch Linux Wayland & Xorg · GitHub (only works for low res screens, the tools are broken for 4k/high refresh currently)
The VRR Issue with amdgpu on my system at least was due to the EDID decoding in the amdgpu driver being broken. So many issues here, did not take me long to find the same issues as mine.
Also the display would randomly lockup, or wake in 640x480 mode…
Overclocking the memory also caused screen corruption…
Another big issue for me was how bad ROCM is in Linux, specifically in Davinci Resolve Studio. In Linux Magic Mask processing runs at 5fps, Windows runs at 27fps.
I briefly considered X11, but can’t go back to that mess. My solution was to switch to NV$D$A 5080. Got full VRR working 48-240hz @ 4k on Gnome.
I did have one weird issue due to the junk vulkan support in the nvidia driver which was fixed by setting GSK_RENDERER=cairo
I really dislike nvidia, but the fact that my hardware just works (and I have all my ROPs! and my GPU didn’t catch on fire yet!) and the driver is decoupled from the kernel is a big plus for me. Reverting to an older kernel to fix GPU issues is madness. You are also reverting FS features/fixes, security fixes, performance improvements, entire drivers.
1 Like
Its not so much linux sucks compared to sithware
you have to understand without native support from manufacturers linux does not come with hardware specific drivers.
linux usually relies on unidrivers for most hardware.
manufacturers are often contracted with non competition clauses and forced to support only a specified OS
individual developers often do not have the resources to purchase equipment or decompile firmware or are at severe risk of legal actions if they do.
our only recourse is to make it attractive to the manufacturers, But that could be expensive if you have to fight with the big sith lords and maclawyers.
That sounds similar to issue I would have. I would get black screen if I tried to run at certain VRAM speeds and alt tabbing between a certain game lead to black screen freeze in that game. Going back to X11 (temporary) showed me that it’s something relating to Wayland and VRR (high refresh rate). I tried so many things, like 60 hz display and 120 in games, same hz display as in games. Someone mentioned its something relating to timings of the display but because it was outside of my knowledge I decided not to try do any hacking, which could end up me breaking the entire display without knowing how to fix it.
I like Linux alot but when I said “Linux sucks” it’s that this issue seems to have been around for nearly a year. And what made it suck is that it was so difficult to find out how to solve it, and I still haven’t found a proper solution. Despite these inadequacies, that aren’t necessarily Linux’s fault (AMD’s it seems), It’s still a great platform to be on and if someone switches to Windows they will find a myriad of other crap that will create headache for them.
Right, so far the FPS limiter works great, I have have a question.
There is a function that allows for multiple FPS limits. The example they give is (0,30,60) where 0 is unlimited if you don’t run vsync.
Adaptive sync counts as no vsync so if I add that example, I just get unlimited FPS…
What do I type in that FPS limit field, if possible, to have it run at 120FPS. If it can’t make that target, step down to 60FPS or even worse 30FPS?
0,30,60,120 would give toggleable options of unlimited, 30, 60, and 120 using Shift+F1 to swap between them. Not certain but you may be able to order it as 0,120,60,30 so each press from unlimited would reduce the cap.
1 Like
Oh no. Man I hoped it would work like triple buffering did with WoW back in the day. It would step between 60 fps and 30 fps depending on how taxing the game was. Oh well. Thank you anyway.
It’s still a great platform to be on and if someone switches to Windows they will find a myriad of other crap that will create headache for them.
Absolutely, I installed windows 11 just to do a sanity check on my AMD GPU performance. What a nightmare, I had to clean install three times as the first two I got the werid scheduler bug which Hardware Unboxed picked up on in a video they did. The whole system was “laggy”, I spent ages debugging it thinking it was a driver issue, or maybe some “tweak” i needed for windows, on the 3rd clean install it was just fine… exact same install process/drivers/programs.
Then I had all sorts of issues with the AMD GPU driver as windows auto installs a bad one so I had to use DDU in safemode to uninstall the MS one and install official AMD driver with ROCM/WSL2 support.
Even with all that the interface is terrible, the whole right click menu (not just the UI) is an abomination. It can take seconds for it to pop up on some files due to the extensions that get installed and run when you click certain files, and it happens every time! Anyway complaining about Windows is an endless task… kinda like right clicking a file in Windows 11.
Overall AMD GPU on linux is a much easier experience for any user if comparing installing windows vs linux. Honestly if it wasn’t for the fact that Davinci Resolve Studio performs so badly on Linux I would still be using an AMD card.
I have had time to run a comparison with the new RTX5080 card and in DRS magic mask I get 30fps without Neural Opt (which is broken on 5080 at the moment and would improve performance a lot) which is basically the same as the Windows 11 7900XTX performance of 27fps, where 7900XTX linux gets max 7fps (avg 5fps).