• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Nightingale Devs Remove FSR 3 Integration From Launch Build

When the devs are incompetent, one way or another the fault will be AMDs.

Good logic
 
getting rid of the stuttering in unreal engine is a lot of work and time = costs a lot of money but since gamers are stupid and buy anyways why should the publisher care.

but epic is working on it to make it for devs much easier to get rid of it lets just hope this will not take to long since 90% of games will be on the unreal engine 5 in the future sadly.

the coalition who made gears 5 are master of the engine.
 
FSR / DLSS / XeSS in general aren't difficult to implement. That one dev in particular is having an issue speaks to either a specific problem with to their unique situation (like engine issues) or just their competence in general.
Streamline allows them to be easily implemented, at least for the upscaler component.

This case seems to be an issue with implementing frame generation, which is the main feature of FSR 3, hence why they are talking about trying an older version of FSR.

I don't how fair it is to say this is definitely the developer's fault, considering they had no apparent issues implementing DLSS and XeSS. AMD has had issues with their early releases of software in the past, and FSR 3 specifically seems to be a rushed marketing counter to have feature parity with DLSS 3, absent hardware componentry or a working Reflex equivalent to fix the latency issue.

Maybe it's some bug with the version of Unreal Engine they're using, who knows. Lets not jump to conclusions on assigning blame though.
 
Streamline allows them to be easily implemented, at least for the upscaler component.

This case seems to be an issue with implementing frame generation, which is the main feature of FSR 3, hence why they are talking about trying an older version of FSR.

I don't how fair it is to say this is definitely the developer's fault, considering they had no apparent issues implementing DLSS and XeSS. AMD has had issues with their early releases of software in the past, and FSR 3 specifically seems to be a rushed marketing counter to have feature parity with DLSS 3, absent hardware componentry or a working Reflex equivalent to fix the latency issue.

Maybe it's some bug with the version of Unreal Engine they're using, who knows. Lets not jump to conclusions on assigning blame though.
FSR 3 does have a built-in latency reduction component, it's just not exposed as a setting like Reflex, unless you're thinking of Anti-Lag+ which is more meant for AFMF.
 
Both vendors have their fair share of issues but when it comes to technology implemented in games Nvidia has a long history of performance and stability issues. Both Hairworks and PhysX were a complete cluster even on Nvidia hardware. Enabling PhysX in borderlands 2 causes massive frames pikes and crashing. Exact same goes for the witcher 3. Nvidia over-tesselation killed performance in Crysis 2 and a PhysX patch tanked performance in Sacred 2.

FSR / DLSS / XeSS in general aren't difficult to implement. That one dev in particular is having an issue speaks to either a specific problem with to their unique situation (like engine issues) or just their competence in general.

But I digress, the anti-AMD one line quippers don't comment to have a genuine conversation but to validate their existing opinions.
Took the words right out of my mouth
 
This isn't completely new. The Witcher 3 Patch 4.02 about a year ago basically broke DLSS Frame Generation which crashed frequently on that version after working fine on 4.0 and 4.01. CDPR later released a patch to address this.
 
AMD hate is a must have but some of these people really are this dumb as well.
Yep. I wasn't surprised this devolved into a circle-jerk of stupid within the first 3 posts.

Edit: the folks that are anti-Nvidia or anti-AMD are normally exhibiting their choice-supportive bias because they spent a large portion of their disposable income on a GPU and need social validation of their purchase so they don't feel like they wasted the money.
 
Last edited:
Streamline allows them to be easily implemented, at least for the upscaler component.

This case seems to be an issue with implementing frame generation, which is the main feature of FSR 3, hence why they are talking about trying an older version of FSR.

I don't how fair it is to say this is definitely the developer's fault, considering they had no apparent issues implementing DLSS and XeSS. AMD has had issues with their early releases of software in the past, and FSR 3 specifically seems to be a rushed marketing counter to have feature parity with DLSS 3, absent hardware componentry or a working Reflex equivalent to fix the latency issue.

Maybe it's some bug with the version of Unreal Engine they're using, who knows. Lets not jump to conclusions on assigning blame though.
AMD does not support Streamline.
However like I said just in addition of the games I already mentioned I just tried Callisto Protocol to put the mod there to add FG in a game that does not support FG at all and yeah it works there as well, just HUD is ghosting which is obvious since it's a mod.
So again if one guy can do it, company that has many devs should not have issues with troubleshooting the implementation and fixing it without removal.
 
Last edited:
FSR3 came put a year late and still incomplete LOL.

Without AMD hand holding, implementimg FSR3 probably is quite tough with all the UI special handling
 
