Time? What time? A guy did it from his basement in a single day. That's bs frankly.
Exactly my point.
That little time was spent on this - people make their parts independent of each other (textures, voice lines, animators etc) and it's all packages to be assembled later.
The final product of these console games doesn't seem to actually GET tested these days - they skip the final QA, let community feedback provide it and only then do they pay someone to fix the top issues.
Look at games not out to make quick buck and how they fix things instead - BG3 (DLSS, FSR, performance patches multiple times in launch week after a year long public beta)
Deep Rock Galactic: Game has FSR, FSR2 and DLSS, with FSR2 looking worse than FSR and DLSS With artifacting for a long, long time.
When asked on a live devstream the devs simply answered that they installed them with the default settings and only
ONE of the 6 person dev team actually plays the game who has even the faintest idea how that tech works, despite four of them all playing on PC live streams weekly. They have 32 total employees, and you bet none of them have days or weeks spare to sit down and test and finetune FSR, FSR2 and DLSS on all the GPU and resolution combinations out there - they believe that if AMD or nvidia want it done better, that they should provide better tools for it.
FSR2 works best with known and static base and output resolutions, because that's what the consoles use. Nvidia used their AI stuff to math that out in advance, so they have a little less guesswork on that side. Neither AMD nor Nvidia keep sending updates out to companies with newer versions of these tools - theres no easy person to blame. Is it AMD/Nvidia/Intels fault? The game devs? Should it be in drivers, like SLI profiles were?
I'm well aware of how it all works because I made my own DLSS mod for DRG to unlock DLSS on all GPUs, and use it on my GTX 1080 to play DRG in 4k - since that mod literally just uses FSR2 (and the starfield mod is THE EXACT SAME MOD) it's clear that FSR2 can actually do all the same things as DLSS, the only differences was in the default scaling and sharpening settings - and those are copy pasted with the DLL you use.
What about the other 22 out of 27 amd sponsored games that don't have dlss?
As for the bold part, that's pure bullshit. The implication is that AMD block them, when it's actually that when sponsored by Nvidia you're REQUIRED to.
They force DLSS, frame gen and RTX in every title possible to try and make gamers want to buy nvidia over AMD.
What about the games that already had dlss but was removed after amd sponsorship?
All 3 of them?
Three studios removed DLSS support after receiving AMD sponsorship - Xfire
Because they wanted FSR for the consoles and focused their time on a universal, cross-platform solution?
The entire source of that was someone who was misquoted and deleted his tweet and explained how he was being misquoted, but it's the internet so that doesn't reach people.
“Bethesda’s decision to use FSR is console leverage,” he explains. Starfield is also likely this year’s biggest Xbox game, and FSR runs on the AMD chips inside the Xbox Series X and S as well as competing graphics. Meanwhile, each version of Nvidia DLSS is exclusive to specific recent generations of Nvidia GPU.
AMD claims there’s nothing stopping Starfield from adding Nvidia DLSS
AMD ask them to support FSR so that they work on modern consoles, or they wouldn't include THAT, either.
There is no motivation to add DLSS to a game, but there is motivation for console games to support FSR.
DLSS is a fraction of a fraction of their users - windows gamers with modern Nvidia cards playing their game vs every single console sale.
My first google result had this, on the game devs being lazy.
TPU's DLSS/FSR comparisons are always chaotic with many games having only one method actually working properly (and it's not always DLSS) with default sharpening values usually way off the mark, at the default provided in the source SDK.
Just like here on TPU we have a list of DLSS .dll files because game devs are too lazy to even update those.
Edit sorry
@the54thvoid , didnt see the lock.