💚 Nvidia

Current known issues

  • See the Nvidia section of our latest news for the ways in which Nvidia is being special today.

Crash when taking shield damage in-game

  • There is a shield rendering bug that causes the game to crash. It seems to affect 1000 series cards.
  • There is currently no known workaround other than switching cards. We recommend AMD.

Typically caused by dxvk being broken or not installed

  • Use the LUG Helper to update dxvk

Game fails to start after clicking Launch Game on laptops with Nvidia GPU + intel graphics

  • Errors may include
    DXVAVDA fatal error: could not LoadLibrary: msvproc.dll
    or
    Major opcode of failed request: 156 (NV-GLX)
  • Try removing all optimus/prime env vars for render offload and set the Vulkan device to the Nvidia GPU.
    • identify device name using command vulkaninfo --summary | grep deviceName
    • set device name with environment variable DXVK_FILTER_DEVICE_NAME=yourdevicenamehere

Severe frame drops

  • Some Penguins are seeing VRAM exhaustion problems on Nvidia cards. Overriding the max allowed VRAM allocation may help.
  • Use the LUG Helper to edit your launch script.
  • If you’re using DXVK:
    • Add the following environment variable to your launch script. Replace 4096 with the appropriate value from the table below. 
      export DXVK_CONFIG="dxgi.maxDeviceMemory = 4096;cachedDynamicResources = a;"
  • If you’re using Vulkan:
    • Use vulkaninfo --summary to verify that you have the VK_LAYER_MESA_vram_report_limit layer available. If you do not, look for a package in your distro’s repos named vulkan-mesa-layers or similar.
    • Use vulkaninfo --summary to find the correct vendorID:deviceID values for your GPU.
    • Add the following environment variables to your launch script. Replace 4096 with the appropriate value from the table below. Replace ID=0x1002:0x73df with the vendorID:deviceID values found above. 
      export VK_LOADER_LAYERS_ENABLE=VK_LAYER_MESA_vram_report_limit
export VK_VRAM_REPORT_LIMIT_HEAP_SIZE=4096
export VK_VRAM_REPORT_LIMIT_DEVICE_ID=0x1002:0x73df
    GPU VRAM (GB) Overriden Value (MB)
    12 9216
    10 8192
    8 6144
    6 4096
    4 2048

DLSS (Deep Learning Super Sampling)

  1. Use the latest LUG Helper to install a LUG-Wine runner. (For any other wine runners, avoid wine-staging)
  2. Use the latest LUG Helper, select Manage DXVK, and install DXVK-NVAPI
  3. DLSS 3 will now be available in the game options
  4. To enable DLSS 4, add the following environment variables. In the Helper’s Maintenance menu, select the Edit launch script option 
    export PROTON_ENABLE_NGX_UPDATER="1" 
export DXVK_NVAPI_DRS_NGX_DLSS_SR_OVERRIDE="on"
export DXVK_NVAPI_DRS_NGX_DLSS_RR_OVERRIDE="on"
export DXVK_NVAPI_DRS_NGX_DLSS_FG_OVERRIDE="on"
export DXVK_NVAPI_DRS_NGX_DLSS_SR_OVERRIDE_RENDER_PRESET_SELECTION="render_preset_latest"
export DXVK_NVAPI_DRS_NGX_DLSS_RR_OVERRIDE_RENDER_PRESET_SELECTION="render_preset_latest"
  5. To confirm DLSSv4 is working, enable the debug overlay env var and look for it in-game to say Render Preset: K or DLSSv3 v310.x+ 
    export DXVK_NVAPI_SET_NGX_DEBUG_OPTIONS="DLSSIndicator=1024,DLSSGIndicator=2"
  6. Disable the debug overlay when done by changing the above env var to: 
    export DXVK_NVAPI_SET_NGX_DEBUG_OPTIONS="DLSSIndicator=1,DLSSGIndicator=1"

Nvidia Smooth Motion

  • Mangohud and other FPS monitoring HUDS may interfere with Smooth Motion and cause game crashes. You may need to disable them.
  • Vsync may need to be disabled in the game’s graphics settings.

When using Smooth Motion, the following environment variables may slightly improve latency if you have a compatible monitor:

export __GL_GSYNC_ALLOWED=1
export __GL_MaxFramesAllowed=1

Gamescope not working

  • See this known issue report.
  • A possible fix is to set the environment variable __GL_THREADED_OPTIMIZATIONS=0