It’s BS though. People with TOTL hardware are having issues. Those systems don’t underperform because the game is advanced or anything like that – the game underperforms because it is a new release that is poorly optimized. It’s also expected because it’s on a senior citizen of a game engine that likely needs a few other nudges.
Todd Howard forgets that PC users see this shit all the time, and it’s pretty obvious with this one. Hoping to see talk of optimization in a coming patch instead.
Edit: a good example – not hitting 60fps in New Atlantis, but concurrently, CPU usage in the 50s and GPU usage in the 70s. That’s a sign of poor optimization.
I’m starting to think that maybe, just maybe brute forcing a 26 yesr old engine that makes skyrim have a stroke if you try to play above 30fps isn’t a good idea
While I’m no fan of paid sponsorships holding back good games, this is untrue.
Neither nvidia nor amd block their partner devs from supporting competing tech in their games. They just won’t help them get it working, and obviously the other side won’t either, since that dev is sponsored. There are some games out there that support both, some of them even partnered.
So yes, it’s bullshit. But it’s not “literally paid” bullshit. Bethesda could have gone the extra mile, and didn’t.
AMD blocks partners from implementing DLSS. You’re probably right that it’s not paid bullshit as the payout isn’t monetary. But it’s still being blocked due to the partnership.
This is hardly the first game to do this. Jedi Survivor, RE4 have the same problem. AMD sponsored FSR2 only. The work required to implement FSR2 or DLSS is basically the same (motion data). That’s why DLSS mods were immediately available.
Since FSR2 was released not a single AMD sponsored game has DLSS added. Even games done in engines like unreal where all the dev has to do is include the plugin.
It’s BS though. People with TOTL hardware are having issues. Those systems don’t underperform because the game is advanced or anything like that – the game underperforms because it is a new release that is poorly optimized. It’s also expected because it’s on a senior citizen of a game engine that likely needs a few other nudges.
Todd Howard forgets that PC users see this shit all the time, and it’s pretty obvious with this one. Hoping to see talk of optimization in a coming patch instead.
Edit: a good example – not hitting 60fps in New Atlantis, but concurrently, CPU usage in the 50s and GPU usage in the 70s. That’s a sign of poor optimization.
I’m starting to think that maybe, just maybe brute forcing a 26 yesr old engine that makes skyrim have a stroke if you try to play above 30fps isn’t a good idea
What game engine is 26 years old other than the Unreal engine?
Edit: stepped on some toes i guess lmfao
Gamebryo, the base of creation engine used by Bethesda for this
Ah okay. Thank you for the actual answer
…like not launching with DLSS. What a weird oversight.
AMD is the official sponsor. That’s the one thing that wasn’t a surprise.
It’s not an oversight, they were paid to not include DLSS.
While I’m no fan of paid sponsorships holding back good games, this is untrue.
Neither nvidia nor amd block their partner devs from supporting competing tech in their games. They just won’t help them get it working, and obviously the other side won’t either, since that dev is sponsored. There are some games out there that support both, some of them even partnered.
So yes, it’s bullshit. But it’s not “literally paid” bullshit. Bethesda could have gone the extra mile, and didn’t.
AMD blocks partners from implementing DLSS. You’re probably right that it’s not paid bullshit as the payout isn’t monetary. But it’s still being blocked due to the partnership.
This is hardly the first game to do this. Jedi Survivor, RE4 have the same problem. AMD sponsored FSR2 only. The work required to implement FSR2 or DLSS is basically the same (motion data). That’s why DLSS mods were immediately available.
Since FSR2 was released not a single AMD sponsored game has DLSS added. Even games done in engines like unreal where all the dev has to do is include the plugin.
Literally not the case here, as evidenced by public communications.