julienbenjamin
commented
4 years ago I have the same error with an Nvidia GPU (RTX 2070 Super) and its proprietary driver (440.100) on Debian (kernel version 5.4.0)
Open NTMan opened 4 years ago
julienbenjamin
commented
4 years ago I have the same error with an Nvidia GPU (RTX 2070 Super) and its proprietary driver (440.100) on Debian (kernel version 5.4.0)
xythobuz
commented
4 years ago Same here on Arch Linux with kernel 5.7.7 and an Nvidia GTX 760 with driver 450.57.
qsniyg
commented
4 years ago I've drafted this patch: https://source.winehq.org/patches/data/188960 I don't have the game to test, so it might not work.
Turns out it was already in wine haha (zebediah figura already added it), I just hadn't updated my source tree.
EyesWithoutFace
commented
4 years ago ~I've drafted this patch: https://source.winehq.org/patches/data/188960 I don't have the game to test, so it might not work.~
Turns out it was already in wine haha (zebediah figura already added it), I just hadn't updated my source tree.
does that mean you got it working?
qsniyg
commented
4 years ago @yurgburg No, I have no idea if it works or not with that patch. Just that it turns out that the patch wasn't necessary, as it had already been added a few days prior to wine :) That being said, you'll still need a development build of wine (or a wine with https://source.winehq.org/git/wine.git/commit/37238a74a5fea133b8dbcf55ca62cd0d80dc49f7 patched in) in order for it to work.
EyesWithoutFace
commented
4 years ago @yurgburg No, I have no idea if it works or not with that patch. Just that it turns out that the patch wasn't necessary, as it had already been added a few days prior to wine :) That being said, you'll still need a development build of wine (or a wine with https://source.winehq.org/git/wine.git/commit/37238a74a5fea133b8dbcf55ca62cd0d80dc49f7 patched in) in order for it to work. Oh alright, do you have any idea how I could add that to my wine?
qsniyg
commented
4 years ago @yurgburg You'll need to apply this patch to the wine directory:
As to how to build it, I'm not sure, I've never built proton before (only wine), sorry! I think there are probably some guides available for that though :)
EyesWithoutFace
commented
4 years ago @yurgburg You'll need to apply this patch to the
winedirectory: PatchAs to how to build it, I'm not sure, I've never built proton before (only wine), sorry! I think there are probably some guides available for that though :)
No problem, you've given enough info to figure it out. Cheers!
xythobuz
commented
4 years ago I've tested it with the wine patch suggested by @qsniyg. I now get the error message "Death Stranding requires Windows 10 version 1809 or later".
qsniyg
commented
4 years ago @xythobuz Could you send the proton log? Alternatively, if you don't mind sending a rather large log (though it compresses very well, so please do compress it haha), run it with WINEDEBUG=+all,-heap, to get a full log, which will probably be more helpful in the not unlikely case the proton log doesn't contain enough information :)
xythobuz
commented
4 years ago Sure, there you go.
qsniyg
commented
4 years ago 6686.111:00c0:00c4:Call ntdll.RtlGetVersion(0051f880) ret=14162ef78
6686.111:00c0:00c4:Ret ntdll.RtlGetVersion() retval=00000000 ret=14162ef78
6686.111:00c0:00c4:Call user32.MessageBoxA(00000000,143761de8 "Death Stranding requires Windows 10 version 1809 or later.",143761db8 "Death Stranding",00000010) ret=14162efcf@xythobuz Could you try setting the windows version in winecfg to windows 10? (or protontricks 1190460 win10 I believe)
xythobuz
commented
4 years ago As far as I can tell (running winecfg with the run script generated in /tmp with PROTON_DUMP_DEBUG_COMMANDS), the windows version is already set to Windows 10.
As you can see in the image, the default is set to Windows 10 and the one listed applications has "Use global settings". But I also get the same error when setting the application to Windows 10 explicitly, too.
qsniyg
commented
4 years ago @xythobuz Could you check if the following patch fixes it?
diff --git a/dlls/ntdll/version.c b/dlls/ntdll/version.c
index 4fef2b5e43..1c8fe83ffb 100644
--- a/dlls/ntdll/version.c
+++ b/dlls/ntdll/version.c
@@ -181,7 +181,7 @@ static const RTL_OSVERSIONINFOEXW VersionData[NB_WINDOWS_VERSIONS] =
},
/* WIN10 */
{
- sizeof(RTL_OSVERSIONINFOEXW), 10, 0, 0x42EE, VER_PLATFORM_WIN32_NT,
+ sizeof(RTL_OSVERSIONINFOEXW), 10, 0, 0x4A61, VER_PLATFORM_WIN32_NT,
{0}, 0, 0, VER_SUITE_SINGLEUSERTS, VER_NT_WORKSTATION, 0
},Edit: And Zebediah is one step ahead of me again haha: https://source.winehq.org/patches/data/188498 and https://source.winehq.org/patches/data/188499 (I don't think the second patch should be necessary for getting death stranding running, but it shouldn't hurt to apply either).
I'm guessing he was probably given an early build of the game, considering both these patches and the one before were written a week ago at about the same time.
xythobuz
commented
4 years ago I tried both your patch and also the two patches you've linked. They don't fix the issue, I still get the same message as above. Here are the logs with the two patches from Zebediah.
qsniyg
commented
4 years ago ``` diff --git a/dlls/ntdll/version.c b/dlls/ntdll/version.c index 1c8fe83ffb..6984cfb74f 100644 --- a/dlls/ntdll/version.c +++ b/dlls/ntdll/version.c @@ -585,6 +585,11 @@ NTSTATUS WINAPI RtlGetVersion( RTL_OSVERSIONINFOEXW *info ) info->dwMinorVersion = current_version->dwMinorVersion; info->dwBuildNumber = current_version->dwBuildNumber; info->dwPlatformId = current_version->dwPlatformId; + ERR("dwMajorVersion=%i, dwMinorVersion=%i, dwBuildNumber=%i, dwPlatformId=%i\n", + info->dwMajorVersion, + info->dwMinorVersion, + info->dwBuildNumber, + info->dwPlatformId); wcscpy( info->szCSDVersion, current_version->szCSDVersion ); if(info->dwOSVersionInfoSize == sizeof(RTL_OSVERSIONINFOEXW)) { ```
xythobuz
commented
4 years ago Ok, here you go:
a0kami
commented
4 years ago Hey there! From your log:
dwBuildNumber=17134
Somehow the value returned still matches the value 0x42EE. Was the change taken into account ? (I believe that version.c patch didn't make it yet in the wine source tree)
xythobuz
commented
4 years ago I was worried about that, but I took extra care to do a full rebuild in the vagrant VM (deleting the build folder) and made sure the change is in the source tree of the wine subdirectory inside the VM.
What am I missing? How can I force a rebuild of wine? I was just expecting that deleting the build folder would be enough.
Edit:
See the screenshot below, the changes are there. Also, I can see the log-output from the ERR(...) call added by @qsniyg, and if this has been compiled in then the other change has been compiled in as well, for sure!
47468.831:003c:0040:err:ver:RtlGetVersion dwMajorVersion=10, dwMinorVersion=0, dwBuildNumber=17134, dwPlatformId=2
qsniyg
commented
4 years ago @xythobuz Ahhh right, the issue (I believe) is that the registry hasn't been updated yet. Could you run the winecfg command again, set it to windows 7, click apply, then set it to windows 10, then click apply again? In theory this should update the build number (I should probably note that zebediah's second patch is likely required for this to work).
0f3b79350c99d
commented
4 years ago Not the one you were asking, but after many failed attempts I simply edited registry file in proton pfx (steamapps/compatdata/1190460/pfx/system.reg)
"CurrentBuild"="19041"
"CurrentBuildNumber"="19041"I probably need to attach long log file, but haven't figured how to create it through steam yet.
(probably need to think about building wine with d3d12? Or it's too soon to do that?)
qsniyg
commented
4 years ago @0f3b79350c99d Thank you! To create a log file, prepend: PROTON_LOG=1 to the game's launch arguments. Since it crashes on __wine_spec_unimplemented_stub, I'm pretty sure a full log (WINEDEBUG=+all,-heap) won't be required, we only need to know which function needs to be stubbed out and/or implemented :)
theo-meow
commented
4 years ago @qsniyg Not the other guy but I did the same thing, got the same error and here is the proton log: steam-1190460.log
qsniyg
commented
4 years ago @0none Huh, the unimplemented_stub thing doesn't show up in the log (and unfortunately it doesn't appear like any relevant information as to what caused the crash is displayed, at least from a quick glance):
Can you submit a full log then? (PROTON_LOG=1 WINEDEBUG=+all,-heap) Remember to compress it after, otherwise it might be quite big haha :)
theo-meow
commented
4 years ago @qsniyg Sorry for the long delay I could not get it to compress smaller than 20 MiB. Original Log file is about 900 MiB. I have created a repo for the files now as a work around: https://github.com/0none/FileDump
xythobuz
commented
4 years ago I also get the same error message. Here are my logs:
qsniyg
commented
4 years ago 11335.933:00b8:00bc:trace:dxgi:dxgi_output_QueryInterface iface 0x9f3fc0, iid {068346e8-aaec-4b84-add7-137f513f77a1}, object 0x51e4b8.
11335.933:00b8:00bc:warn:dxgi:dxgi_output_QueryInterface {068346e8-aaec-4b84-add7-137f513f77a1} not implemented, returning E_NOINTERFACE.
11335.933:00b8:00bc:trace:seh:raise_exception code=c0000005 flags=0 addr=0x14174e0d8 ip=14174e0d8 tid=00bcSeems like IDXGIOutput6 (DXGI 1.6) needs to be implemented for this to work. From a quick grep in the wine source tree, it seems like it's not implemented yet. It appears to be implemented in DXVK, but it won't be of much help for us (other than an implementation reference I guess), since it doesn't work with vkd3d, which is needed for dx12.
theo-meow
commented
4 years ago So that means there is nothing left to do but wait for it to be implemented in Wine? Or, at least for me, since that task is vastly outside of my abilities.
qsniyg
commented
4 years ago @0none
Here's a completely untested patch to stub out support for DXGI 1.6: https://gist.github.com/qsniyg/84550f4421c8ee3ff4134ca07d4ad398 (note that I have absolutely zero knowledge about anything relating to directx, I just basically copied what I saw done for DXGI 1.4)
I would be very surprised if it were to actually work, but I guess it's worth a shot :) If it doesn't, please attach a log anyways, it might be possible that we'll be able to progress a bit further.
aeikum
commented
4 years ago Hello. The next branch of the Proton app in the Steam client is now available. Death Stranding is playable on this branch. Please see issue #4070 for more details.
EyesWithoutFace
commented
4 years ago Yo?! Is this true
On Wed, Jul 15, 2020, 16:04 Andrew Eikum notifications@github.com wrote:
Hello. The next branch of the Proton app in the Steam client is now available. Death Stranding is playable on this branch. Please see issue
4070 https://github.com/ValveSoftware/Proton/issues/4070 for more
details.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4069#issuecomment-659058750, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFLFPNSEVPS4RITFPZYF3JLR3YYW3ANCNFSM4OZUFSMQ .
theo-meow
commented
4 years ago @aeikum The branch is not showing up for me, even after restarting steam. Do I need to refresh the list manually? @qsniyg The patch is giving me errors at dlls/dxgi/dxgi_private.h:144 and dlls/dxgi/output.c:569. On what wine branch are you?
qsniyg
commented
4 years ago @0none Ah sorry, it's written against https://github.com/wine-mirror/wine/commit/54b2a10659871032720df31ae9ca6cba2ff4acf0. If you want to compile from scratch, I'd say just compile https://github.com/ValveSoftware/Proton/tree/proton_5.0-next instead :) (the next branch aeikum mentioned above)
theo-meow
commented
4 years ago I am compiling that right now and will be reporting shortly :wink:
Funny that, I was just pulling proton when the new branch popped up. "Huh, what's that all about?"
Edit: Compiling fails and it's late, I take the "shortly" back
EyesWithoutFace
commented
4 years ago It does work with the proton 5.0 -Next branch. Playing it right now 144fps
0f3b79350c99d
commented
4 years ago It does build (if it fails -- did you update submodules after switching branches/recreate vagrant? git submodule update --init --recursive)
However it does crash with this message: Error initializing rendering configuration, check video card and drivers\n\nThe details of the error are output in error.txt..
Is there a minimum version of nvidia drivers? Currently I have 435.
Edit: nevermind, I actually read in the link above that I need at least 440 or 450.
a0kami
commented
4 years ago I got to the point of building proton with the patches @qsniyg proposed and got to the same crash.
Hopefully the recent changes on the next branch of Proton 5 on the steam client announced by @aeikum, let me play the game 3 hours straight through a few chapters. Stutters as hell to initially compile shaders but then it's pretty smooth except some massive loading times, if it looks like it froze, give it time, be ex-tre-me-ly patient, you likely ran out of memory but the game will catch up. This sometimes can cause some brief audio buffers corruption.
SevgiZ
commented
4 years ago I just tested the game for roughly an hour with 5.0-10 RC, I could launch the game and start playing but there are some major issues.
### System information:
Crash logs: President cutscene: https://gist.github.com/SevgiZ/db2b351cb54e783b171c628b69131321
Options menu: https://gist.github.com/SevgiZ/8d5a10d4186b947baf52cdfdec96e5b6
Hopefully I'm not missing anything, I'm pretty new to this stuff
   
