PROTON_USE_WINED3D=1 %command%

Originally posted by xdshot:

PROTON_USE_WINED3D=1 %command%

As I've already stated, I've tried this command. Maybe the issue is that I use it coupled with DRI_PRIME? Or there's an issue with syntax, because I've tried both Argument1 Argument2 %command% and A1 %command% A2 %command%

Or should I restart steam after applying proton compatibility to a game?

Once again, I tried to use the command specified above with and without Prime support - no luck. Wine launches the newly installed app effortlessly.

If anyone willing to help me figure out the solution
Here's system info:
System:
Kernel: 5.4.0-193-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Xfce 4.14.2 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal
CPU:
Topology: Dual Core model: Intel Core i3-2330M bits: 64 type: MT MCP
arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17560
Speed: 990 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 884 2: 881
3: 941 4: 879
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0
Device-2: NVIDIA GF108M [GeForce GT 540M] vendor: ASUSTeK driver: N/A
bus ID: 01:00.0
Display: x11 server: X.Org 1.20.13 driver: modesetting
unloaded: fbdev,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2)
v: 3.3 Mesa 21.2.6 direct render: Yes

It seems that I currently use Nvidia390 driver, I'll try to install 340 and see if it's an issue of a version

DRI_PRIME works only on relatively recent gpus. For older you probably still need to stick to primusrun https://wiki.archlinux.org/title/Bumblebee

From what I've seen there's a threshold where that command just doesn't work for any recent Proton version, possibly due to some other hardware or software limitation, other people without Vulkan support have had the same problem whereas others also without it had it fixed with PROTON_USE_WINED3D=1 %command%

Thank you for your inputs. It still is a wonder for me why proton, being based on wine, doesn't work, but wine launches the app effortlessly. However, I also think that I should try to use proton closer to my wine version (5 something from ubuntu distro), maybe it's the issue of compatibility of later versions.

Also, it may be driver issue, because I use 390 and I've read that 390 sucks with my GPU and I should stick with 340 (even though they're probably similar).
I'll report if drivers or proton version were the issue

Funnily enough, with 340 driver steam refuses to launch. Guess it's time to do something else

Yes, it started to work.

Surely the first thing I did is to upgrade my NDriver to 390, because 340 caused my laptop crash, and it did crash Steam for that matter.

Secondly, I chose the proton version that mirrors my wine version, so no ProtonExperimental, but 5.0.

Thirdly, added argument "PROTON_USE_WINED3D=1 %command%" and it finally started to work.

The thread may be closed