You are not logged in.
This is obviously for games that have no Linux native version and therefor must be installed and/or played using their windows binary via WINE.
I use the latest nvidia DKMS binaries and latest intel drivers coupled with bbswitch, optirun and primusrun to accomplish the majority of my Windows based gaming needs;
I use the wine-d3dstream-git package for my gaming wine setup, and it is coexisting hapily with wine-silverlight used for the pipelight implementation.
If I simply "primusrun steam" or "primusrun glxspheres" cat /proc/acpi/bbswitch returns "ON" after closing the application cat /proc/acpi/bbswitch returns "OFF"
Similarly, if I primusrun the windows versionf of steam via primusrun wine /path/to/steam.exe - bbswitch returns on. However, when I launch a game from that steam instance, I experience the same relatively performance and graphical errors I do with the Intel chipset.
I have tried running steam without primusrun, and then running the game binary directly with Primusrun - this yields bbswitch with a value of "OFF" - probably because running the game binary just calls Steam to relaunch itself.
What would be the best way to run a Windows game on Windows steam using bumblebee? How can I ensure that the game is launched utilizing the nvidia GPU?
Offline
primus needs /usr/$LIB/primus to be present in LD_LIBRARY_PATH environment variable. You can check that by running
tr \\0 \\n < /proc/PID/environ | grep ^LD_(try substituting process IDs of Steam, the game, and wine-server in place of PID)
You can also try
sudo fuser -v /usr/lib*/primus/libGL.so.1to see which processes have primus' library loaded.
I can't give a complete explanation, but maybe you have wine-server already running prior to launching Steam, or somehow LD_LIBRARY_PATH gets reset along the way.
You can try libgl-switcheroo (see the Bumblebee article on the wiki), but as it also works via LD_LIBRARY_PATH, you may see the same problem.
Offline