Originally Posted by DNMock
Nah, the consoles are pushing for ray-tracing, so I would expect AMD to have some form of a ray-tracing solution available with Big Navi and on all other RDNA2 gpu's
Big navi is not going to affect console performance or ray tracing.
The consoles are going to have a custom zen 2/navi chip in them based on current tech, so I doubt any hardware solution for ray tracing is going to enter it. Their GPU is going to basically be a 5600-5700 performance at best. Ray tracing solutions for AMD are all going to be software for this generation.
Originally Posted by skupples
I'd prefer to buy in like that, but seeing how PhysX went, NV is probably 100% anti-addin cards. hell, they barely even acknowledge mpgu as being a thing anymore.
unfortunately, this is the only way, since its a transitional period as we move towards a completely different way of building games, etc. We'll be emulating games from 2020 in not too many more years
and yeah, like dude said. latency. 2nd card = inherently added latency.
Since multi GPU has been dead because of DX12, both AMD and nvidia have stopped really moving in that direction.
DX12 and vulkan are suppose to have natural support in multi GPU, which killed SLI/CFX support. So until those get better, multi GPU work is basically dead.
Regarding physx, it is a completely different matter than ray tracing. Using an addon for physx (which you can still do today though), was possible because the calculations were not part of the rendering. They needed to calculate how things move and destroy, not how to render and what color they are going to be.
So ray tracing on a second dedicated card is not going to work, because ray tracing is part of the rendering and lighting of the scene itself, something you can't offload in async compute to another GPU.