Re: Let us update DLSS .dll by excluding it from EasyAntiCheat

Don't live support game usually have current year shown ? Something like it's still being worked on, rather than done deal.

---

@EA_Atic wrote:

Thats correct, it suppose to show the year the game came out. @Foxfort

/Atic

---

I think in BF1 and V they show the current year (or at least a newer year than the year they came out). I imagine it is as simple as a hard-coded number versus a variable that checks for current year. 

@EA_AticOh nice, community manager responded. Any chance of this getting brought up to the team?

@EA_Atic Any chance we can get DLSS updated in the game? The new versions of DLSS fixes a lot of problems the DLSS 2.2 version has that Battlefield 2042 is running. I imagine it's not that big of a time investment to implement, but I'm not a dev so I wouldn't know and I'm sure they already have a lot on their plate. It would be greatly appreciated by anyone who uses DLSS though.

They don't even have to update it. Just exclude the DLSS .dll from EasyAntiCheat like other games do so we can swap it to newer versions ourselves and not have it greyed out in the menu. Super easy fix.

Still not possible in 4.0

@NikkMann149 It seems to me that EA knows something about this game and we may expect the closure of this project, since they cannot pay NVIDIA for supporting new versions. Moreover, they blocked the change in this file, which suggests that they were forbidden to do this by Nvidia. Just a business, nothing personal.

And I believe that they simply looked at EA and decided that new versions do not bring anything new to this game, and maybe even reduces performance. Although... most likely what is written in the first paragraph.

T0TALfps (Reddit)
Hey there,

We've been looking into this for quite a while, and at this moment in time, we have no plans to update to a different version of DLSS. The gains that DLSS provides are dependent upon the game, and we'll continue to assess if we feel it warrants a version upgrade.

Thanks!

@pecmeserp Alot of that is just wrong, don't really think you know what you're talking about. Many newly released games (and even games which still get live service updates) come with older DLSS versions and never bother updating them, probably because its too much of a hassle to test every new DLSS version and see how it affects all aspects of gameplay. DICE not updating DLSS in bf2042 is not any indication of any kind of loss of support.

Nvidia also does not bar any developers from updating DLSS, once a dev has access to it they can use whatever version they want and tweak it for their game. There is no need for "continued payment" to keep the feature in the game. Once its in there its in there for good.

Newer version of DLSS have been objectively proven to eliminate issues from older versions while retaining the same performance, and DLSS 2.5.1 is the best version so far out of all them. If DICE does not want to go to the trouble of testing new DLSS versions, all they need to, like many other games do (including live service ones), is to allow users to swap the DLSS .dll file for a newer version and still be able to use it in game. That way, DICE does not have test new versions, users can upgrade it whenever they want, and any issues that would arise from it are on the user, but 100% there would be no issues since this can be done in literally every game that uses DLSS and has never caused issues.

Still not possible in 4.0.1

And we need it please!

It will be a HUGE IMPROVMENT.

Only problem i can't swap the files myself because of anti-cheat system

Or better yet, EA/DICE can you please update DLSS.dll for us in the next patch?

Now we have DLSS 2.5 according to DLL file. Once I've logged on today, I instantly observed the difference - the game is much sharper now.
That's a massive win for us - good job DICE/EA.

Just saw, nice!

Still can't .dll swap which would future proof it, but the update is very nice.

Although 2.5.0 still had dlss' terrible old sharpening implementation, which even nvidia says was bad and is why they disabled it in 2.5.1 (and why I wanted 2.5.1 specifically).

Hopefully its enabled too strongly in the game, or if it is they'll at least add a slider in the future.

It also still has the issue of greatly reducing motion blur strength or disabling it on objects all together like the hovercraft's back fan (and I think DOF as well)