I’m a render graph fan. The ability to statically analyze graphics work and do per backend & per platform optimization, and also handle tedious error prone things (resource transitions!) is really cool.
Näytä tämä ketju
-
The idea being that graphics settings could change and affect the graph, but that it would only require a one-time "recompile" on the next frame. All of this happening on the front-end rather than at the back post-submission. Pie in the sky and all that though, not proven yet.
I've had similar thinking. One thing too, I don't like that a node of commands can be so diverse. It temps you to have one node that does an UpdateResource command right before a Draw command. Ideally, they're different nodes, easier to sort into queues.
-
-
Basically, finding the right abstraction that is easy up front and lightened the load on the back end.
-
I have a feeling this is going to depend a lot on engine architecture, details of the target rendering load, and engine team member opinions.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.