Ban Warning / Optiscaler DLSS/FSR FPS improvement

Installed optiscaler which enables DLSS on non-dlss cards.

It converts DLSS pipeline to FSR 3.1.2 to enable limited frame gen on non-RTX cards.

I'm posting this as I was in no way trying to cheat. I've since removed optiscaler.

As soon as I entered the game I was booted with a ban warning for cheating (i.e. map hack/) which is understandable as I think optiscaler hooks into the game.



The crux of this post -

Can you please suggest to devs to implement FSR 3.1.2 My FPS was clean and improved from a choppy 50 to stable 90+ fps).

Seconded... GGG please either make it a policy not to ban upscaler mods, or commit to adding native FSR3/FSR4 support.

I can tell you this is at the bottom of their list. Probably not even on their radar.

Well hopefully if this post gets bumped the right eyes will see this.

Using optiscaler for a bit now, no warning... could be related to the way it is installed maybe, as there are different options?

But yes we need FSR 3.1 ASAP indeed.

"

monkeyskank#1595 wrote:

Using optiscaler for a bit now, no warning... could be related to the way it is installed maybe, as there are different options?

But yes we need FSR 3.1 ASAP indeed.

How did you install it? I used version.dll - It doesn't matter now I can't risk it.

The ban warning stated if I even attempt one more time both my PoE 1 and 2 accounts will be banned. That's 15 years of progress I can't risk.

In the interest of understanding,

I would very much enjoy knowing why GGG would consider Optscaler/reshade and the like a cheat? Or is it a false positive?

"

Sage_One#5363 wrote:

How did you install it? I used version.dll - It doesn't matter now I can't risk it.

The ban warning stated if I even attempt one more time both my PoE 1 and 2 accounts will be banned. That's 15 years of progress I can't risk.

At least there was a warning and not a straigh ban, so there's that. It's still a shame but if their thing sees it as a map hack it is what it is.


Now, IIRC I went through a rather regular process, making it use DLSS through the dxgi dll. Now using a different dll could be the difference that gets it flagged, or it relates to the fact I also have the extra dlls for the framegen etc that are seperated on the github.


Even if I got it working, and for future references,
Disclaimer: this is not recommended to attempt, and will always be at your own risk.

What we need is at least fsr 3.1.x to be implemented, thanks GGG.

Stability seems to have improved slightly with recent updates but some of us on middle range pcs are still struggling.

FSR3 implementation would solve a lot of this.

From what I know they just repackage it with the latest .dll since the more recent ones are standalone files and backwards compatible. A lot less work for devs to implement. Hopefully not hard to implement with their engine but it is custom so who knows. I hope they update it too