[D3D9] F.E.A.R.: see-through player body

[DaRkL3AD3R]

The player character's body model is ghostly transparent.

Software information

F.E.A.R. max settings. FSAA = off, Soft Shadows = off.

System information

• GPU: GTX 1080 Ti
• Driver: 442.19
• DXVK version: v1.5.4-38-g4cf3ef5

Apitrace file(s)

https://www.mediafire.com/file/dvf2lgnr5lopr57/FEAR.zip/file

Log files

• d3d9.log: https://www.mediafire.com/file/539dmsneqkwn0wk/FEAR_d3d9.log/file

[misyltoad]

Please upload the apitrace somewhere else -- I can't connect to that site.

[DaRkL3AD3R]

https://drive.google.com/file/d/1rdir-Y3uUI-R1FPDxHAcYZ4YdE9ogtIJ/view?usp=sharing

[misyltoad]

Looks like an NV only bug, I will look into it tomorrow. (I think it might be SWVP causing it because we currently have issues with that on NV due to uniform buffer range stuff)

AMD:

Nvidia:

[xpander69]

yeah, confirming on nvidia 440.58.02

[NerosTie]

The last time the textures were not transparent was with version 1067.

The issue comes from this commit: https://git.froggi.es/doitsujin/dxvk/-/commit/b738c4220b7f2ea71cf2f1f61521a08606ee7022

[misyltoad]

I am aware it is depth bias scaling, sorry I should have updated the issue with that info.

[WinterSnowfall]

The last time the textures were not transparent was with version 1067.

Sorry for derailing this a bit, but since I can't check the trace myself at the moment, I have to ask: are the textures also transparent with wined3d, or only with dxvk?

I'm asking because I've seen something similar in D&D Dragonshard, only on Nvidia, but with both wined3d and dxvk. I thought it was a driver bug (since it looks fine on Intel at least), but I'd report it if it's something potentially fixable in dxvk.

[NerosTie]

Only with dxvk (>1067), everything is fine with wined3d.

[DaRkL3AD3R]

Is there any update to this depth bias issue? As an Nvidia user this one is a bit frustrating because DXVK actually resolves Nvidia driver bugs with the game (visible here on Nvidia and goes away when you start capturing through NVENC hence the camera capture: https://www.youtube.com/watch?v=d-sJef5M2J8 ).

[DaRkL3AD3R]

Was going to open a new issue for FEAR about water shader effects being broken.

D3D9: https://i.imgur.com/xpvXU6e.png
DXVK: https://i.imgur.com/2JKDIQD.png

But then I remembered I was running an older version of DXVK to prevent this ghostly transparent bug I reported ages ago, so I updated the version FEAR was using and nice to see the water is rendering fine now: https://i.imgur.com/9bjIrhe.png

Unfortunately transparency problem is still present :( is there any hope for this one? Or are Nvidia users screwed?

[warriormaster12]

It would be nice to get this fixed since soon Lutris will remove Wine3D support.

[warriormaster12]

Nvm about the Wine3D part but still, any chance of getting this working in DXVK?

[vide0hanz]

Confirming issue is still present.

• GPU: Nvidia RTX 2080 Super
• Driver version: 510.54-1
• OS: Arch Linux 5.16.14-arch1-1

Additionally, setting PROTON_USE_WINED3D=1 now results in funky looking shadows and dark areas (probably this just happens to be more perceptible in these environments). Can provide screenshots if desired. Basically the colors look as if they are rendered in 16bit despite 32bit being set in-game.

[Blisto91]

While i was testing something else in this game i tried to check out this issue a bit more.
I have found this to be a regression in dxvk 1.5.1. A more specific bisect will be done later

Edit: i just saw that the faulty commit is already known above. Pardon my brain.

[mascherone108]

Same issue also happens in Condemned: Criminal Origins. Using PROTON_USE_WINED3D=1 %command% fixes it.

[rakantoh]

ok, known issue, some progress or workaround?

[Blisto91]

For workaround you'll have to use wined3d (if on Linux) or dxvk 1.5

[rakantoh]

For workaround you'll have to use wined3d (if on Linux) or dxvk 1.5

dxvk 1.5 is too old, and fear was affected by the megaissue #1318 out of space, but i will try again with 1.5

[xpander69]

Confirming fixed on nvidia with #3042
both F.E.A.R. and F.E.A.R. 2: Project Origin

[K0bin]

I'd still prefer to leave this open until we have a proper solution instead of a workaround.

[K0bin]

Fixed by #3501