AdamSzopa commented 6 years ago

Compatibility Report

Name of the game with compatibility issues: The Witness
Steam AppID of the game: 210970

System Information

GPU: Nvidia GTX 680
Driver/LLVM version: nvidia 396.54
Kernel version: 4.15.0-36-generic
Link to full system information report as Gist: https://gist.github.com/AdamSzopa/1a092acd1ba45df45a7c8891e75111e3
Proton version: 3.7-7 Beta and 3.7-6

I confirm:

[x] that I haven't found an existing compatibility report for this game.
[x] that I have checked whether there are updates for my system available.

steam-210970.log

Symptoms

Crashing after a few seconds into the game

Reproduction

I have a save game just before solving a overworld puzzle, which generates some particles, some lag and then a immediate crash.

AdamSzopa commented 6 years ago

Changed the graphic settings from high to medium let me play a few seconds longer, but it still crashes, so it's not related to this particular puzzle.

kisak-valve commented 6 years ago

Hello @AdamSzopa, can you check ulimit -Hn and confirm that it is a high value and not 4096.

ghost commented 6 years ago

17177.593:002a:0033:warn:seh:call_stack_handlers exception data not found in L"witness64_d3d11.exe"
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000140358368).
Register dump:
...

Windows has seen problems with witness64_d3d11.exe as well so it might be a game related problem although it could be Proton/DXVK does something the game doesn't like. https://steamcommunity.com/app/210970/discussions/3/458606877334668174/

The solution(s) in linked thread possibly not applicable here.

AdamSzopa commented 6 years ago

@kisak-valve my FD limit is 1048576

AdamSzopa commented 6 years ago

I also should add that I played the game some months back on the same system but using "Play On Linux" (i think that was before DXVK) and while there were some graphic issues, there were no crashes

doitsujin commented 6 years ago

Does it work with PROTON_USE_WINED3D11=1?

AdamSzopa commented 6 years ago

@doitsujin it seems to work with PROTON_USE_WINED3D11=1 . It didn't crash yet after some time of playing, but I believe my FPS went down.

LeJimster commented 6 years ago

Still works nicely for me on 3-7-6 and 3-7-7 Beta on my RX Vega 56, so it must be driver/gpu/system specific? @glubsy https://github.com/ValveSoftware/Proton/issues/344#issuecomment-418399957 has a system closest to yours that I've seen testing The Witness on here and didn't mention any crashes once they got up and running.

AdamSzopa commented 6 years ago

I managed to finish the whole game with PROTON_USE_WINED3D11=1. In this game, rendering issues could prevent you from finishing the game, since some puzzle rely on reflection, shadows, light etc.

I'm happy to report that no game breaking render issues were found. The performance was no so great, but playable for a puzzle game (could sometimes dip below 20 on my setup).

Nadrieril commented 6 years ago

I am having some game-breaking rendering issues; see here: https://github.com/doitsujin/dxvk/issues/724

kisak-valve commented 6 years ago

Hello @Nadrieril, if you're feeling adventurous, build mesa git with https://patchwork.freedesktop.org/series/50969/. The game is most likely needs this vulkan extension.

LeJimster commented 6 years ago

I'm pretty sure this title doesn't need the Transform Feedback patches. I personally haven't experienced this bug and I've completed this puzzle. The difference being I'm running an RX Vega with RADV.

ghost commented 5 years ago

The game runs well for me on Manjaro 4.14.90-1-MANJARO, Nvidia GTX 1050 driver version 415.25, with 2 exceptions:

it more often than not crashes whenever I cross the region near the bridge in the lake area;
after I start solving puzzles I can't move the cursor in the game menu and it doesn't show up in Steam overlay; if I minimize the game there is a good chance that the issue is fixed, but the mouse goes wild in game and I have to restart it.

I've tested multiple Proton releases including 3.16-6, 3.16-4, 3.7-8) These issues don't happen with PROTON_USE_WINED3D11=1, but the performance suffers a lot. I'll try and get some logs for the crashes.

Jaegrqualm commented 3 years ago

/This issue appears to be pretty dead, but I have done a little bit of testing and found some results and a tentative workaround. It appears that the crashes happen most frequently at specific locations, spots between areas. I tried walking very slowly and stopping for long periods (10-30 secs) and I managed to avoid a crash that otherwise was completely reproducible. I wouldn't know, but I would guess that there's some sort of race condition at play. As a result, at present, I believe I'll be able to finish my playthrough on Linux.

I also pulled a stacktrace pulled from stdin:

