Crysis 3 Remastered not playing nice about dlsstweaks

[ShinChaosBahamut]

Extra note (noticed the "Releases" page was updated to reference Crysis 3 Remastered: ForceAutoExposure did nothing. And it's not that the dll is causing rendering issues so much as it's full-blown stopping DLSS from doing anything.

[emoose]

Another user posted a screenshot where it seemed to start rendering for them but had a lot of issues, does it get this far for you at all?

https://twitter.com/Litt_Mattster/status/1625548957039591424

[ShinChaosBahamut]

That's pretty much what's going on. No DLSS/DLAA, no anti-aliasing of any kind. And no DLSS Indicator overlay either, which means DLSS just isn't being loaded at all when ForceDLAA's set to true.

[emoose]

Ahh right, hmm.

no DLSS Indicator overlay either, which means DLSS just isn't being loaded at all when ForceDLAA's set to true.

I had a similar issue testing debug build of DLSSTweaks on SOTTR, turned out my hook code was failing to return a value properly, didn't matter on release build some reason but game started having issues show up with debug - wonder if maybe that could be affecting Crysis somehow.

The build at #2 (comment) should have that code fixed, if that still doesn't help maybe try with ForceDLAA = false and change one of the new DLSSQualityRatio values to 1.0 instead, maybe game doesn't like it when ForceDLAA makes all the quality levels the same.

[ShinChaosBahamut]

No dice, enabling DLSSQualityRatio and setting the used value to 1.0 disengages DLSS as well. (and this is regardless of which DLSS dll build I'm using, dev or enduser)

ForceDLAA also doesn't work with the build you linked. Still think its weird "Using DX11 but also using Vulkan to handle ray tracing" bit is at least partly responsible for this.

[doktorsleepelss]

Check if it works with any ratio other than 1. Try 0.95 for example. Mortal Shell is game that refused to work with DLAA or 1, but it does with any other ratio.

[ShinChaosBahamut]

0.95 worked. Not good enough for my literal OCD though. XD

[doktorsleepelss]

0.999 gets me an internal resolution of 2559x1439. Close enough I guess.

[doktorsleepelss]

Actually, try this ghetto workaround. Make only ultra performance mode a ratio of 1. Leave the other modes with their stock ratio. Now start up the game with quality mode already enabled. And when you're in the game playing in a loaded up level with a working DLSS, go to the options and change the mode to ultra performance. Maybe DLAA will stick if you do it this way.

Mortal Shell just plain crashes if I start a game with DLAA already enabled. But if I start the game in quality, and then change it to DLAA (ultra perf with ratio of 1) while already playing, it seems to work fine.

[ShinChaosBahamut]

No dice. Setting DLSS in-game to the mode I set to 1.0 causes DLSS to disengage as well.

Man, game just HATES any and all attempts to convert DLSS into DLAA it seems.

[ShinChaosBahamut]

Tried with version 0.123.10; naming the dll to dxgi, xinput9_1_0, or winmm causes the game to crash before booting, regardless of whether DLAA's being forced or not. Naming the dll to anything else causes it to not try to inject in the first place.

[emoose]

@ShinChaosBahamut hm, could you try the beta2 and beta3 releases from #2 (comment) & #2 (comment), and see whether either of those works? Guessing the changes in beta3 could be causing issues, but not really sure.

[ShinChaosBahamut]

Turned out it was something else causing the crash. (took care of that though) Not that it matters as forcing DLAA/setting the mode scaling to 1.0 still results in DLSS disengaging.

Think I'll consider this a wash and just deal with SMAAT2X.