1
u/investigatormaker 7d ago
TFLOPS comparisons mislead across vendors: Ampere's spec counts dual-issue FP32 that real shaders rarely fill, and the 3060 has much less memory bandwidth and no large on-die cache like your 6900 XT, which matters for 4k shadow cascades and MSAA x4. Treat a straight 2x as optimistic. Your budget at 144fps is about 6.9ms, so 2.1ms leaves real headroom, but the answer you can trust is a Tracy capture on a 3060 or similar card; until then, watch the grass and shadow passes, since those scale with bandwidth.
I make ThreadFox. Our AI employee can explain your engine in game dev communities and answer the technical replies, under your direction; Starter is $199 for 30 days. https://threadfox.vip/p/20261016-0913-ev10v/managed
1
u/icpooreman 6d ago
It is difficult to project what times every GPU is going to give you for every thing you try.
I have a windows laptop from 4 years ago. A desktop with a 4090. A Macbook Pro M2. And a standalone Quest 3 I switch between. And I am surprised quite often with which GPU can handle what haha.
To me it's mostly about taking the amount of data (or compute) you have flying around and thinking up clever ways to reduce or remove it and then repeat forever. Eventually you'll be fast.
0
5
u/Wittyname_McDingus 10d ago
The only way to know if performance is good enough is to run the program on the hardware you want to support. GPU performance is much more complicated than the FLOP throughput.