4 ms·

> You mean Intel HD 520? Yes. Here's the output. But how do I know the game is actually using these drivers ? Also, when I tried running with proton I couldn'

> You mean Intel HD 520? Yes. Here's the output. But how do I know the game is actually using these drivers ? Also, when I tried running with proton I couldn't join any servers (insecure mode) but I suppose it's a VAC thing. $ hwinfo --gfxcard|grep Driver -n3 11- SubVendor: pci 0x1028 "Dell" 12- SubDevice: pci 0x079f 13- Revision: 0x07 14: Driver: "i915" 15: Driver Modules: "i915" 16- Memory Range: 0xee000000-0xeeffffff (rw,non-prefetchable) 17- Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable) 18- I/O Ports: 0xf000-0xf03f (rw) -- 20- IRQ: 130 (5238325 events) 21- I/O Port: 0x00 (rw) 22- Module Alias: "pci:v00008086d00001916sv00001028sd0000079Fbc03sc00i00" 23: Driver Info #0: 24: Driver Status: i915 is active 25: Driver Activation Cmd: "modprobe i915" 26- Config Status: cfg=new, avail=yes, need=no, active=unknown 27- 28-Primary display adapter: #23 and $ glxinfo | grep "OpenGL vendor" OpenGL vendor string: Intel Maybe the source engine doesn't like it. I'd have to try another game like Talos to be sure.

bogwog 5y ago
That looks like you have the right driver. It might be a source engine/porting issue then. There's not much that can be done about that, except run it under proton. However, as you said, that probably won't let you play on some servers. Have you tried running the game's benchmark with and without Proton? Disable vsync and set all the graphics settings to the same level, then see if one performs better than the other. That would at least confirm that the issue is due to a shitty port. > But how do I know the game is actually using these drivers ? I'm not expert on the Linux graphics stack, but if you see that in hwinfo, then it probably means the game is using it unless you have some funky switching setup (like Nvidia Optimus). The safest way to check be to read the game's logs, since it might print out that information (similar to the output of glxinfo). There are debugging tools like Renderdoc you can use, but that might get you VAC banned. Launching Steam through a terminal will show you the standard output of the Steam client, but idk if it also shows you the output of launched games. There's probably a way to do it.
- johnchristopher 5y ago
  Thanks for the follow-up. I'll try flatpack during the holidays but it's unlikely I'll fiddle more with it. Until I decide to finally get a musheen with a decent GPU I'll stick to windows for the little bit of gaming I do.

bogwog 5y ago

That looks like you have the right driver. It might be a source engine/porting issue then. There's not much that can be done about that, except run it under proton. However, as you said, that probably won't let you play on some servers. Have you tried running the game's benchmark with and without Proton? Disable vsync and set all the graphics settings to the same level, then see if one performs better than the other. That would at least confirm that the issue is due to a shitty port. > But how do I know the game is actually using these drivers ? I'm not expert on the Linux graphics stack, but if you see that in hwinfo, then it probably means the game is using it unless you have some funky switching setup (like Nvidia Optimus). The safest way to check be to read the game's logs, since it might print out that information (similar to the output of glxinfo). There are debugging tools like Renderdoc you can use, but that might get you VAC banned. Launching Steam through a terminal will show you the standard output of the Steam client, but idk if it also shows you the output of launched games. There's probably a way to do it.

johnchristopher 5y ago
Thanks for the follow-up. I'll try flatpack during the holidays but it's unlikely I'll fiddle more with it. Until I decide to finally get a musheen with a decent GPU I'll stick to windows for the little bit of gaming I do.