the only reason i have tendency to believe MS went with vega is that leaks for PS5 said its clocked at 1850 MHZ(which at the time sounded insane) and Dante dev kit at 1410 MHZ(already pushed to the max apparently based on the leak) . this to me means one is vega and one is navi given what we know today after amd computex.I don't know how I could ever stop thinking about it when this exact thing keeps getting posted over and over as justification for a rumor that came from nowhere and is being pushed REALLY hard on this thread with no actual evidence. XD. I mean, sure Vega could happen. But you know what? Jaguar COULD happen. MS hasn't specifically debunked that rumor, so FOR ALL WE KNOW. Personally, I think they're going back to the Pentiums on the CPU side. They used on in the Surface Go last year, so it's basically confirmed.
/s. Hard /s
At the end of the day, the hardware will be great on both sides of the divide. In our wild speculations, let's at least try to keep some semblance of being grounded in what little we know. Postulating that MS is trying to do this, so therefore they need this, because of this tenuous link, thus there is no other solution except this.. is all about as flimsy of argumentation as we can get. Trying to justify that conclusion with imagined evidence is just silly. Even if it were true, it would have been a dumb way to get there :/
I get the frustration, but I can also see why he wouldn't understand what you meant from what you said. I think most people here aren't trying to intentionally misrepresent you for what it's worth, but things are getting lost in translation and/or obviously lots of people fundamentally disagree with the assumptions you are making (and vice versa). Eh. Disagreements don't necessarily come from bad faith. Perhaps one day we will all understand each other and be happy. Hope springs eternal..
Then.. *boom* nuke of discord
I disagree. RT is fundamentally bounce computation. What's computationally intensive is calculating all the bounces it takes and then doing the filtering on that. So, what if you just did one bounce for all lighting locally? That would get you most of the way there - more than usable at least. If the bounce lighting is 2 frames behind or slightly noisy when you spin at high speed, I wouldn't call that "completely falling apart".
To be clear, I don't know if this tech is actually possible or exists. We certainly don't have the evidence for this working in this specific way, so I wouldn't pretend that this is confirmed or even likely in any way. But I don't think there's anything fundamentally wrong with this line of thinking. Put the critical tasks on the local machine, supplement it with cloud computation. You're not wrong to be skeptical though.
it could also mean that MS dev kit is only on vega and final product will be navi.