Cynicalking
Regular
YepDoesn't starfield already have PBR and GI?
YepDoesn't starfield already have PBR and GI?
An interesting tidbit from one of the devs of Starfield.
Starfield would have had PBR Lighting, Indirect lighting, and RTX technology integration according to Germain Mazac a graphic programmer's Linkedin profile. DLSS integration was to be guaranteed if this is true.
I kind of understand why it's heavy on CPU/memory, being a massive Bethesda game. Although it is so heavily segmented by loading screens I'm not sure this argument makes a ton of sense. But the way it smashes the GPU is baffling to me.
Would be very interesting to see what they do to make it so heavy.
We've had Skyrim cheese and now Starfield potatoes -
Why bring this up? There's likely design trade offs involved here in that optimization choices that allow the above to be relatively easy done have drawbacks in other scenarios. So game might not seem actively heavy all the time, but back end also has to be capable of this.
The official implementation of FidelityFX Super Resolution (FSR) in Starfield still exhibits excessive shimmering on thin steel objects, transparent materials, tree leaves, and vegetation. Enabling DLSS resolves these shimmering problems and ensures a stable image quality, even at lower resolutions like 1080p.
The internet backlash did its thing. Devs now realize that DLSS is always going to be a publicly requested feature, especially with NVIDIA's doiminant marketshare.So Bethesda just announced (via a no fanfare patch note) that DLSS will be included in a future patch.
Sweet. Curious to see the levels of support, FG would be a massive boost here for them. And yesssss!!!!! I don’t have to deal with mods!So Bethesda just announced (via a no fanfare patch note) that DLSS will be included in a future patch.
I guess we can close the thread now!
Leaving this here, which explains what happened with Bethesda, AMD, DLSS etc.
To me, he seems to have a good track-record regarding leaks.MLID has always been a joke.
If you would have watched more than 30 seconds you would have understood what happened. The game was being developed on Vulkan and was a mess. They decided late in development to switch to DX12 (for whatever reason). They had issues with this as well, and decided to bring AMD on-board to help facilitate the transition. Makes sense, considering that Vulkan was pretty much pre-developed by AMD, and they have experience with DX12 too. And it also explains why the game seems to run like crap on everything. If they had problems getting the game to run at all, how can we expect them to have time and resources to implement XeSS and DLSS? Obviously AMD would want some sort of compensation for assisting, so... They included AMD tech and advertised for them.I only watched the first 30 seconds of that video but it seems he is basing his assertion that "Bethesda were 100% not blocked by AMD from adding DLSS" on the fact that DLSS is now being added to the game.
Lol.
Everyone understands that possibility, but it simply doesn't seem to line up, unless you presuppose that AMD is the bad guy, which is obviously a very popular position on the internet. There were also reports that nVidia deliberately leaked the AMD blocking DLSS story as a smear campaign, but that's another story for another thread (or maybe another forum).So the possibility that it was blocked, and then due to the massive backlash AMD amended their contract to quietly unblock it didn't even occur to him?
What exactly could AMD have said?So what exactly was happening during all those months of silence in which this PR firestorm was burning through AMD's and Bethesda's reputations?
He's a clown, from dlss 3 being a driver level toggle to rdna3 RT being much faster than ada to numerous other rubbish and he deletes the old videos when they are so wrong it's embarrassing. Why would bethesda need to call in AMD to help with vulkan when they have iD ???? Sounds like more of his typical rubbish without thinking about the holes his story has.To me, he seems to have a good track-record regarding leaks.
To me, he seems to have a good track-record regarding leaks.
If you would have watched more than 30 seconds you would have understood what happened. The game was being developed on Vulkan and was a mess. They decided late in development to switch to DX12 (for whatever reason). They had issues with this as well, and decided to bring AMD on-board to help facilitate the transition. Makes sense, considering that Vulkan was pretty much pre-developed by AMD, and they have experience with DX12 too. And it also explains why the game seems to run like crap on everything. If they had problems getting the game to run at all,
how can we expect them to have time and resources to implement XeSS and DLSS?
All these are testaments for how messed up the game was that they needed AMD's help, rather than this being AMD paying to somehow mess up the game for nVidia (and Intel).
Everyone understands that possibility, but it simply doesn't seem to line up, unless you presuppose that AMD is the bad guy,
There were also reports that nVidia deliberately leaked the AMD blocking DLSS story as a smear campaign, but that's another story for another thread (or maybe another forum).
What exactly could AMD have said?
They ultimately said no, and nobody believes them.
If they would have immediately said that months ago, would anyone have changed their minds back then?
Probably not, because everyone's minds are already made up.
Easy to say in hindsight.No everyones minds were made up by their silence and refusal to give comment when a simple open and honest answer (if they were legally at liberty to give such a thing) would have cleared the whole thing up
It's relatively easy to implement technically. It doesn't mean it's easy to implement legally. What are nVidia's requirements for officially including DLSS in a game?Because it takes almost no effort to implement if you already have FSR for an enormous return. Not just in technical terms, but in marketing terms and in the avoidance of very bad PR. It's a no brainer.
Exactly. Who would sponsor a game, to then at the same time allow the competitor to market with the same game, where they basically didn't contribute anything through development? It simply does not work in practice.I mentioned earlier in here that AMD likely words it's sponsorship agreement here in a plausibly deniable way that works against the implementation of competitor technologies without explicitly doing so or even explicitly mentioning them. For instance I suspect there is no specific lines in there with respect to DLSS.
Nvidia's standard license it's RTX SDK (including DLSS) requires 2 things marketing/branding related things -
1) The game must have in it's credits, splash screen/title cards, and box (if applicable) attribution to Nvidia and it's logo. Keep in mind this doesn't specify you need one specific splash screen for Nvidia.
2) Allow Nvidia the right to use the game as promotional material for RTX subject to what is "commercially reasonable."
AMD's agreement (at least now) likely probibits the above, which they can plausibly argue fits an exclusive marketing partnership.
Yes it's based on lawyering and technicalities but it is what it is. As with these things one's personel viewpoint is likely going to be swayed by their feelings to the parties involved.
There are none. The UE4 plugin is for free. And the rest is using the Github streamline version.It's relatively easy to implement technically. It doesn't mean it's easy to implement legally. What are nVidia's requirements for officially including DLSS in a game?