It's interesting to see how the doubled CUDA cores work that some, but not all, people are trying to call out as misleading. It is a bit more nuanced than many realize.

What used to be only INT32 cores can now be FP32 cores when needed. Being that those formerly INT32 cores can now be FP32 cores there are twice as many potential FP32 CUDA cores. Nvidia could have tweaked their phrasing to make that bit more clear perhaps. It is accurate enough to state double CUDA cores. Especially, as Gamers Nexus mentioned, in gaming you tend to use more FP32 cores than INT 32 cores anyway.

In case some don't know INT32 is 32 bit Integer math and FP32 is 32 bit Floating point math. Integers are whole numbers only, no decimals or fractions. Floating point means the decimal can be anywhere, which adds complexity to the calculation. Floating point is important for precise calculations(your GPU is truly a super complex math & geometry calculating machine truly) because fixed decimal points are simply too limited. 

Judging by this breakdown of the architecture I would *speculate* that in tomorrow's benchmarks we will see significantly greater performance gains in Ray Tracing and DLSS, while standard rasterization won't see as much of a performance increase. I've been very skeptical about some of the early benchmarks floating around personally. This could explain why some of those benchmarks have shown what appear to be dubious performance increases. 

If that speculation is correct then for those that are interested in getting above 60 fps using Ray Tracing these will be desirable cards. For those less interested in Ray Tracing the 3000 series might be less desirable. 

Although we won't know for sure until we see benchmarks from trusted reviewers.

Looking forward Ray Tracing appears to be the new PhysX. Physics processing was regarded as gimmick early on, and is now standard and normalized. It would seem that Ray Tracing will become the new standard, and rasterization will become old tech. Especially when both next gen consoles and AMD's RDNA2 are adopting Ray Tracing technology to keep up with Nvidia.

torick

Intoxicus

In case some don't know INT32 is 32 bit Integer math and FP32 is 32 bit Floating point math. Integers are whole numbers only, no decimals or fractions. Floating point means the decimal can be anywhere, which adds complexity to the calculation. Floating point is important for precise calculations(your GPU is truly a super complex math & geometry calculating machine truly) because fixed decimal points are simply too limited. 

Why do we use INT32 at all then if FP32 covers all numbers no matter if odd,even, before and after a decimal? Just trying to learn some more. 

Correct me if I'm wrong but INT32 should be faster than FP32

So does INT32 find the whole number and then FP32 find anything behind the decimal? So if I have a number of 142.6523 triangles the INT32 side finds the 142 triangles and the FP32 will do the .6523 triangle portion? Do they work in conjunction with each other?
 

Digital Foundry's 4K benchmarks of Doom Eternal, should be all we need for now. 120fps and above at 4K .. you can tell Doom Eternal is set to global Ultra Nightmare graphics settings just by looking at it .. I think the perf is in the pudding .. Nvidia will come out smelling like a rose when it's all said and done... just waiting for AMD now.

the_Scarlet_one

torick
So does INT32 find the whole number and then FP32 find anything behind the decimal? So if I have a number of 142.6523 triangles the INT32 side finds the 142 triangles and the FP32 will do the .6523 triangle portion? Do they work in conjunction with each other?
 

My understanding could be incredibly skewed, as I don’t truly understand a whole heck of a lot, but I would assume FP32 would be the primary in games, because geometric shapes make up the game and they are rarely a whole number in size. Each shape would be a different size, even if only slightly, and would need the FP32 precise scaling to get it correct.

I don’t know if both Int32 and FP32 can coexist on the same geometric shape, but if one shape was a whole number and the shape next to it is calculated using a decimal location, then maybe they can work together.

I would also like to understand this better, so hopefully we can get someone with more knowledge to help us out :-)

 
I was doing some digging on google and from what I read is that both INT32 and FP32 are both needed because FP32 is limited on the size of calculations it can accomplish by the power of ten.

torick

the_Scarlet_one

torick
So does INT32 find the whole number and then FP32 find anything behind the decimal? So if I have a number of 142.6523 triangles the INT32 side finds the 142 triangles and the FP32 will do the .6523 triangle portion? Do they work in conjunction with each other?

My understanding could be incredibly skewed, as I don’t truly understand a whole heck of a lot, but I would assume FP32 would be the primary in games, because geometric shapes make up the game and they are rarely a whole number in size. Each shape would be a different size, even if only slightly, and would need the FP32 precise scaling to get it correct.

I don’t know if both Int32 and FP32 can coexist on the same geometric shape, but if one shape was a whole number and the shape next to it is calculated using a decimal location, then maybe they can work together.

Yes, they can coexist but are unlikely to. Remember in the video from GN he specifically states that most gaming GPU calculations are FP32.

The real limit is 32 bits. The 32 bits(4 bytes) per number is how many ones and zeros the number can use in binary. We use a base 10 system of math and it's converted to binary and back by the CPU or GPU to do the math. Which gets very complicated to think about converting base 10 into binary and back to base 10. Machine langauge seems like a headache to me. Blessed are those that have and can code at machine level.

Personally I'm kinda curious why GPUs do not use FP64 and INT64 instead(64bit limit.) Whatever that reason is, it's beyond my knowledge.

I hope you two don’t mind, I added a quote bracket to each of your posts and one was lost and it was causing a running quote. That was the only edit I made, to clean up your posts :-)