Didn't stop Intel from pushing 14+ nm Skylake beyond 8-pin connector tdp limits so why would this stop AMD?I doubt they can push it much further with current architecture without jumping to some unhealthy TDP. Personally I'd prefer RDNA2.
Didn't stop Intel from pushing 14+ nm Skylake beyond 8-pin connector tdp limits so why would this stop AMD?I doubt they can push it much further with current architecture without jumping to some unhealthy TDP. Personally I'd prefer RDNA2.
Didn't stop Intel from pushing 14+ nm Skylake beyond 8-pin connector tdp limits so why would this stop AMD?
BTW, does anyone know if CP2077 gonna support Nvidia SLI?
I think the best approach when devs don't answer technical questions is to compare with The Witcher 3.SLI is a dead approach. The question rather is, whether it will support multi-GPU through Vulkan. So far developers didn't answer this. They in general avoid answering technical questions as far as I know (or practically all questions really).
I think the best approach when devs don't answer technical questions is to compare with The Witcher 3.
That game used to work with SLI but since then Nvidia tinkered with its SLI profile so it doesn't work with Pascal and Turing GPUs. AMD CrossfireX works fine and RX 4xx beats Novideo in Hairworks.
There's no mGPU profile support in TW3 and won't be in CP2077. AMD RX 5xxx will beat RTX 2xxx in raytracing.
This extension provides functionality to use a logical device that consists of multiple physical devices, as created with the VK_KHR_device_group_creation extension. A device group can allocate memory across the subdevices, bind memory from one subdevice to a resource on another subdevice, record command buffers where some work executes on an arbitrary subset of the subdevices, and potentially present a swapchain image from one or more subdevices.
This is not new engine, it's named Red Engine and has a bigger number, no one keeps the old name and writes the engine from scratch.I don't think TW3 is indicative of anything. CP2077 is using a new engine, and for sure is using Vulkan at least in some cases (Stadia). I'm not sure what it's using on Windows, but could be Vulkan as well. And Vulkan doesn't work with SLI as far as I know. It has its own VK_KHR_device_group.
This is not new engine,
On Windows it will be a DX12 title, I don't see any reason not to be.
Many questions. That's because the answers won't be pleasant and it's all politics and economy and not related to tech.They refused to answer this question.
Many questions. That's because the answers won't be pleasant and it's all politics and economy and not related to tech.
An RTX title without API restrictions? This only possible when studio doesn't sign any exclusive contracts with Novideo. I only know one company that doesn't do this - Id Software who has rich publisher.
Politics. Google pays for Stadia support and CDPR will do exactly that, no desktop support is set in stone until said otherwise (won't be until release date).No idea why, they refused to explain that too. Stonewalling the community is their modus operandi. As for RTX, not sure what you mean. RTX works with Vulkan as I already explained to you. And it's quite clear that RTX is optional, since Stadia using AMD hardware won't have RTX support.
To the worse if any since the game lost compatibility with Novideos Kepler GPUs and doesn't fit into 2GB VRAM buffer anymore (RDR2 with some tweaking did, for comparison). That's, traditionally, a rumor.It is new, that far was known for a long time already. Calling it "RedEngine" doesn't change the fact that it's a complete rewrite, when renderer is concerned.
Google pays for Stadia support and CDPR will do exactly that, no desktop support is set in stone until said otherwise
Because Novideo said so - use DXR so we can have advantage for two months (or longer if AMD decides to be a slowpoke and hold RDNA 2 until 2021). It's in the paid contract.And now think from their management and also developers perspective. They are using Vulkan already. So why waste time on work duplication? Using it for Windows will reuse their work.
Because Novideo said so - use DXR so we can have advantage for two months (or longer if AMD decides to be a slowpoke and hold RDNA 2 until 2021). It's in the paid contract.
You're not the first one to question why.Nvidia can't say so. They can say use RTX, and CDPR can do it through Vulkan just fine.
MS has always been junk. It's just simpler programming. Would be nice to see gaming companies switch to linux and be able to incorporate more flexibility. And with all of the noise from the MS programs running in the background being gone, we wouldnt need as much power all around to game. I've been done with MS for everything except gaming for years now. Just wish program makers would get with open source.That article has nothing to do with Nvidia though. MS pushing that junk and developers being stuck with it due to MS brainwashing, that could happen. But it's not because of RTX.
And it's from 2016. Today developers are getting smarter, thanks to Google pushing more Vulkan usage in Stadia. Going forward, lock-in will start dying out, and will remain only where walled garden lock-in proponents will mandate it, like Xbox, PlayStation and the like. And even there, it will eventually die out due to developers' pressure.
I've been done with MS for everything except gaming for years now. Just wish program makers would get with open source.
Im hoping the "Red Point" is a thumbs up.I've been gaming on Linux quite a while already, and it got a lot better in the recent couple of years. Progress has been amazing. So give it a try.
Im hoping the "Red Point" is a thumbs up.