60-100 FPS), because then there's better chance you get CPU-limited and glthread can make some difference. Use graphics settings which yield reasonably high FPS (as you'd really like to play, e.g. So don't run in 4K on Ultra settings, if you get 30 FPS, because you'll be likely GPU-limited and you'll see no difference. Mesa glthread can only help you when the CPU is the bottleneck of rendering, not when you're GPU-limited. Another option is to look at ps aux output.
The easiest way is probably to run htop, the process is likely to consume lots of CPU and it will be somewhere on top (or you can use F5 Sorted view to see which child processed are spawned by steam, or GOG's start.sh script). It's important to find the correct executable name so that Mesa can detect when this particular game is running. $ vblank_mode=0 mesa_glthread=true GALLIUM_HUD=fps /path/to/your/game/executable Finding the executable name If your maximum FPS stay on your monitor refresh rate (usually 60 Hz/FPS), it's quite likely the vsync is enabled.
It's recommended to have a slower CPU compared to the GPU.ĭon't forget to disable vsync (vertical synchronization), either in game options or via vblank_mode=0 environment variable. In order to have a good chance of having higher performance, API-thread-offloaded-slots must be 2x or higher than API-thread-direct-slots. Even if you enable glthread, Mesa can still decide to disable it for compatibility. If they are 0 while playing (not in menu or during loading), glthread is force-disabled. The API charts on the HUD show glthread counters. $ mesa_glthread=true GALLIUM_HUD=fps,API-thread-offloaded-slots+API-thread-direct-slots+API-thread-num-syncs /path/to/your/game/executable $ mesa_glthread=true GALLIUM_HUD=fps /path/to/your/game/executable If you want to combine that with enabling glthread on a command line, it would look like: (as usual, replace game executable with %command% if you're setting this in Steam). $ GALLIUM_HUD=fps /path/to/your/game/executable GALLIUM_HUD: Use GALLIUM_HUD=fps environment variable to show a FPS overlay.Steam: If you run a game through Steam, simply enable FPS counter in Settings -> In-Game -> In-game FPS counter.Perform the test at least twice to verify results.
#Grim fandango remastered stuttering drivers#
Please note that the first execution of a game with updated drivers shows more stuttering (and therefore has lower average FPS in benchmarks) due to recompilation of shaders.
If your game doesn't have a benchmark mode, go to an (ideally static) game location and observe the FPS on the screen. desktop launcher for a game:Įxec=env mesa_glthread=true /path/to/your/game/executableĪlternatively, you can modify /etc/drirc accordingly. In steam, you can go into Properties -> Set Launch Options and use $ mesa_glthread=true /path/to/your/game/executable To enable it, you can run the game from terminal with an environmental variable set: driconf in Mesa git (below The GL thread whitelist is below comment)īy default, it's off.See the example guide.īefore testing, review the list of games that are already whitelisted and don't need further testing: Bleeding edge builds for popular distributions: Some developer comments can be found at Phoronix forum.įor testing, you need at least Mesa 17.2.0 git master as of or later ( check your version). Read more at OpenGL multithreading in Mesa is ready for wider testing and Call for community testing: OpenGL multithreading is ready. Help them figure out the impact on your favorite games. This functionality is available for all Mesa drivers (RadeonSI, R600, Nouveau, Intel). The functionality is disabled by default, but games known to benefit from this feature are then whitelisted in global mesa configuration file. Mesa developers are looking for feedback about which games benefit from Mesa's glthread implementation (OpenGL multithreading), also known as threaded dispatch.
0 kommentar(er)
