While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
-
SteamVR Beta gets Linux fixes, plus Beta updates for De…
- Eike -
SteamVR Beta gets Linux fixes, plus Beta updates for De…
- melkemind -
Ubuntu 24.04 LTS (Noble Numbat) is now available
- Eike -
SteamOS 3.5.19 for Steam Deck out now for everyone
- Pengling -
SteamVR Beta gets Linux fixes, plus Beta updates for De…
- psycho_driver - > See more comments
Latest Forum Posts
- Free Steam Keys!
- robvv - Hello to all
- JordanBurton - New Desktop Screenshot Thread
- goule - Introduce Yourself!
- goule - Fairtris 2
- wvstolzing - See more posts
View PC info
Set the environment variable before launching the game. I launch it from the terminal, so for me it looks like:
DXVK_HUD=1 wine_dir=wine-vulkan ./the_witcher3.sh
But that uses a bunch of my own scripts inside. How are you launching the game?
Example of the above script:
the_witcher3.sh
#!/bin/bash
mesa=${mesa:-true} # use custom built mesa
hud=${hud:-false} # use GALLIUM_HUD
export wine_dir=${wine_dir:-"wine-master"}
export mesa_dir=${mesa_dir:-"mesa-master"}
if $mesa; then
mesa_run="mesa_run.sh "
fi
if $hud; then
hud_run="gallium_hud.sh "
fi
export WINEPREFIX=/opt/games/wine/prefixes/witcher3
export mesa_glthread=true
export WINEDEBUG=-all
cd $WINEPREFIX/drive_c/the_witcher_3/bin/x64
${hud_run}${mesa_run}wine_run.sh witcher3.exe #&>wine_run.log
View PC info
wine_env.sh - Environment setting script.
wine_run.sh - Wine launcher that uses wine_env.sh.
winetricks_run.sh - winetricks launcher that uses wine_env.sh.
mesa_run.sh - script to use custom Mesa.
You can get the idea from it, how to run custom Wine + custom prefix + custom Mesa.
View PC info
I still sometimes use POL to install things since it has a nice UI for creating desktop launchers. But I prefer my scripts when I need more flexibility, and cases like testing TW3 with tons of different settings and environments is just such case.
View cookie preferences.
Accept & Show Accept All & Don't show this again Direct Link
There was only one or two times I used custom scripts to launch a game since I have q4wine.
View PC info
POL does all that too. But with scripts it's just faster to do and edit in place. Besides, I'm gradually trying to get rid of applications that are stuck with GTK2 and Qt4 with no hope of getting any updates. It's another motivation for me to replace POL.
Back to 60% because the optimization turned out to be broken for (most) other games.
Played with high settings on 2560x1080 fullscreen. I get more stable fps. With wine staging my fps dipped sometimes in towns under 20 fps, now I am around 35-40. No freezes, no texture glitches on underground. Rotfiends looks strange - like a box of triangles. But really good playable. Played for 2 or 3 hours in Blood and Wine. Quite impressed from dxvk.
View PC info