Disregarding the launcher thing, the game seems to deadlock shortly after starting in D3D12 mode anyway.

Here's my log with VKD3D_DEBUG=trace from my Wine prefix (using wine-staging-protonified-tkg-git 5.22.r10.g2a073f33): Warframe.x64-1607039127.log.gz

I'll try to record an apitrace from a W10 machine sometime tomorrow in case this is not enough to figure out what's wrong.

Not sure if our bug or not.

Right, might as well be a Wine bug or some D3D12–specific game bug (after all, devs warned that D3D12 support is in unstable beta). Fwiw, D3D11 mode has no such issues. I'll try with vkd3d on Windows too maybe.

Doesn't help that the game is such a massive pain in the arse to get running, so trying to reproduce that is going to be all sorts of "fun". I never managed to make the game work even with D3D11.

That's… interesting. I haven't had any issues with Warframe in D3D11 mode since forever (except maybe the Launcher being unable to tell the exact progress of ongoing game update process). Nowadays I can get a working setup just by creating a new prefix, installing DXVK and wine msiexec /i Warframe.msi. Proton-GE also worked for me out of the box with Steam version a few months ago.

steam-230410.tar.gz

Here is an apitrace recorded on W10 while using native D3D12:
https://drive.google.com/file/d/1kRdnu09JomKP8BtLfLwg3OHY5g6IkofK/view

Here is log file created when trying to run the game with vkd3d-proton on W10 (game crashes instead of deadlocking):
https://drive.google.com/file/d/1RqstsnMUeMhTWf_Y-yiybEDzyBJXtrN9/view

Same build as yesterday, older hardware.

Doesn't help that the game is such a massive pain in the arse to get running, so trying to reproduce that is going to be all sorts of "fun". I never managed to make the game work even with D3D11.

This is very strange to hear. I have never had any issues with Warframe at all using DX11 on Steam. This is my third PC I have it installed on and my partner also plays it on her Manjaro setup. The only quirk is that the updater sometimes says "Checking for updates" or "Checking for new content" when it's actually busy downloading stuff. Just let it finish and it works.

i'm trying to test Warframe under DX12 with VKD3D-Proton but i can't do warframe launcher detect DX12 support.

You'll need to make sure that your wine prefix is set to Windows 10, and some games require Feature Level 12_0 which we currently cannot support on RADV (VKD3D_FEATURE_LEVEL=12_0 might work around that, might also end up not working at all).

also turn off "Launcher GPU Acceleration"

it looks like Warframe is working fine in fullscreen mode

if the selection list for the graphic renderer is empty, turn off "Launcher GPU Acceleration" and restart the launcher.

Don't use wine-staging 6.7 - dx12 is not showing as an option when you use that release (with 2.2 or 2.3 vkd3d).

https://bugs.winehq.org/show_bug.cgi?id=51062

@RSerejo Friendly ping.
Am i correct in assuming that this issue was solved?

@Blisto91 working very well, even without full screen, Proton GE 7.48.

not sure if it's me, but even with VKD3D_FEATURE_LEVEL=12_0 on lutris, it doesn't seem to work. steam as well.

What is your dxvk and vkd3d-proton version and GPU and driver?
Or post a Proton log

dxvk v2.2, vkd3d v2.9, gpu is rx 580, mesa v23.1.3

now that I'm looking at it, though, mesa on gentoo has the USE_EXPAND for VIDEO_CARDS d3d12. i wonder if i would need to compile with that USE flag as well. i'll give it a try.