vkd3d-proton icon indicating copy to clipboard operation
vkd3d-proton copied to clipboard

LEGO® Builder's Journey: Will not launch in DX12 mode.

Open Bitwolfies opened this issue 2 years ago • 6 comments

When launching from Steam, you're given 3 options, Launch as normal, "compatibility mode" (appends -dx11 to launch) and "low spec mode" (uses a separate exe and appends -dx11) yet launching normally always places the game into DX11 mode, even when DXR 1 or 1.1 is enabled. My best guess is its unable to detect DX12 support, and thus forces compatibility mode.

I suspect a workaround like the one created for Control may be needed. https://github.com/HansKristian-Work/vkd3d-proton/pull/1190

Thank you!

Bitwolfies avatar Sep 21 '22 23:09 Bitwolfies

Can you try it with a DXVK master build? It might check the feature level on a D3D11 device and DXVK has returned something <12 until very recently.

K0bin avatar Sep 21 '22 23:09 K0bin

Tried it with GE 35, which was re based from master 3 days ago, apologies if that's not the same thing.

Bitwolfies avatar Sep 22 '22 00:09 Bitwolfies

Can we please have a proton log, hardware info, driver info, literally anything that would help us debug this?

doitsujin avatar Sep 22 '22 15:09 doitsujin

https://gist.github.com/Bitwolfies/f12db2c5d7a7c5d0a304d51a08f6ea7d#file-gistfile1-txt-L47 looks questionable, seems like you're running on llvmpipe?

HansKristian-Work avatar Sep 23 '22 14:09 HansKristian-Work

I tried it. It tries creating a device but it just exits right away.

With PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_DEBUG=trace VKD3D_LOG_FILE=/tmp/lego.txt %command%

lego.txt

It creates a device, then a command queue and from there it just releases everything. Dunno really. I tried faking RENDER_PASS_TIER_2 support since it queries that struct, but doesn't change anything. I also tried VKD3D_CONFIG=dxr without 1.1, and no dice.

HansKristian-Work avatar Sep 23 '22 15:09 HansKristian-Work

Today's Proton Experimental update has enabled ray tracing. I can now see the options, turn them on, see a visual difference, and see my frame rate tank. I was able to turn on all the different options, and everything seems to work correctly. The Proton changelog doesn't note anything relevant for this release.

philipl avatar Mar 23 '23 05:03 philipl

Yes the experimental changelogs usually does not include all of the upstream changes and fixes.

Work has merged a couple of days ago so vkd3d-proton and dxvk together support D3D11On12 https://github.com/HansKristian-Work/vkd3d-proton/pull/1472 The only known problem right now afaik is that RT doesn't work on AMD RADV. But that is a driver issue.

Blisto91 avatar Mar 23 '23 07:03 Blisto91