Comment

Comment on Jensen Huang says gamers are 'completely wrong' about DLSS 5 — Nvidia CEO responds to DLSS 5 backlash

So this dumb fuck’s own marketing material has said this operates off final pixel colour and motion vectors (for temporal stability presumably) - that says to me that it’s not working with actual geometry info at all. It probably has a step to infer geometry but it’s still just a fancy Instagram filter working with limited data and an obviously ill-suited training set.

source

Sort:hotnew top

lb_o@lemmy.world ⁨4⁩ ⁨hours⁩ ago
Oh, thanks for pointing that out.

Ignoring that current version looks sloppy, as a gamedev I would accept extra AI beautification post processing step as additional feature, but I would never accept corporation getting their hands into my beloved geometry.

source
kromem@lemmy.world ⁨3⁩ ⁨hours⁩ ago
That’s what he’s saying. That it doesn’t change the geometry or textures (still completely controlled by the devs) and that the parts that it does change are also tunable by the devs.

He’s responding to the backlash about how it changes models/textures (which it doesn’t) by saying those are still fully in the hands of the devs and the parts people are seeing in the demos can be fine tuned by the dev teams to match their vision for what they want it to do or not do (like change lighting on material surfaces and hair but not character faces as an example).

source
- nightlily@leminal.space ⁨14⁩ ⁨minutes⁩ ago
  It’s a post-processing screen space effect. At that point, there’s zero control the game can have over the geometry. If the AI model wants to change it, it can. It fundamentally can’t only operate on lighting like the marketing claims, it can only make a hallucinating best-effort statistical guess at what the geometry in the final image should be.
  
  source
lime@feddit.nu ⁨7⁩ ⁨hours⁩ ago
the previous versions at least need the software to supply motion vectors. otherwise it’s just guesswork. i’m assuming there will be some way to supply lighting information as well.

whatever the final product can do, they certainly didn’t show it off in their examples.

source
- orgrinrt@lemmy.world ⁨6⁩ ⁨hours⁩ ago
  Technically, at least on vulkan, these things can be inferred or intercepted with just an injected layer, though it’s not trivial. If you store a buffer history for depth you can fairly accurately compute an approximation of actual mesh surfaces from the pov of the view. But that isn’t the same as real polygons and meshes that the textures and all map to… pretty sure you can’t run that pipeline real time even with tiled temporal ss. Almost definitely works on the output directly, perhaps some buffers like motion vectors and depth for the same frame that they’ve needed since dlss2 anyway. But pretty suspect to claim full polygons, unless running with tight integration from the game itself, even then the frame budgets are crazy tight as it is, nevermind running extra passes on that level
  
  source
  - SkunkWorkz@lemmy.world ⁨6⁩ ⁨hours⁩ ago
    Probably not meshes since it is way too expensive. But these guys write the GPU drivers, so they of course have access to the different frame buffers and textures buffers and light source data. So just from depth and normal map data you can get a good representation of geometry. Like deferred rendering lights the scene from the 2D images in the G-Buffer not geometry.
    
    source