Soldato
- Joined
- 8 Jun 2018
- Posts
- 2,827
I can't remember now, it may have been a YT vid by Hardware Unboxed or someone, AMD said the problems with Navi, was because they were broken at a hardware level.

Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
I can't remember now, it may have been a YT vid by Hardware Unboxed or someone, AMD said the problems with Navi, was because they were broken at a hardware level.
As for the ray tracing stuff... I didn't see the value last gen at all, same with DLSS. It just isn't in enough games yet. I'm not convinced with the incoming generation either as I just don't feel the fidelity offered is there yet... it's not a must have for me especially considering the hit to frame rate. The new consoles will force it into more games but as for how good it will look? I need more convincing.
Always moving goalposts.
So multiple people proving what you're saying is hogwash is now "moving goalposts"? Jog on, pal. Post again when you have something constructive to say.
Typical childish response when faced with cold hard facts.
Your a troll and a not very good one at that.
Quit trying to stir up controversy in this AMD thread, its more than obvious it is what you are doing, and equally as transparent you are a blatant Nvidia fanboy.
I am using a 2080 ti SLi setup and I don't like the performance drop with RTX on...I won't be enabling RTX on Ampere or RDNA2 cuz it's going to be the same story... I won't be possibly using RTX till the performance drop is less than 2%... which might take 3 or more generations of upgrades (I doubt this, the problem seems intractable)..RTX is a waste of computational power which could have been used elsewhere. I am upgrading my knowledge about RTX in the meanwhile..but it's looking nothing more than a grunt approach to IQ
Perfect mature rationale, from this guy.
If you want to join the rush to adopt it fine, you dont have to preach to everyone that they need it - thats right out of Jensen's book, playing into his hands.
Isn't it usually the 3rd iteration of a new technique where it starts working flawlessly, or at least close to flawless? RTX 2000, introducing ray tracing, get games to start using it, RTX 3000, improve performance a bit but still waiting on games to incorporate it efficiently, then RTX 4000 where games now use it properly and the hardware can run it a lot better. So it's next year/2022 where we'll get ray tracing with little performance loss, it'll be interesting to see what AMD do, RDNA3 is meant to be MCM, splitting parts like Ryzen so we'll probably have a die for the shader units, a die for the I/O and possibly a die for ray tracing if they want to push it hard.
Unfounded rumors. Which is why I asked for the source that he alleged amd said themselves that it was a the issue.There actually were a few rumours from people that some of the driver issues were caused by defects in some of the hardware which is why it has taken so long to fix some of the problems
I'm reluctant to make a thing of this because people in here have a habit of holding it against you when you get your speculations wrong, but, count the CU's in this slide, ignore the blue tab on the side actually count the CU's on the diagram. 20 in each array. 8 arrays.
![]()
I think I have ignored the cpu instructions dispatching pipeline..couldn't see something of that sort delineated in the Xbox dieshot.. probably that needs to be sized as well.. what would be a good approximation?
But there is also the possibility that 536 mm2 is pure BS.. or the RGT dude is on the money with his infinity cache leaks... just too many factors.. should listen more to peaceful music.
While i think that idea of being able to use some CU for Ray Tracing is possible
I have read the hybrid ray tracing patent.. and am somewhat confident that the leak isn't making sense.. AMD will rely on fixed function ray triangle intersection hardware and the shaders are just supposed to control the traversals..looking at the schematics that have been leaking it seems the dedicated hardware will either be inside the CU or the cluster, it's a bit nebulous
Something is up with the 80 CU rumour
He posting on here to much.
Let's hope RGT Paul can shine more light, er leaks. Somehow he has been copiously absent from the scene post the coreteks leak
I have read the hybrid ray tracing patent.. and am somewhat confident that the leak isn't making sense.. AMD will rely on fixed function ray triangle intersection hardware and the shaders are just supposed to control the traversals..looking at the schematics that have been leaking it seems the dedicated hardware will either be inside the CU or the cluster, it's a bit nebulous
I can't remember now, it may have been a YT vid by Hardware Unboxed or someone, AMD said the problems with Navi, was because they were broken at a hardware level.
AMD will never admit to there being hardware bugs in Navi 1 that contributed to driver problems. I've tried to find a source but no, it won't happen. It's going to remain a rumour or maybe even escalate to an open secret, but it will never be confirmed.Unfounded rumors. Which is why I asked for the source that he alleged amd said themselves that it was a the issue.
As of now there isnt any.
Let's hope RGT Paul can shine more light, er leaks. Somehow he has been conspicuously absent from the scene post the coreteks leak
Edit: typo
Is it me or has he slightly changed the way he speaks, slightly higher pitch and more clear? Could be the effect of not seeing his face on screen thoughLLLLLadies and gentlemen, my names Paul, and in this redgamingtech.com video......
![]()
Is it me or has he slightly changed the way he speaks, slightly higher pitch and more clear? Could be the effect of not seeing his face on screen though![]()