EyesWithoutFace
commented
4 years ago I actuslly dont have any of these issues when I play and I played for 3 hours straight. Only stuttering I saw was in the beginning and nothing since
NTMan
commented
4 years ago With 5.0-10-rc2 working flawlessly on my hardware in 4K with maximum graphics quality. steam-1190460.log
  
Undeadhunter
commented
4 years ago I also am getting the random flying textures. Playing on Medium settings.
Edit: restarting game solved it. I think it has to do with changing the settings.
doitsujin
commented
4 years ago @NTMan on screenshot no. 2 you can see some sky rendering issues; that's a known problem with RADV at the moment.
Herbstein
commented
4 years ago I run into the game visuals freezing after making the first delivery. The cutscene continues but the visuals are completely frozen. If I force-close the game and try pressing "continue" in the game the loading screen too freezes. If I on the other hand load an autosave from just before making the delivery, the game again freezes during the cutscene. My thinking is that something in the next area is being loaded, and the game doesn't like something about it.
Update: gave it another try and this time it didn't freeze. I avoided touching any input this time, but don't know if it's related or a coincidence.
theo-meow
commented
4 years ago The game seems to be launching fine now, but after a few minutes of gameplay it seems to freeze and not recover. Sound is unaffected. steam-1190460.log
Edit: Game seems to freeze pretty much instantly if I attach a controller for some reason. The log above has no controller.
The log doesn't really update at the time of the freeze, and my GPU seems fine (using radeontop for monitoring).
theo-meow
commented
4 years ago Regarding my last comment:
I switched from KDE Plasma to openbox, just to check, and the game lasted a lot longer. I was actually able to complete the first mission playing on default settings. So for me, it surely has to do with either me DE or Hardware consumption (memory maybe?)
lanceturbes
commented
4 years ago I'm seeing the exact same stuff that @SevgiZ mentioned and showcased in those screenshots: floating rocks, patches of grass in the sky, invisible walls, etc. Performance is close to 40% of Windows (doesn't bother me too much, though). Running the latest NVIDIA drivers on Arch Linux, with the current latest stable kernel (5.7.8), GTX 1070, 16GB DDR4, AMD Ryzen 5 1600.
0f3b79350c99d
commented
4 years ago First of all want to say thank you to everyone involved, it's incredible to be able to play DS two days after release. Thank you for your hard work!
Game runs okay, in 4k, without crashes. Occasionally I see random chunk of stone textures in the sky.
Performance, however, could probably be better: ryzen 3900x, gtx1080ti, 2160p resolution, 450.57 driver, fps bounces between 30 and 40 fps. Occasional drops down to 1 fps, audio is not affected. Driver issue? Proton/wine implementation issue? It's not gamebreakingly bad though for me.
MilesRdz
commented
4 years ago I'm finding that the game tends to freeze when I start a new game and I'm prompted to change brightness settings. error.log steam-1190460.log system specs.log
theo-meow
commented
4 years ago Hello again, I am getting a consistent crash on the same cutscene, regardless of DE used. The cutscene shortly after the opening Title where Porter falls into a body of water crashes after exactly 3 seconds. It ends up killing my Xorg and ending my user session.
No Idea if this is a game Issue or my drivers, but maybe someone else understands the logs better than me.
If I read this correctly, the game somehow causes my GPU (5700XT) to crash, my GPU tries to recover and kills Xorg in the process.
NalianNalis
commented
4 years ago ``` Build : dso 102/1901735 22:46 - Thu Jul 16 2020 Internal system error occured. An Access Violation (C0000005h) has occurred in thread 'Background 4' at instruction location 00000001416A1C35h CallStack : 3932796059 0. 0x00007BCDB36E NtRaiseException 1. 0x00007BCD458A raise_func_trampoline 2. 0x0001416A1C35 ds, 0x416A1C35 3. 0x00014173DBE5 ds, 0x4173DBE5 4. 0x000141700A65 ds, 0x41700A65 5. 0x0001417525F1 ds, 0x417525F1 6. 0x0001487537DF ds, 0x487537DF 7. 0x00014183F59C ds, 0x4183F59C 8. 0x00014183A45D ds, 0x4183A45D 9. 0x000141838E4C ds, 0x41838E4C 10. 0x0001417B0B74 ds, 0x417B0B74 11. 0x0001417B0C6D ds, 0x417B0C6D 12. 0x0001417B1C9B ds, 0x417B1C9B 13. 0x0001417AD08D ds, 0x417AD08D 14. 0x00007BCD6BDD DbgUserBreakPoint 15. 0x000000000000 16. 0x0001417ACF80 ds, 0x417ACF80 17. 0x0789E68125E0 18. 0x000000000000 RAX = f1c30290 RBX = f1c30290 RCX = 4d0f4f8 RDX = 8f3fe720 RSI = 0 RDI = f1c50660 R8 = 0 R9 = 0 R10 = 550000 R11 = 0 R12 = f2450088 R13 = e69c4090 R14 = 0 R15 = 1 RIP = 416a1c35 RSP = 4d0f4d0 RBP = 4d0f5b9 EFL = 10206 Dx12-ErrorCode : 0x80004005 DeviceRemovedReason: 0x0 VMEM: Used 0.00 MB / Budget 8192.00 MB VMEM: Video 8192.00 MB / Shared 8009.63 MB / System 0.00 MB MEM: Used 4569.70 MB / Total 16019.25 MB 0. 0x0001417C0068 ds, 0x417C0068 1. 0x0001417C1F41 ds, 0x417C1F41 2. 0x0001417C2256 ds, 0x417C2256 3. 0x00007BC776AB __wine_spec_unimplemented_stub 4. 0x00007BCDAF72 RtlVirtualUnwind 5. 0x00007BCDB36E NtRaiseException 6. 0x00007BCD458A raise_func_trampoline 7. 0x0001416A1C35 ds, 0x416A1C35 8. 0x00014173DBE5 ds, 0x4173DBE5 9. 0x000141700A65 ds, 0x41700A65 10. 0x0001417525F1 ds, 0x417525F1 11. 0x0001487537DF ds, 0x487537DF 12. 0x00014183F59C ds, 0x4183F59C 13. 0x00014183A45D ds, 0x4183A45D 14. 0x000141838E4C ds, 0x41838E4C 15. 0x0001417B0B74 ds, 0x417B0B74 16. 0x0001417B0C6D ds, 0x417B0C6D 17. 0x0001417B1C9B ds, 0x417B1C9B 18. 0x0001417AD08D ds, 0x417AD08D 19. 0x00007BCD6BDD DbgUserBreakPoint 20. 0x000000000000 21. 0x0001417ACF80 ds, 0x417ACF80 22. 0x0789E68125E0 23. 0x000000000000 ```
Compatibility Report
System Information
I confirm:
steam-1190460.log
Symptoms
The game crashed with an error message:
ERROR: Failed to load api-ms-win-core-systemtopology-l1-1-0.dll.Reproduction
Just launch the game.