in my case dont appear this flickering in same scene using dxvk 2.4.1

@Leopard1907 Out of curiosity could you try running it with d3d9.invariantPosition = False

in my case dont appear this flickering in same scene using dxvk 2.4.1

In your case... you didnt have enabled everything there 🤣 But you have to enable everything to start reproducing it. So first create in a registry ExtendedDialog and enable it. After that enable everything with -setup switch, so make sure it is same settings just like on picture that he posted. There are more setting hidden there, that he didnt showed, but i assume he didnt touched that. 👯 If you do exactly that, then we can figure out if bug is RDNA specific (if it happens also for you with everything enabled) or maybe just happens on RDNA specific ASIC. like his card (if it dont happen for you with everything enabled)..

Yes, i didnt touch those "Dev" options.

@Leopard1907 Out of curiosity could you try running it with d3d9.invariantPosition = False

Yep, that fixes the issue.

Hardware related issue I think.
Cannot reproduce on Nvidia & Windows.

Edit: according to PCGW, this game has broken physics when running over 60 fps. Can you test again under 60hz?

PS: The game seems lock the usage of Windows key on keyboard in setup dialog.

We've found that the issue shows itself when d3d9.floatEmulation is set to Strict which is only default on radv, nvk and amdvlk open as of writing.

@qinlili23333 Can you try with dxvk master?

@qinlili23333 Can you try with dxvk master?

Interesting. I can reproduce on master 8584fc7.

Video: https://youtu.be/LV9gVc3juSs
Device: RTX 4080 Laptop 565.90 (Windows 11 23H2)

Yes, as expected. MR linked above enables same behaviour for NV driver too now so you have same behaviour as RADV now. So not a driver or hw specific issue.

Strict: Use a slower but more correct approach. Necessary for some games

@mrdeathjr28
https://github.com/doitsujin/dxvk/blob/master/dxvk.conf#L489

Probably should be able to repro too with his Intel if he sets this to Strict.

Yes, as expected. MR linked above enables same behaviour for NV driver too now so you have same behaviour as RADV now. So not a driver or hw specific issue.

Strict: Use a slower but more correct approach. Necessary for some games

@mrdeathjr28 https://github.com/doitsujin/dxvk/blob/master/dxvk.conf#L489

Probably should be able to repro too with his Intel if he sets this to Strict.

d3d9.floatEmulation=False fix for me.
Maybe we need to add a config for this game, or maybe strict emulation need to be reverted

Yes, as expected. MR linked above enables same behaviour for NV driver too now so you have same behaviour as RADV now. So not a driver or hw specific issue.

Strict: Use a slower but more correct approach. Necessary for some games

@mrdeathjr28 https://github.com/doitsujin/dxvk/blob/master/dxvk.conf#L489

Probably should be able to repro too with his Intel if he sets this to Strict.

Verified on Intel Xe 80eu (1135G7) 101.5768 (24H2), if set to Strict, same issue.

I've found something already in config

    /* Tomb Raider: Legend, Anniversary, Underworld  *
     * Read from a buffer created with:              *
     * D3DPOOL_DEFAULT,                              *
     * D3DUSAGE_DYNAMIC | D3DUSAGE_WRITEONLY buffer. *
     * Legend flickers with next gen content option. */
    { R"(\\(trl|tra|tru)\.exe$)", {{
      { "d3d9.cachedDynamicBuffers",        "True" },
      { "d3d9.maxFrameRate",                "60" },
    }} },