Well wouldn’t you know, turning it off with
DISABLE_LAYER_NV_GR2608_1=“”
fixes the FPS in TLOU and other games. TLOU we are talking about an almost 50% drop in performance with the layer on! Also, I saw a 10-20 FPS boost in HZD Remastered, which is like a 20-30% boost. Yea there is something severely wrong here. If this is the expected FPS hit we have to take to do Smooth Motion, no thank you.
Hogwarts Legacy worked until I disabled it and restarted the game. Now it shows enabled but it is not working because now I am getting ~100 FPS and before it was ~200 FPS.
I use smooth motion for games that have a hard-coded 60fps limit, so that they hurt my eyes less. For everything else it’s not worth it. Also for watching gaming videos or game streams that are limited to 30 or 60 fps. Wouldn’t currently recommend it for other use cases.
If I am not mistaken, the bug where yellow highlight of interact-able objects in Indiana Jones and the GC is missing, is still present in 580.82.07 ?
I wonder why @adolfotregosa sees DLSS frame gen and the other guy @tda06261 doesn’t.
Compare your Proton version, GPU model, driver version and your launch command line for the game. Maybe the other person didn’t enable the necessary flags.
You need to enable NVAPI and unhiding the NVIDIA GPU to even make DLSS appear in games. Otherwise the Linux gaming default is to hide the NVIDIA-specific features from games.
Your images show Smooth Motion working correctly.
You have 133fps without Smooth Motion, and 144fps (77 x2) with Smooth Motion.
We already explained to you that Linux doesn’t show the fake frames in FPS counters.
The extra rendering latency is the injected shader time that is generating the second, artificial frame. It is rendering two frames during every frame that the game thinks it’s rendering. And yes, frame generation adds a bit of latency per frame, since half of the frames are artificial and thus add latency towards real input reactions. That is true for every frame generation method. You add latency but get smoother motion. That is the trade.
You definitely can’t trust the game’s FPS counters. I don’t think you can even trust the rendering time information in the game. Because 144fps is a display output rate of 6.94ms per frame.
Would be good if NVIDIA officially educates people or I believe this kind of misunderstanding “bug report” will become very common.
That hasn’t been true for a while now. You no longer need to do that.
My launch options are and have always worked before without issue
Proton-GE or CachyOS
PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 ENABLE_HDR_WSI=1 mangohud %command%
RTX 4090
Try toggling it on and then off and restart the game. Mine was showing up too until I toggled it off and restarted.
Manjaro, nobara, cachyos (I only use vms / proxmox) 5070 ti, it has never stopped showing. 100% exact same launch parameters as yours.
@tjwmmd2 yeah, you dont need to enable nvapi for quite some time.
Hmmm, that is odd indeed. When I get home today, I will restart my computer to see if it fixes itself.
That’s why I like VMs. It’s quick to boot them up and compare when something is off.
that’s not true at all, I have enabled absolutely nothing and dlls and frame generation always appear.
I’ve never had any single issue with dlls and frame gen on linux with my 4060.
I think you just have a bad configuration or you’re using a different proton version rather than the official proton from valve or proton-ge
Nope! Using Proton-GE too.
Bad config? Was working just fine before I upgraded the drivers.
DLSS has always worked for me, but Frame Generation was not selectable for me until I turned off the iGPU of my CPU in BIOS.
Did you do a BIOS update which may have re-enabled the iGPU?
This is a desktop machine, so I don’t have an iGPU and also did not do a BIOS update.
Measuring the framerate with Smooth Motion on is tricky. In game FPS counters will not know about the doubled framerate, the actual framerate will be double whatever the app reports. The app’s FPS counter will show a drop in performance due to the overhead of frame generation. This overhead increases with higher input framerates.
Similarly VSync can result in surprising numbers because it limits games to the monitor’s refresh rate. If an application is hitting the max refresh rate without Smooth Motion, enabling Smooth Motion will show up as a 50% performance drop in application’s FPS counter. The actual framerate will still be the monitor’s max refresh rate. Smooth Motion is not useful if an app already runs at your monitor’s refresh rate.
Performance overlays can report either pre or post Smooth Motion framerates. If you use X11 the __GL_SHOW_GRAPHICS_OSD=1 environment variable will enable an FPS overlay that will always report the doubled framerate. Most other performance overlays are implemented as Vulkan layers (just like Smooth Motion) meaning the results will depend on the ordering of the layers. Mangohud should report the doubled framerate because it loads itself as an explicit layer which will run after Smooth Motion’s implicit layer. In order to use Mangohud you will need to pass an additional environment variable NVPRESENT_QUEUE_FAMILY=1 to workaround an incompatibility. The Steam overlay will be ordered arbitrarily because it is also an implicit layer, sometimes it will show the doubled framerate and sometimes it will show the app’s.
If you see identical performance the feature is likely not being enabled at all. The ‘Troubleshooting’ section in the README can help diagnose the issue if this is the case.
We’re keeping an eye on this thread for actionable issues. When reporting performance issues please include the name of the game, what you used to measure the FPS, and the values of in game VSync and Reflex and DLSS settings.
Wow I have a 168hz monitor and I didn’t even know it! Thanks Jensen! RTX: It’s on! Oh and look, Mangohud shows basically the same as the in-game overlay too.
My previous screenshots were with built-in frame gen but they’re all broken in the exact same way. Do I need to boot into Windows and get a screenshot there before you’ll actually do something?
