Compatibility Report

Works fine with Xbox One controller. Did you check your FPS? I was stuck with 30 fps, until I changed the value of OnBatteryFramerateLimit in steamapps/compatdata/690640/pfx/drive_c/users/steamuser/Application Data/Trine4/options.txt (I'm playing on a desktop btw, not on a notebook)

steam-690640.log

Works fine with Xbox One controller. Did you check your FPS? I was stuck with 30 fps, until I changed the value of OnBatteryFramerateLimit in steamapps/compatdata/690640/pfx/drive_c/users/steamuser/Application Data/Trine4/options.txt (I'm playing on a desktop btw, not on a notebook)

Yes, my FPS are also stuck at 30 fps, until I changed the value of OnBatteryFramerateLimit and I'm playing on a desktop too.

Ok, I managed to get my steam controller working: I don't know why, but my system not load uinput module on boot, so I added uinput to /etc/modules-load.d and now the controller works. Basically
echo uinput > /etc/modules-load.d/uinput.conf and reboot (or modprobe uinput if you don't wont to reboot). However, I have played other games through Steam Proton with my controller without uinput module, with no issue, so I had never noticed that uinput was missing.

So, remains the problem of the fps limit, that seems related to an incorrect laptop mode detect, and some crashes (next time I got one, I try to post some logs).

Works fine with Xbox One controller. Did you check your FPS? I was stuck with 30 fps, until I changed the value of OnBatteryFramerateLimit in steamapps/compatdata/690640/pfx/drive_c/users/steamuser/Application Data/Trine4/options.txt (I'm playing on a desktop btw, not on a notebook)

This worked as expected for me. Something to note is that I have a UPS on my desktop. This may or may not matter.

This is how it crashes in my case

• when I start a new game: steam-690640_new_game_crash.log
• after that I can't even reach the main menu: steam-690640_cant_reach_main_menu.log

After reboot I can repeat both steps again.

Weird. Have you tried using protontricks & clearing the proton prefix

@CJ1169 I have protontricks here.
I assume you mean

Delete ALL DATA AND APPLICATIONS INSIDE THIS WINEPREFIX

from protontricks --gui. Doesn't really help. My crashes are rather hit and miss. The common pattern is that I can usually launch the game itself (where you control Amadeus) after reboot and after that if I launch the game several more times it's like I hit a wall and it keeps crashing during loadings (in the end of startup screen with a running wizard, during loading a level).

Judging by ProtonDB reports my case is somewhat special, I guess. The only thing I can think of is something Trine 4 doesn't like about GTX 770 with 2 GB VRAM but it's fine according to minimal hardware requirements.

My hardware. Game is run from SSD. Steam overlay and cloud saves are disabled.

@CJ1169 I have protontricks here.
I assume you mean

Delete ALL DATA AND APPLICATIONS INSIDE THIS WINEPREFIX

from protontricks --gui. Doesn't really help. My crashes are rather hit and miss. The common pattern is that I can usually launch the game itself (where you control Amadeus) after reboot and after that if I launch the game several more times it's like I hit a wall and it keeps crashing during loadings (in the end of startup screen with a running wizard, during loading a level).

Judging by ProtonDB reports my case is somewhat special, I guess. The only thing I can think of is something Trine 4 doesn't like about GTX 770 with 2 GB VRAM but it's fine according to minimal hardware requirements.

My hardware. Game is run from SSD. Steam overlay and cloud saves are disabled.

Yep. That's what I meant.
Its a shot in the dark, but I saw something in your logs that I hadn't seen before. Two particular failures stand out to me in that "OpenVR" failed and memory allocation failed.
Do you have a VR setup plugged in or something? Maybe some odd packages or setup? Definitely a strange case compared to other's experiences.
That's my best guess, otherwise I'm out of ideas.
Edit: I see now that OpenVR happens in all of the logs here. Something with memory allocation. You could try protontricks and changing the setting to 2GB VRAM (or 1?) for DXVK.

@CJ1169 hard to say what it's been, probably the game itself contributed to the issue too? :)
Just played for some time, loading is faster and consistently succeeds now.

@CJ1169 hard to say what it's been, probably the game itself contributed to the issue too? :)
Just played for some time, loading is faster and consistently succeeds now.

Good to hear its running, and running well at that!

Game got a lighting overhaul, so now we have these weird glitches.

here's a log
5.9-GE-7-ST: https://oreolek.ru/temp/steam-690640_5.9.log
5.0: https://oreolek.ru/temp/steam-690640_5.0.log

Proton 5.13 gives this error:

and a log: https://oreolek.ru/temp/steam-690640_5.13.log

<Comment immediately before this one>

err:   D3D11: Cannot create shader resource view:
err:     Resource type:   3
err:     Resource usage:  72
err:     Resource format: 53
err:     View format:     54
<Repeats 4 times>

Looks like the issue lies here, might want to report to DXVK issue tracker if this is on their end.

Also looks like on your proton 5.13 logs that it loads your iGPU instead of dGPU.

Seems to be fixed in DXVK a few days back: https://github.com/doitsujin/dxvk/issues/1826

I have no issues on AMD, when I force llvm instead of aco:
RADV_DEBUG=llvm %command%

I have no issues on AMD, when I force llvm instead of aco:
RADV_DEBUG=llvm %command%

I've a Radeon RX480 and also have these artifacts when i start the Game in Steam with Proton 5.13.

I would try this later, when i at home and when it's not too complicated 🙈

So, can you give a short 'How to' please? Where to use (put in) this command?

I would try this later, when i at home and when it's not too complicated 🙈

So, can you give a short 'How to' please? Where to use (put in) this command?

It's pretty easy:
Right click the game
Select Properties
In the General tab, select SET LAUNCH OPTIONS
Enter RADV_DEBUG=llvm %command%, click OK, close Properties.
Then launch the game

RADV_DEBUG=llvm %command%

Ok, i can confirm…this is working. Nice :)

The black square issue which happened only with RADV/ACO is fixed in DXVK. You need DXVK 1.7.3+ which means Proton 5.13-3+ it seems.

I confirm with Proton 5.14 works. The black square disappeared. Thank you.