Streamline allows them to be easily implemented, at least for the upscaler component.

This case seems to be an issue with implementing frame generation, which is the main feature of FSR 3, hence why they are talking about trying an older version of FSR.

I don't how fair it is to say this is definitely the developer's fault, considering they had no apparent issues implementing DLSS and XeSS. AMD has had issues with their early releases of software in the past, and FSR 3 specifically seems to be a rushed marketing counter to have feature parity with DLSS 3, absent hardware componentry or a working Reflex equivalent to fix the latency issue.

Maybe it's some bug with the version of Unreal Engine they're using, who knows. Lets not jump to conclusions on assigning blame though.
Who said they implemented it on their own?

From what I know about Nvidia, they often provide assistance(capable hands $$$) in implementing their technologies, even for small indie studios. Intel shouldn't be much different given their course of action($$$) in other markets.
 
So again if one guy can do it, company that has many devs should not have issues with troubleshooting the implementation and fixing it without removal.
Maybe that one guy is a better programmer than those working in that company. It wouldn't be strange. Many people doing something for hobby or using their skills for their own profit are better than many working on small, medium or even big corporations. Let's not forget the example of ZLUDA a few days ago where one person probably managed to develop a better CUDA emulation than Intel's or AMD's programmers could build themselves.
 
FSR3 came put a year late and still incomplete LOL.

Without AMD hand holding, implementimg FSR3 probably is quite tough with all the UI special handling

Do you really think so when modders can just swap them?
 
When a game needs upscaling to run smooth, it is bad in design. Just my opinion.

I guess FSR3 will come back when they figured out how to implement it.
 
Low quality post by Dave65
When the devs are incompetent
I wouldn't call this incompetence. FSR and DLSS are not as easy to get right as is generally perceived. It's actually quite difficult and that difficultly is dependent on the game engine itself and how it interacts with the GFX API(whether DirectX, OGL or Vulcan).

So temporarily disabling FSR so they can get it right is a good move and the right decision.

AMD software was and still is total garbage.
Only for Nvidia fan babies.
Oh please. Put a cork in it the both of you.
 
Last edited:
The game looks promising though I'm a bit eh on the cards part. :)

...and as usual some of the first comments are total trash. :kookoo:
 
Well this is going about as well as I expected, whataboutism, persecution complexes, double standards, pots calling kettles black, and just straight up dumb unjustified hate.... you all know who you are, even if you don't want to admit it. Another day on TPU forums.

Now having said that, it very much seems like this developers unique struggle, given the history with the tech that doesn't need to be rehashed.
 
The game looks promising though I'm a bit eh on the cards part. :)

...and as usual some of the first comments are total trash. :kookoo:

Yeah i'm a bit iffy on all the crafting-heavy bullshit they've shown on the trailer.

Per usual with early access: I don't deem a game playable until after it's out of early access and a year has passed.

It's insane to pretend that quite a big game like an open-world survival coop crafter will be "playable" on early access release
 
Yeah i'm a bit iffy on all the crafting-heavy bullshit they've shown on the trailer.

Per usual with early access: I don't deem a game playable until after it's out of early access and a year has passed.

It's insane to pretend that quite a big game like an open-world survival coop crafter will be "playable" on early access release
It's a bit hit though mostly miss. Someone got me a copy of Valheim during early access and it was pretty solid. I literally just purchased Cyberpunk 2077 plus the expansion two weeks ago and it's got a few bugs though not too bad. I don't get to game much so I rarely deal with many bugs to begin with. I very much agree that waiting a while after a game releases is a good idea in regards to bugs, the price usually comes down a bit too.
 
It's a bit hit though mostly miss. Someone got me a copy of Valheim during early access and it was pretty solid. I literally just purchased Cyberpunk 2077 plus the expansion two weeks ago and it's got a few bugs though not too bad. I don't get to game much so I rarely deal with many bugs to begin with. I very much agree that waiting a while after a game releases is a good idea in regards to bugs, the price usually comes down a bit too.
indeed, unless you suffer FOMO or cave to social pressure(i.e. your group of gaming friends jump onboard whatever at release) it's best to wait at least a year or more or until it's on significant sale on steam and/or they stop patching -or stop releasing super huge patches-.

CP2077 is one example where almost 2 years(or a little less) it's still bugged and they keep releasing patches with dozens and dozens on changes.

Reviews are in and.... they're mixed at best, i'd say par for the course...
always online even on singleplayer, overcomplicated tedious crafting fotr even the simplest thing: one review showed that to cook a small meal they had to open 5+ menus and click something like 15 different windows/buttons
 
Back
Top