Tomb Raider 2013: Black textures, distortions caused by tesselation

[jarrard]

This game works but the graphics has issues. There are black textures all over the place and the characters are mostly black textures. I have discovered this only occurs with tessellation turned on, has this not been allowed for DXVK yet ?

Software information

Tomb Raider, High-Low Settings. Everything works except for tessellation

System information

• GPU: 1080ti
• Driver: 396.24
• Wine version: 3.7staging
• DXVK version: latest master

Apitrace file(s)

• not useful, dxvk issue

Would a apitrace help resolve this tessellation issue? or is it a known limitation of DXVK at this present time?

Log files

• d3d11.log: not useful, dxvk issue
• dxgi.log: not useful, dxvk issue

[doitsujin]

I'm aware of this bug. It's low-priority for me because it's highly game-specific (in general, Tessellation works just fine) and this game has a native Linux port, but I'll tend to it at some point.

[pingubot]

Tesselation is known to be broken in 396.24. You need at least 396.18.07, but please use the latest vulkan beta which is 396.18.11.

https://developer.nvidia.com/vulkan-driver

Edit after dojutsins comment: If its known to be broken in dxvk itself, then even 396.18.11 won't help.

[doitsujin]

@pingubot this particular issue is not a driver bug in this case, happens on RADV as well.

Although you're right in that 396.18.11 is recommended over 396.24.

[jarrard]

The native Linux port is terrible however, looks a little worse and has very poor performance for my 1080ti card in any open/dense area. So hence thought I give DXVK a go. I'll look at getting beta drivers, but like said, seems like a DXVK issue.

IMO It would be worth fixing as I think this game is a strong candidate for comparison with the native linux version which runs quite bad.

There is no arch package for 396.18.11 (or 07) so I can't test that beta release. Might need to wait until they move it to official drivers.

[SveSop]

@jarrard

There is no arch package for 396.18.11 (or 07) so I can't test that beta release. Might need to wait until they move it to official drivers.

Generally i dont think there is any packages of beta drivers.. Same for Ubuntu, as only the release drivers are packaged. The nVidia downloaded .run driver works after you figure out how to install that tho :)

[jarrard]

NVIDIA's packages are often VERY strict about which kernel builds they work with. I can assure you they don't work with the 4.17rc I'm using atm. MAYBE with 4.15 if your lucky.

[SveSop]

@jarrard Yeah, probably needs patches to work with 4.17. 4.16 works without any patches tho, but that might not be a option for you. I have not tested on 4.15 recently, so i dont know.

[jarrard]

This issue with the driver, would that explain why hairworks doesn't work in witcher3?

I'm happy to wait until next driver update, if I was using Antergos I'd probably risk it but manjaro's mhwd doesn't like people overriding it. Can probably do it but I'd risk black screen stuff happening and I can't be stuffed messing with that this week.

[ghost]

@jarrard strange, last nvidia release driver works on 4.17-rc4 without ANY issues for me

[jarrard]

Works yes, but unless you enable hairworks and look at geralt's HAIR, you won't notice a issue ;)

[doitsujin]

Hairworks requires stream output to work, it's an unrelated issue (see #138, #135).

[doitsujin]

To give you an update, I looked at the issue but I have no idea what's wrong, especially since none of my usual set of debugging tools work with the game.

[doitsujin]

Another update: Considering some very weird behaviour I'm seeing on RADV, this might be a driver bug after all, but I'm not sure. @jarrad can you test whether this still happens on 396.24.02?

[jarrard]

I'll give it a go later tonight.

[doitsujin]

Ping?

I spent another couple of hours debugging this again and it looks like part of this is caused by an interface matching issue; declaring the tessellation shader input and output variables manually like in the original D3D11 shaders partially resolves this problem. But even with that there's some undefined data floating around.

Still no idea what's wrong and how to fix this in DXVK, sadly.

[aufkrawall]

The tesselation issue is still present with 396.51.02.

[doitsujin]

Finally found the bug, should be fixed now.

[random2324]

I think this also fixed an issue with Dirt3 with 0.72. Setting option cloth to high caused those red splines in DXVK 0.70 proton. From the games settings xml file it can be read that Tesselation is used when set cloth to high in game menu.