Vain Riser

protonopen appid 1059850Game compatibility - Unofficial

ValveSoftware/Proton#4482 · opened 2020-12-19 by Seng-Jik · updated 2020-12-20 · 4 comments · github · game page · search this game

SSeng-Jik 2020-12-19 github

Compatibility Report

Name of the game with compatibility issues:Vain Riser
Steam AppID of the game:1059850
This game is still developing, this report was reported by game developer.

System Information

Gist:https://gist.github.com/Seng-Jik/5c4f1558c2611922a53b8eabb2d1b9a5

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.

Symptoms

This game is working on Windows 7 fine, and this game is only support D3D11(Feature Level:D3D10_0).
Using Windows 8.1 SDK, Visual Studio 2019, MSVC 14.28.

call SteamAPI_Init
call SteamUtils()->SetOverlayNotificationPosition
call SteamUserStats()->RequestCurrentStats
Load save data from Steam Cloud API
call Steam Remote Play apis for preparing Steam Remote Play
CoInitializeEx
Imm32.dll --> ImmDisableIME
Create Window
- CreateWindowEx
- RegisterTouchWindow (failed, but ignored)
- Hacking WM_SIZE and WM_SIZING
Create D3D SwapChain and D3D11Device
- Source Code: https://github.com/Strrationalism/Snowing/blob/VainRiserProject/WindowsImpl/D3DDevice.cpp (Line 12 ~ Line 136)

If PROTON_USE_WINED3D is enabled.

Broken in Line 101 with no message.
Logs: WINED3D_ENABLED.log

If PROTON_USE_WINED3D is disabled.

D3DDevice create failed with HRESULT=0x80004005(DriverType = REFERENCE)
Hardware and WARP device create failed.
Logs: WINED3D_DISABLED.log

Reproduction

Kkisak-valve maintainer 2020-12-19 github

Hello @Seng-Jik, Proton uses DXVK to translate DirectX 9, 10, and 11 into Vulkan. Your virtual machine setup does not support Vulkan which is why the game fails to initialize with:

err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3

PROTON_USE_WINED3D=1 tells Proton to use wine's DirectX to OpenGL render path, however, this is not considered supported. You'll need to reproduce your issue with that in a vanilla wine setup and report any issues you encounter with that to the upstream wine bug tracker. That said, fixme:winediag:wined3d_select_feature_level None of the requested D3D feature levels is supported on this GPU with the current shader backend. is most likely from the virtual machine only supporting OpenGL 3.3.

SSeng-Jik 2020-12-20 github

Hello @Seng-Jik, Proton uses DXVK to translate DirectX 9, 10, and 11 into Vulkan. Your virtual machine setup does not support Vulkan which is why the game fails to initialize with:
err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3
PROTON_USE_WINED3D=1 tells Proton to use wine's DirectX to OpenGL render path, however, this is not considered supported. You'll need to reproduce your issue with that in a vanilla wine setup and report any issues you encounter with that to the upstream wine bug tracker. That said, fixme:winediag:wined3d_select_feature_level None of the requested D3D feature levels is supported on this GPU with the current shader backend. is most likely from the virtual machine only supporting OpenGL 3.3.

Thank you!
Now I install Ubuntu to my real PC(support to OpenGL 4.6), and when I using PROTON_USE_WINED3D, the game will run perfectly, but if I don't use PROTON_USE_WINED3D, the game will stay in a black scene and look like paused.
steam-1059850.log

Is this a bug?

SSeng-Jik 2020-12-20 github

Another problem, when I import SteamLibrary(in a NTFS file system partition) that contains my game, and run it in Proton, the function SHGetKnownFolderPath will failed.
Now I fixed this bug through remove Proton and game and reinstall them into default SteamLibrary(and remove another SteamLibrary).

Kkisak-valve maintainer 2020-12-20 github

I took a look at the log, but unfortunately, I don't see an obvious hint as to what happened there. Proton interacting with NTFS is known to be finicky.