protonscr

Warframe crashes during launch with DXVK after 24.2.X

dxvkclosed
doitsujin/dxvk#888 · opened 2019-01-26 by danielimperial · updated 2019-02-08 · 6 comments · github
1 matching comments, n / p to jump
Ddanielimperial 2019-01-26 github

Hello. At the moment of the writing, Warframe is on version 24.2.10. However, the issue with launching has begun since the 24.2 update (The Profit-Taker). I installed the game via Lutris using the GloriusEggroll script. Didn't touch nor tweaked anything: as it shipped, it launched perfectly just before this update.

Now, it's somehow not working anymore. After the update script, the game just crashes at launch. No load screen, just the standard crash report.

EDIT: The game opens up just fine without DXVK.

Software information

Warframe using Lutris and Wine64. All graphical configurations set to low. Borderless fullscreen. No additional arguments.

System information

  • GPU: Nvidia GT 750M
  • Driver: 415.27
  • Wine version: wine-4.0-rc6 (Staging)
  • DXVK version: 0.90

Apitrace file(s)

I wasn't able to create a trace. If someone could help me out on that, I'm new on this stuff, and there is no Warframe.exe.

wine64 apitrace trace -a dxgi Warframe-Launcher.bat 
000b:fixme:winediag:start_process Wine Staging 4.0-rc6 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
wine: cannot find L"C:\\windows\\system32\\apitrace.exe"

Log files

Ddoitsujin maintainer 2019-01-26 github

From your logs:

err:   DxvkSurface::getSurfaceFormats: Failed to query surface formats
err:   DXGI: DxgiSwapChain: Failed to create presenter or back buffer

This would explain the crash, but I frankly have no idea what could cause this to happen. Can you please attach the full wine log / console output?

Ddanielimperial 2019-01-27 github

Lutris output:

INFO     2019-01-27 00:02:41,434 [runner]:Runtime disabled by system configuration
INFO     2019-01-27 00:02:41,565 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/system32/dxgi with DXVK version
INFO     2019-01-27 00:02:41,589 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/system32/d3d11 with DXVK version
INFO     2019-01-27 00:02:41,604 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/system32/d3d10core with DXVK version
INFO     2019-01-27 00:02:41,604 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/system32/d3d10_1 with DXVK version
INFO     2019-01-27 00:02:41,605 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/system32/d3d10 with DXVK version
INFO     2019-01-27 00:02:41,605 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/syswow64/dxgi with DXVK version
INFO     2019-01-27 00:02:41,606 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/syswow64/d3d11 with DXVK version
INFO     2019-01-27 00:02:41,606 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/syswow64/d3d10core with DXVK version
INFO     2019-01-27 00:02:41,607 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/syswow64/d3d10_1 with DXVK version
INFO     2019-01-27 00:02:41,607 [dxvk]:Replacing /home/imperial/Games/warframe/drive_c/windows/syswow64/d3d10 with DXVK version
INFO     2019-01-27 00:02:42,142 [runner]:Runtime disabled by system configuration

Couldn't execute the updater.exe nor the Warframe-launcher.bat files with wine to catch the logs with Wine. I installed it via Lutris, so maybe that's the issue. I will try installing it via the script given within the game files and return.

EDIT: Okay, I installed using the script I mentioned before, and used the .exe available. Here goes the Wine64 output. Apparently, I opened it without the DXVK command, and it ran smoothly: however, with the no sound. I didn't change a thing on Lutris for this installation.

$ wine64 cmd /C start /b '' 'Z:\home\imperial\Games\Warframe\drive_c\Program Files\Warframe\Downloaded\Public\Warframe.x64.exe' -dx10:1 -dx11:1 -threadedworker:1 -cluster:public -language:en &> log.txt

Logfile created by wine64: log.txt

Ddebiangamer 2019-01-28 github

Latest Warframe works fine with these instructions and OS.
https://www.youtube.com/watch?v=6oMOCSqgiIU

NNeroBurner 2019-01-31 github

could you try with the standalone version from master?

?ghost 2019-02-01 github

This issue can most likely be attributed to xaudio2_7. Wine 3.19 came with a patch for xaudio2_7 "Don't return XAudio28 interface for XAudio2[0..7] objects in QueryInterface().". In my experience this solved issues in other games but left Warframe unable to launch. You can build wine staging via tkg and create your own patch with this removed, however I recommend just sicking with wine staging 3.18 for the time being. I noticed that you said you use gloriouseggroll's script but you are using wine 4, his script strictly specifies to use 3.18. You probably just updated accidentally. Hope this solves the issue.

If, after reverting to 3.18, it still crashes I would reinstall the dlls provided by gloriouseggroll. The script installs a folder called xaudio (or something similar) into Warframes directory. There should be a script in that folder that is not a dll. Execute it while setting your wineprefix variable with 'WINEPREFIX=YOUR WINEPREFIX'S ABSOLUTE DIRECTORY ./scriptname'. It should solve the issue. You could also try setting xaudio2_7 to native, builtin or builtin, native. Find what works best.

Finally, if you encounter further random crashes (not launch crashes) in the game a solution which I found worked was to delete the dxvk.cache file pre installed by gloriouseggroll's script.

The apitrace you tried to do would not have been helpful as it doesn't even get to rendering anything (so don't feel bad about stuffing it up lol). Read the bottom of this page if you need to do it again in the future: https://github.com/doitsujin/dxvk/wiki/Common-issues

For the record, Warframe works for me regardless of the update.

Just read that you got it to launch before so I shouldn't have commented most of the previous stuff, but reinstalling xaudio will likely solve your sound issue.

NNeroBurner 2019-02-08 github

@doitsujin @danielimperial I recommend closing this issue as it has nothing to do with DXVK rather with an outdated Lutris script

Launch options