Since you're already using debug layers, please post the full console output which contains the output from those debug layers.
Yup sorry about that.
Using 8dfe708 fixed that color problem with the new compiler.
This error is weird and makes no sense to me:
DS(ERROR): object: 0x2290 type: 27 location: 9212 msgCode: 108: vkAcquireNextImageKHR: Application has already acquired the maximum number of images (0x1)
Does that also show up with the old driver? If so, I need an apitrace to debug the issue.
I couldn't get apitrace to work with wined3d is a trace with DXVK useful?
https://send.firefox.com/download/2eb3482310/#KB1lAQ2Pmn4LOB9kwOlyTw
looks somewhat similar to a tekken 7 issue where colors are all weird.
Ok so this might not be a driver problem like we thought. I think it might be related to fullscreen mode. 390.48 was also hanging until I turned off fullscreen in the config file.
GstRender.FullscreenEnabled 1
Looks like it. 396.18 runs in windowed mode.

Fullscreen works if enabled through the game but hangs upon relaunch.
Still hangs with 2566457
Can you post a new log with debug layers enabled?
Anyway, if that commit doesn't help, I don't think I will be able to fix this issue, sorry.
I noticed doing alt+enter does some weird things. When GstRender.FullscreenEnabled is set to 1 the game starts off in windowed mode and switches to full screen so could that be related?
https://www.youtube.com/watch?v=vSY0Efi28ys
Anyway here are the debug files:
Can you test if it works with bb3e3c9e4f15e5232d1a60ffbda00d9fd55064c4? It should now report display resolutions correctly, which has been an issue for some games before.
Still freezes with that commit.
Can you restest with latest master ?
Still freezes with 4c298d4 and still doesn't stay open when not using virtual desktop. However it places my cursor on the top-left of the screen now.
Please re-test with 62e4c867ec55da8feda277140cf21c43503aeb43.
Just posting here for people not following on Discord. No that commit did not work.
I searched this repo for "NFS" and this issue was what I found.
Same, if not similar things happen to me with both NFS The Run and NFSMW2012
Trying to play them in fullscreen mode without any special configuration either makes the screen go full black, makes it flicker or turns it off.
Using DXVK_DEBUG_LAYERS=1 makes the games play properly in fullscreen mode.
I have a laptop with a vega 8 igpu, though, and I'm on Fedora 32
Using DXVK_DEBUG_LAYERS=1 makes the games play properly in fullscreen mode.
That environment variable does nothing unless you're using DXVK versions that are 2 years old.
hmm, it seems i was mistaken...
I've tested the Steam release of this game on an Nvidia GTX 1060 (455.23.04) with Wine and DXVK's DXGI and both were able to launch in Fullscreen mode (without any launch options) on Proton 5.13-1 (DXVK 1.7.2).
The game does have several issues with focus (Title minimizing at launch when launched in Fullscreen, Requires several attempt to maximize back to Fullscreen from the dock / minimized state, Window resizing to a 1x1 window on focus loss...), but nothing that prevents the game from being played. These same issues have also been noticed on several other NFS games and other EA / Origin titles released on Steam.
proton 5.13-1x1 2020-10DXVK_DEBUG_LAYERS=1x2 2020-06DXVK_DEBUG_LAYERS=1`x1 2018-04
Upgraded to 396.18 from 390.48 today and now NFS Payback won't load unless
DXVK_DEBUG_LAYERS=1is specified. Game ran yesterday with 390.48: https://www.youtube.com/watch?v=ym7IhPpH4oESoftware information
Need for Speed Payback
High settings
System information
Apitrace file(s)
Log files
NeedForSpeedPayback_d3d11.log
NeedForSpeedPayback_dxgi.log