Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Void (37000) #4527

Open
2 tasks done
mz1193 opened this issue Jan 3, 2021 · 4 comments
Open
2 tasks done

The Void (37000) #4527

mz1193 opened this issue Jan 3, 2021 · 4 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues

Comments

@mz1193
Copy link

mz1193 commented Jan 3, 2021

Compatibility Report

  • Name of the game with compatibility issues: The Void
  • Steam AppID of the game: 37000

System Information

(Note: none of this is particularly relevant to the bug, because this occurs regardless of system or Proton/WINE version)

  • GPU: RX 560 X
  • Driver/LLVM version: Mesa 20.2.6
  • Kernel version: 5.9
  • Proton version: Any

I confirm:

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

Symptoms

The game appears to work perfectly until you get to the second sister's chamber. No matter what, upon walking through the room, the game will crash to desktop. This happens regardless of settings, regardless of hardware, regardless of Proton version, regardless of vanilla WINE version, etc. It has also been reported about at WineHQ over the years, but it seems like either nobody can figure out why this is occurring or there's no active work being done to remedy it.

On the WineHQ page, reports have listed "Unhandled page fault on read access to 0x00000000 at address 0x1953eb7" as the relevant error message connected to this issue.

Link to WineHQ bug report

Reproduction

Install The Void, play until you reach the second sister's chambers, and walk through the room. Use any Proton or WINE version you'd like, on any hardware you have, and you'll see the same crash to desktop result.

@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Jan 3, 2021
@kisak-valve kisak-valve changed the title The Void The Void (37000) Jan 3, 2021
@gofman
Copy link

gofman commented Jan 7, 2021

Could you please upload a game save near to the problem and exact instructions how to reproduce it? The game save files are in /steamapps/compatdata/37000/pfx/drive_c/users/steamuser/My\ Documents/My\ Games/Void/Savegames/

@mz1193
Copy link
Author

mz1193 commented Jan 7, 2021

Could you please upload a game save near to the problem and exact instructions how to reproduce it? The game save files are in /steamapps/compatdata/37000/pfx/drive_c/users/steamuser/My\ Documents/My\ Games/Void/Savegames/

Attached is the save file. In this game, you can only save on the void (map) screen, so upon loading you must click on the sphere that your character is currently on to load the problematic area. Once you're inside, walk forward and explore the room, it will most likely crash somewhere around the couch/cushions. If not, it will eventually crash the longer you linger in the room. A similar problem occurs if you are to travel on the map to Uta's Chambers over toward the left, but my save may not have enough health to make the journey without picking up more color along the way, as a forewarning. The difference with Uta's Chamber is that the game instantly CTDs when attempting to enter the area.

I hope this is helpful. Thank you for looking into it.
thevoidsave.zip

@gofman
Copy link

gofman commented Jan 7, 2021

Thanks! I see what issue is about. This is the first game I see which depends on d3d9 shader validator interface actually validating the shaders, just returning 'ok' from IDirect3DShaderValidator9::Instruction (like both Wine's d3d9 and dxvk currently do) is not enough. I am going to prepare some more or less sensible patch for that soon.

Just in case you are willing to continue playing the game sooner and are ready to build Proton for that I can attach my ugly debug patch which seems to fix the crashes.

@mz1193
Copy link
Author

mz1193 commented Jan 7, 2021

Thanks! I see what issue is about. This is the first game I see which depends on d3d9 shader validator interface actually validating the shaders, just returning 'ok' from IDirect3DShaderValidator9::Instruction (like both Wine's d3d9 and dxvk currently do) is not enough. I am going to prepare some more or less sensible patch for that soon.

Just in case you are willing to continue playing the game sooner and are ready to build Proton for that I can attach my ugly debug patch which seems to fix the crashes.

Fantastic! Congratulations on finding out what was causing this, I'm sure it will make a few people happy.

And thanks for the offer about the patch. I'd really like to finish this game at some point, but I have other things on my to-do list at the moment, so I'm more than happy to wait for the patch to be merged. You may want to consider attaching it anyway though, just in case any other user stumbles across this report and would like to play.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues
Projects
None yet
Development

No branches or pull requests

3 participants