What you linked to was just my code for ADAPTIVENESS_Y and ATOC?
Please don't link random values up to ATOC... That can break things.
IDK what KanL is meant to do, I imagine its meant to signify to the driver that this is Kane and Lynch for driver hacks.
Is there an actual problem with the game btw?
What you linked to was just my code for ADAPTIVENESS_Y and ATOC?
Yes, for context.
Is there an actual problem with the game btw?
No, the game works good.
This isn't a bug then.
If there's any difference on native drivers that's noticable, let me know.
(ie. does it look like ATOC or another feature is enabled?)
AMD variant. Just for the record[^1]. No LOD-Bias hack or sharpening unlike the initial screenshots.
The hack (ported to dxvk-2.7.1):
[^1]: @WinterSnowfall thought about what to do with the game-specific hacks after #4888, so more info if this still relevant ...
The FOURCC value is KanL. I doubt it used somewhere in drivers, it looks like it was either for debugging purposes or to be treated as
D3D9Format::Unknown(Edit: I mean "and applied with D3DRS_ADAPTIVETESS_Y". Name likely was "invented" to be unsupported format.).Out of curiosity I created a hack to accept this format (where
D3D9Format::ATOCcheck is in current code)https://github.com/doitsujin/dxvk/blob/b4f2094c02bea9b241f558a1c1888ba28a88d3f0/src/d3d9/d3d9_device.cpp#L1695-L1697
and there is indeed noticeable difference (see screenshots). Actually I don't know what I'm doing, so this bug report is FYI.
Before
After
Software information
System information
Apitrace file(s)
Log files