Gamemoderun %command% -vulkan -novid -nojoy -high -tickrate 128 -fullscreen -refresh 165 +exec autoexec.cfgĪlso tested without -high and same results.
~/.cache/mesa_shader_cache folder can be removed after My startup options are very similar to what you suggested: ~/.cache/mesa_shader_cache_sf where the single shader cache file (there will be multiple files, but the cache is stored in a single file) will reside. Put MESA_DISK_CACHE_SINGLE_FILE=1 in your /etc/environment or export it. This is probably because all have pre-shader cache activated (default) in steam client, and then they download the shader caches.įor Vulkan they are not yet available, so the shader cache has to be created, and therefore it lags until the cache is fully stored.įurther testing possibility use single mesa shader cache file (mesa 21.1+ required) Shader cache has been stored, I had no issues after all. So I joined DM as spectator and moved around the whole map(s) and after some time as probably the whole I tested -vulkan on DM, and it lagged really hard in the beginning. So using the game without is probably the best. IMPORTANT -threads option with more than 16 will crash the game (tested on 96 core machine) threads 4 -> 290fps (I think not using threads option defaults to 4 if CPU has at least 4 cores) Could you try these launch options (if not already set - remove high if you have it or threads for testing) +fps_max 0 -novid -nojoy -fullscreenĭoes this happen only during DM or does this also happen on workshop aim maps or local bot games?
0 kommentar(er)
