-
Ever wanted an RSS feed of all your favorite gaming news sites? Go check out our new Gaming Headlines feed! Read more about it here.
Godfall update enables ray tracing......... on AMD GPUs only.
- Thread starter Stacey
- Start date
You had to enable PhysX in options and it ran like total ass on NV HW too...
Yall are misunderstanding what im saying. CDPR is at a state where their engine is using the RT tech with nvidia drivers to the level they need and not the AMD ones. They aren't stopping AMD, they just aren't ready yet. The option will be there when they finish the work of incorporating the support in their engine.
Devs don't need to implement things for each specific brand. Battlefield V got it's RT patch in 2018 (partnering with Nvidia), even before RDNA1 cards was out, let alone RDNA2. And yet it works just fine with RT on new AMD cards. So, it's not even a toggle, unless devs specifically want to implement some vendor-exclusive feature (DXR is not), the game just talks to OS via generic API calls. That's the whole point of DirectX/OpenGL/Vulkan/etc.
They don't need to enable any amd specific options. AMD will use the same options as nvidia with DXR.
DXR is specifically made to be a vendor independent API that can be used by both manufacturers.
It absolutely isn't. The RT capabilities in the game is vendor agnostic, using DXR.
Performance will be dependant on hardware
It's on dGPU vendor to develop drivers to run games properly and well, not on developer. Sure developers test with different HW and SW configurations, but ultimately it isn't on them.
If AMD puts in the work they can have driver out for 77 that enables AMD dGPU's to run RT in the game.
Also do you have some receipts or just own speculation..?
[/QUOTE]
not having an option to enable particular thing vs being able to enable while having lower performance . Is there a difference?
As far as I know, this is an Unreal Engine game so unless they put their own RT code in I don't see any reason why Nvidia RTX would be disabled other than for marketing reasons
Engine support is already there.
RTX is AMD raytracing and AMD raytracing is RTX.
Both are DXR, there's no difference other than Nvidia calls it RTX for marketing reasons.
I know why it's confusing - because Nvidia wants you to think it's proprietary technology, but it's not.
To be fair nvidias hardware implementation of RT uses specialised hardware (RT cores) and that's the reasoning behind the RTX label.. along with the tensor cores..
AMD does not use any specific different hardware to what it uses for raster graphics..
The API in DX12 DXR allows it work on all the hardware regardless.
I think that's why people tend to think Nvidia has some secret exclusive RT sauce... In some respects they do, but the marketing makes people believe that it's not vendor agnostic, when it is.
re ray tracing exclusivity on vendors' cards:
more at my RX 6800/6800XT review:
arstechnica.com
more at my RX 6800/6800XT review:
AMD Radeon RX 6800, 6800XT review: The 1440p GPU beasts you’ve been craving
Equivalent Nvidia GPUs beaten in significant cases—but not in ray tracing.
arstechnica.com
I guess I should have said AMD instead of CDPR, but I really wasn't being that serious folks. The point I was trying to make is that nvidia is further along with RT than AMD is, thus CDPR feels more comfortable putting the brand on the game.
Then it should work on Nvidia cards too, unless it can't. The game is out, though the update probably isn't, only time will tell. Similar to freesync, I like when AMD stuff isn't locked since I currently have a Nvidia card, and I avoided G-Sync monitors since it would lock me into their ecosystem, removing my options.
That's the theory, though it wouldn't be a first time with new, fundamental feature to have issues between vendors at beginning. Even without RT on DX/GL/Vk there are sometimes differences between drivers, for example performance might vary wildly or some tiny details might be handled differently hiding (application) bugs in renderer that other vendor's driver exposes. Modern APIs have better tools to deal with such issues but they are still possible.
And if a game uses Nvidia's Vulkan RT extension then it will not work on AMD without patching the game. And there is no reason to blame Nvidia for that.
Q2 RTX doesn't use DXR, though. Along with Wolf2, it uses Nvidia's exclusive Vulkan RT extension. It had to, since at the time Vulkan didn't have it's own global RT extension.re ray tracing exclusivity on vendors' cards:
more at my RX 6800/6800XT review:
AMD Radeon RX 6800, 6800XT review: The 1440p GPU beasts you’ve been craving
Equivalent Nvidia GPUs beaten in significant cases—but not in ray tracing.
Theoretically, AMD could support it via driver update, but they obviously won't bother.
When the CDPR statement on only supporting Nvidia at launch was initially released, RDNA2 cards barely even existed, no one had them, and we were still working with a November release date for CP2077 that preceded the RDNA2 launch.
I'm confused as to how people expected CDPR to commit to having support for an architecture they hadn't touched, and for GPUs that at the time weren't even going to be in consumer hand when the game launched.
The thing is, if anything they've had RT capable Nvidia GPUs in their hands for literal YEARS longer than they have AMD's. Don't tell me they've never touched a Turing GPU.
If anything, the Nvidia RT should be far more ready for the spotlight that that for which the GPUs aren't even on the market.
But marketing says....
The game ships with an AMD RT. DLL I velive, so I think Godfall may end up using a different Version of RT shadows than the Standard UE4 ones.
Technically incorrect, they did use their own VKRay solution for Q2RTX and Youngblood. And I know about at least one game where the developer can't enable RT on any h/w but NV's for some period of time. So they are, again, equal here. AMD isn't "open", NV isn't "evil". Both are commercial companies selling their products however they can.
Not sure about your unnamed game you know of, but VK_NV_Raytracing is what both Q2 RTX and Youngblood use. This is a standard Vulkan extension that any vendor is free to implement. It is common for vendors to implement other's extensions in Khronos API's - the vendor tag just signifies who created it initially for extensions too new or rare to be added to the API proper.
The surprising thing is Godfall doesn't have RT shadows on PS5 AFAIK. No idea why.
Many games don't have RT on next-gen (now current-gen) consoles while they do on PC: Dirt 5, Godfall, Far Cry 6, Fortnite etc...
Many games don't have RT on next-gen (now current-gen) consoles while they do on PC: Dirt 5, Godfall, Far Cry 6, Fortnite etc...
It performs badly because it uses a ton of tesselation, which NVIDIA GPUs are very good at, and AMD GPUs have traditionally been much weaker at.
AMD's solution to this was a driver hack that forced tesselation to run at lower iterations than specified by the games, which often produced very bad results.
I don't know if that is still the case with their latest hardware.
I'm not sure if it fully caught up but Vega and then Navi both greatly improved AMD's geometry performance. I don't think that's a hugely relevant weak point for them anymore, now it's RT and ML (DLSS).
That's what I thought, but that's the entirety of the "gameworks kills AMD performance" thing.
It's just that NVIDIA were using a lot of tessellation, which AMD's hardware was weak at, at the time.
And it was not "unnecessary tessellation" as many claimed. Forcing lower iterations did ruin the effects, and the Crysis 2 example people loved to point at was culled outside of wireframe view.
Nvidia does this all the time with industry standard APIs? Examples?
aside from PhysX, all of their stuff was made inhouse
also, Godfall might just have RT Shadows for character models? or might have some additional screen space rt shadowing going on
That is big oofff... for title that has been pushed pretty hard as RT game to play with newest AMD dGPUs.
Is it to save performance or just developer not being good with implementation?
probably for performance reasons? or possibly because RT was such a late addition they couldn't add much else. the lack of RT reflections is weird given how much shiny shit is in the game
Shadows are considered one of the cheapest effects to RT, but why to even do that partially?
Reflections with this amount of reflective surfaces would be something else for AMD and NV cards :D
You see the first AMD RT demo video thing? they are up to the task of making mirror world.
I remember it looking really bad and reflections being low-res.
Maybe I remember wrong 🤔
I was just joking about that demo taking reflections to infinity and beyond, and you know how jokes on the internet go when you don't explicitly state it as such ;)
/not well.
The reflections, from a technical point, seemed fine. But everything else about the demo looked disgusting so you're right about it looking really bad.
VK_NV_ray_tracing is NV's proprietary Vulkan extension which served as a basis for Vulkan's generic VK_KHR_raytracing.
They are very close obviously and one could relatively easily support the former if there's already support for the latter.
But it's not "standard Vulkan extension".
Whether this is even relevant is another question though since there were no KHR extension back with NV launched their first RT h/w.
Cause they aren't cheap when done in full. And RT which isn't cheap is not something which AMD will be pushing into their games.
I disagree with your terminology. Proprietary usually indicates some kind of special secret sauce or lock in to the vendor. The Vulkan extension has no such thing and it is in fact common practice for one vendor to implement another's extension in Khronos APIs.
Enabled with an .ini edit?
www.reddit.com
According to the author VRS and DXR are tied to the same variable, so you actually gain performance when enabling it.
Reddit - Dive into anything
www.reddit.com
According to the author VRS and DXR are tied to the same variable, so you actually gain performance when enabling it.
right? then it turned out Godfall maxes out at 8600MB VRAM at 4K. That was the weakest cheap shot marketing i ever seen. Besides stating they have more cards than nVidia and ending up having even lesser amounts on release...
So I got some bad news for ya:
Like it's absolutely in the same boat as Godfall re: DXR implementation being bizarrely restricted to one vendor on launch.Google Translate of this said:
Also mentioned by one of CM's.
Curious what is "the issue" as implementation should just use standardized API and NV has said there is nothing that would prevent AMD cards from running RT day 1 in games that have it. Could it be just that CDPR didn't have AMD cards and drivers to develop and test with? 🤔