doitsujin
Fallout - New Vegas BlackScreen Issue
Software information
Name of the game: Fallout - New Vegas | Settings used: Ultra/High | Resolution: 1920:1080p
System information
- GPU: Primary: AMD RX6800XT | Secondary: Intel Arc A380
- Driver: AMD: 25.6.1 | Intel: 32.0.101.6881
- Wine version: Windows Native Non-Linux
- DXVK version: Works Fine No Issues on 2.5.3 below and does NOT work on any version after or above
Apitrace file(s)
https://mega.nz/file/q413DJKY#J_6n4sofcVz1VZq8RbQKnxzKMdMtO_WyPtHi2dWWJ0A
DXVK 2.5.3
DXVK 2.6.2
AMD is known not to work with 2.6 on many systems, it's a pretty much undebuggable issue with their driver.
Not sure if that's your problem since no long is provided, but the game works on literally everything else.
DXVK 2.6.2
If you're concerned about your A380 showing up as an AMD 6700 XT now, don't be. We're hiding/masking Intel GPUs by default for d3d8/9 titles since at the time the only Intel presence on the market were GMA iGPUs and other low end chips that games of that era supported very poorly.
AMD is known not to work with 2.6 on many systems, it's a pretty much undebuggable issue with their driver.
Not sure if that's your problem since no long is provided, but the game works on literally everything else.
Thank you for the information. Version 2.6.2 works fine with GTA IV and Dead Rising 2, but it just has issues with Fallout for some reason. I just like using the Frame Generation from AMD's Drivers via Vulkan since it is not supported with DX9. Fallout on DXVK 2.6.2 works properly for the A380 with no black screens; however, the newer 2.6.2 version for some reason has issues with my RX 6800XT on Fallout. This is not a significant problem, as I will use version 2.5.3 instead.
Log File for Both DXVK 2.5.3 and 2.6.2
The issue likely has to be fixed by AMD, which it has been reported to. The exact cause is not known.
Yeah this is the exact issue I was talking about, just swapchain creation failing for no apparent reason. I used to be able to trigger that bug on my Windows 10 install as well, but for some reason it just works now so I don't know what's going on.