Arch Linux

naygez

Member

Registered: 2026-03-01

Posts: 2

most games through proton have very bad performance

Each time that i turn on Hell Let Loose (steam), i get terrible framerate, stuttering on the mouse, making doing anything impossible.
Proton works fine on TF2 and other games, i dont have any lag, stuttering etc.
How may i fix this problem?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,106

Re: most games through proton have very bad performance

https://bbs.archlinux.org/viewtopic.php?id=57855

What's your system configuration, which GPU do you use, are you sure it's being used, are lib32 graphics/vulkan drivers installed? What output do you get from

vulkaninfo --summary #vulkan-tools
glxinfo -B #mesa-utils
glxinfo32 -B #lib32-mesa-utils

Are you sure you're using TF2 through Proton? It has a native version.

naygez

Member

Registered: 2026-03-01

Posts: 2

Re: most games through proton have very bad performance

the output looks like this:
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.341

Instance Extensions: count = 27
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_layer_settings                  : extension revision 2
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_maintenance1            : extension revision 1
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 4
--------------------------
VK_LAYER_MESA_anti_lag      Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303  version 1
VK_LAYER_MESA_device_select Linux device selection layer                                 1.4.303  version 1
VK_LAYER_NV_optimus         NVIDIA Optimus layer                                         1.4.325  version 1
VK_LAYER_NV_present         NVIDIA Presentation Layer                                    1.4.325  version 1

Devices:
========
GPU0:
    apiVersion         = 1.4.335
    driverVersion      = 26.0.1
    vendorID           = 0x8086
    deviceID           = 0x9bc4
    deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
    deviceName         = Intel(R) UHD Graphics (CML GT2)
    driverID           = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
    driverName         = Intel open-source Mesa driver
    driverInfo         = Mesa 26.0.1-arch1.1
    conformanceVersion = 1.4.0.0
    deviceUUID         = 8680c49b-0500-0000-0002-000000000000
    driverUUID         = 30197fcb-8a7e-d879-bf7f-c30f00ec8457
GPU1:
    apiVersion         = 1.4.335
    driverVersion      = 26.0.1
    vendorID           = 0x10de
    deviceID           = 0x1f95
    deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
    deviceName         = NVIDIA GeForce GTX 1650 Ti (NVK TU117)
    driverID           = DRIVER_ID_MESA_NVK
    driverName         = NVK
    driverInfo         = Mesa 26.0.1-arch1.1
    conformanceVersion = 1.4.3.0
    deviceUUID         = 6701de10-951f-0000-0100-000100000000
    driverUUID         = 940db202-c13e-388e-cf28-585fef2b2f69
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics (CML GT2) (0x9bc4)
    Version: 26.0.1
    Accelerated: yes
    Video memory: 15755MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.0.1-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.0.1-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.0.1-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

and yes, im sure that i run it through proton since i manually changed it to ge proton

GPU setup - Intel + NVIDIA hybrid
Integrated GPU - Intel UHD Graphics (Comet Lake GT2)
Dedicated GPU - NVIDIA GeForce GTX 1650 Ti Mobile
Intel driver - Mesa
NVIDIA Vulkan driver - NVK (Mesa)
OpenGL renderer - Intel UHD Graphics
Vulkan - works on on both GPUs
OpenGL - version 4.6
Display server - X11

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,106

Re: most games through proton have very bad performance

The games you are running run on what (DXVK_HUD=1 for a small overview in the launch options, assuming they opt for dx11/dx12)? On TF chances are you're using the OGL renderer either way, which would autoselect the intel gpu by default. Things that use dxvk vkd3d, will by default default to the dGPU, are the games that are performing "bad" running on that via NVK? Afaik NVK is still somewhat experimental, can you reproduce any of this on the proprietary nvidia stack?

On a formal note, please use  [code][/code] tags when pasting outputs.