``` Installing breakpad exception handler for appid(steam)/version(1621394999) Installing breakpad exception handler for appid(gameoverlayui)/version(20210519015400) Installing breakpad exception handler for appid(gameoverlayui)/version(1.0) Installing breakpad exception handler for appid(gameoverlayui)/version(1.0) [0606/160533.457471:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer Installing breakpad exception handler for appid(gameoverlayui)/version(1.0) [0606/160533.633249:ERROR:frame_sink_video_capturer_impl.cc(206)] Invalid resolutions constraints: 0x0 must not be greater than 0x0; and also within media::limits. RecordSteamInterfaceCreation (PID 89969): SteamUtils007 / Utils wine: Unhandled page fault on read access to FFFFFFFFFFFFFFFF at address 000000014036CD70 (thread 011c), starting debugger... ERROR: ld.so: object '/home/jae/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. couldn't load main module (2) Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit c ode (0x000000014036cd70). Register dump: rip:000000014036cd70 rsp:000000000063f700 rbp:000000000063f940 eflags:00010297 ( R- -- I S -A-P-C) rax:0000000000000008 rbx:0000000009993890 rcx:00007fdabb808000 rdx:00007fdabb9a 8004 rsi:000000001e695ff0 rdi:00000000352db150 r8:ffffffffffe5fffc r9:000000000000 0000 r10:0000000000000000 r11:0000000000000008 r12:0000000000000000 r13:0000000007ec4890 r14:000000000000 0000 r15:0000000000000001 Stack dump: 0x000000000063f700: *** Invalid address 0x000000000063f700 *** Backtrace: =>0 0x000000014036cd70 (0x000000000063f940) 0x000000014036cd70: -- no code accessible -- Modules: Module Address Debug info Name (0 modules) Threads: process tid prio (all id:s are in hex) 00000020 steam.exe 00000024 0 000000bc 0 00000030 services.exe 00000034 0 00000038 0 00000044 0 00000060 0 00000078 0 00000084 0 000000a8 0 000000e8 0 0000003c winedevice.exe 00000040 0 0000004c 0 00000050 0 00000054 0 00000058 plugplay.exe 0000005c 0 00000064 0 00000068 0 0000006c 0 0000008c 0 00000194 0 000001a0 0 00000070 winedevice.exe 00000074 0 0000007c 0 00000080 0 00000088 0 00000094 0 00000098 0 0000009c 0 000000a0 svchost.exe 000000a4 0 000000ac 0 000000b0 0 000000b4 conhost.exe 000000b8 0 000000c0 explorer.exe 000000c4 0 000000cc 0 000000d8 0 000000e0 rpcss.exe 000000e4 0 000000f0 0 000000f4 0 000000f8 0 000000fc 0 >>> Adding process 90042 for game ID 210970 00000100 0 00000110 witness_d3d11.exe 00000114 0 00000118 (D) Process_00000118 0000011c 0 <== 00000120 0 00000124 0 00000128 0 0000012c 0 00000130 0 00000134 0 00000138 0 0000013c -2 00000140 -2 00000144 -2 00000148 -2 0000014c -2 00000150 -2 00000154 0 00000158 0 0000015c 0 00000160 0 00000164 0 00000168 0 0000016c 15 00000170 0 00000174 15 00000178 2 0000017c 0 00000180 0 00000184 0 00000188 0 0000018c 0 00000190 0 00000198 0 0000019c 15 000001ac 0 System information: Wine build: wine-6.3 Platform: x86_64 Version: Windows 7 Host system: Linux Host version: 5.12.6-zen1-1-zen ```

ghost commented 3 years ago

I don't get the crashes I mentioned a few years ago, with Proton 5.13-6 and a slightly better GPU, the GTX 1070. What are your specs @Jaegrqualm?

Jaegrqualm commented 3 years ago

@ceLoFaN

What are your specs @Jaegrqualm?

Sorry for the late reply, but I've been trying to investigate further. I'm running (what should be a current) Proton Experimental with an i5-8265U and Intel UHD 620, PCIE NVME storage.

The problem with this bug is that it's very localized to certain areas. Running through at full speed seems to trigger it most often, but i'm in a very late game room where it's becoming extremely annoying, and I'm not sure if I'll be able to complete it. For the curious, it's:

``` the bottom of the mountain room, stepping onto or off of the little staircase. ```

(*sorry, couldn't figue out spoilers) It still does seem to be some sort of loading bug.

Jaegrqualm commented 3 years ago

Update, finished the game, aaaaaand it crashed during the ending sequence. Isn't that lovely.

ghost commented 3 years ago

Lovely indeed. I read somewhere that the HD620 can only use about 1.7GB of RAM which is pretty close to my GTX 1050. Have you tried lower graphical settings btw?

Jaegrqualm commented 3 years ago

I've had it on low settings and dynamic resolution the whole time, only bumping up shadows to see if it would help for some puzzles.

I ended up watching a youtube video of the ending, and noticed that, even in windows, it looks like there's a lot of chugging in the exact same spots that I was having crashes. So it looks like the issue is still there in windows, it just isn't as deadly.

Jaegrqualm commented 3 years ago

Update, it appears that something changed in proton experimental. I forgot to report it at the time, so this was a month or two ago that I was playing this, but it appears that the game is appropriately stuttery and doesn't crash while doing so. So, all good on my end. The game appears to be fully functional.

ValveSoftware / Proton

The Witness (210970) crashes #1701

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction