Doubling console performance has gone from $250 2.7 years into a generation to $800 4 years into a generation. This is not at all comparable to the 1060.
Value of Hardware Unboxed benchmarking *spawn
- Thread starter Phantom88
- Start date
Technically, rasterising is just the mathematical process of transforming triangle (or HOS) geometry to a flat screen-space or buffer. Back in the early days of CG and drawing flat triangles, we either raytraced them or rasterised them. Rasterising was faster and how GPUs were designed to work, and so everything they did became 'rasterising' regardless how complicated the process became. We can include texture sampling and shading in that process, but things like projecting shadows probably doesn't come under that. Calculating LOD probably doesn't come under that.
It might be worth drawing up a reference list of everything a GPU does, or maybe a graphics pipeline does as perhaps the CPU gets involved, and then identify different hardware solutions to different steps, and see what really is 'rasterisation' and what's 'ray tracing' and what's 'something else presently with no name'. And maybe a name can be found for the other stuff and the overlap?
I think this definition is the only one that enables proper debate. It doesn’t make sense to me to bucket workloads under “raster” when those workloads are equally applicable to a fully raytraced implementation. You still need to texture and light your pixels with raytracing. Those aren’t rasterization specific and use the same hardware either way.
If there are performance or quality tradeoffs when doing a texture lookup from a ray hit vs a pixel shader we should discuss that. But texturing isn’t a rasterization specific workload.
DegustatoR
Legend
That's my point: people use the "rasterization" word as if it means "everything which isn't RT h/w" while "rasterization" is just one step of traditional rendering pipeline in h/w with most of other steps (again, in h/w) being used even for pure PT. So the whole division is misleading, RT won't work without general purpose FP32 processing units whatever you'd call them, it won't work without memory load/store units, without the very same caches, even without texture filtering h/w (you could do the same calculations via shaders of course but this again won't be "RT h/w").
But when people are using this distinction they mean "using RT h/w" vs "not using RT h/w". Which is a rather pointless distinction as you can render the exact same graphics with or without any h/w - even without a GPU at all.
@DegustatoR I think most gamers are not aware of what a rendering pipeline is, or what a hardware rasterizer is. Technically the rasterizer is a fixed way of doing ray tracing for primary visibility, I guess.
I think you've basically got it right. In the context of this forum I've always thought of it as a shorthand for the standard raster pipeline in opengl, vulkan, d3d that includes the rasterizer stage. But like you said, it gets blurry because we say ray tracing when we mean DXR, when I think pretty much all games still use the rasterization stage, including Nanite-enabled UE5 games that use it as a fallback for large triangles.
It's more like graphics pipeline without DXR = rasterization vs graphics pipeline with DXR = ray tracing. Like most people wouldn't call a UE5 game with software lumen ray tracing, even though it is. I think the settings menus in games are pretty much responsible for this, because in that context ray tracing almost always means DXR hardware-based ray tracing.
I think you've basically got it right. In the context of this forum I've always thought of it as a shorthand for the standard raster pipeline in opengl, vulkan, d3d that includes the rasterizer stage. But like you said, it gets blurry because we say ray tracing when we mean DXR, when I think pretty much all games still use the rasterization stage, including Nanite-enabled UE5 games that use it as a fallback for large triangles.
It's more like graphics pipeline without DXR = rasterization vs graphics pipeline with DXR = ray tracing. Like most people wouldn't call a UE5 game with software lumen ray tracing, even though it is. I think the settings menus in games are pretty much responsible for this, because in that context ray tracing almost always means DXR hardware-based ray tracing.
I'm not sure I understand that line of thought that led to the conclusion in this post ...
Just because a particular IHV implements a lot of special HW states for specifically accelerated pipelines (GFX/compute/RT), it doesn't necessarily mean that they'll always have fastest implementation for those certain sets of pipelines. Developers will use those features if it makes sense (RT pipeline/texture sampling/etc) for their use case or other more programmable features (bindless/compute shaders) as well and IHVs can't force developers to use API/features that they don't like such as vertex buffers or tessellation ...
More specialized HW implementations aren't always better since it can make it harder for them to do work balancing/distribution compared to more flexible HW implementations as we saw in the past before the advent of unified shading pipelines or more recently async compute. At the end of it all, competitive hardware design isn't purely about mutually exclusively subscribing to diametrically opposed philosophies between special hardware acceleration or dynamic repartitioning schemes for hardware resources since in the real world IHVs are forced to find the optimal balance to match common API usage patterns ...
DavidGraham
Veteran
Take for example ray marching techniques, used nowadays to renders stuff like volumetrics (clouds, fog, smoke، god rays, ... etc), used also for advanced shading, screen space shadows, screen space reflections and others, people still classify them under rasterization, despite them having very little to do with rasterisation!
Cappuccino
Newcomer
Why would DLSS cause stuttering lol
Btw 960 was 200, 1060 was 250. I don’t care that neither of these cards did 4k, as even top end cards didn’t do 4k.
I understand liking Nvidia hardware but this generation was universally considered overpriced and that’s why the Super refreshes came out.
davis.anthony
Veteran
DLSS does cause stuttering, just like it did in The Witcher 3 next gen update.
1060 6GB was $300 in 2016.
Nearly $400 in 2024 when adjusted for inflation, which is 4060ti money.
So what's your problem with cost again?
Top end cards still can't do 4k in the best AAA games.
Adjust the prices for inflation and then talk.
davis.anthony
Veteran
1060 6GB was $299
DegustatoR
Legend
Frame generation specifically, not DLSS, and it is a result of a bad implementation which can be fixed - and is usually fixed with game patches.
I've never heard this claim anywhere. Where is this coming from? This? https://www.pcgamesn.com/cyberpunk-2077/dlss-3-stutter-fix
Only Founders Edition, MSRP for the rest was $249 like 760
Edit: just because I know you won't take my word for it because NVIDIA can't do wrong anywhere
NVIDIA GeForce GTX 1060 6 GB Review
Today, NVIDIA released the GeForce GTX 1060, which is designed to combat AMD's Radeon RX 480. It looks like NVIDIA has won this fight since the GTX 1060 brings GTX 980 performance levels to the table while being much more power efficient than the RX 480 - all at a price point of $249 to $299.
Last edited:
raytracingfan
Newcomer
I'm not claiming specialized HW is inherently faster for a given task. Just that the current trend with games - including Nvidia-sponsored titles - is that the vertex shader pipeline is becoming less important and therefore the HW Nvidia dedicates to it will have less and less value but RT HW will only increase in value.
Nanite Skeletal Meshes and Nanite Foliage are leading to a future in which all UE5 geometry is Nanite, and Epic is doubling down on HWRT with Lumen and MegaLights. Alan Wake 2 uses mesh shaders on any GPU that supports it and has multiple RT options. Avatar: Frontiers of Pandora and (presumably) Star Wars Outlaws use mesh shading (on consoles) and have multiple RT options. AC Red will have ray tracing and some form of virtualized geometry. Capcom's next iteration of the RE Engine will support mesh shaders and double down on RT.
The logical conclusion is that Nvidia will eventually ditch the dedicated HW that only works with the vertex shader pipeline but continue to improve on RT performance.
Another reason why I think bundling FrameGen into "DLSS" was a stupid idea from Nvidia..