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
-
How do you specify the graph? Our system (have had for many years) generates a list of render commands, then we can build dependency graph in rendering back-end (per frame) if necessary. Have always found retained graph code clunky to work with.
We also generate rendering commands, but each command is submitted with a dependency list. So you can declare nodes up front, then fill their commands out of order (ideal for MT engines). The dependency graph is just whatever the dependencies were submitted as.
-
-
I actually like the idea of a retained graph, but it requires more work to set up, IMO, and I’m not yet sure about any benefits. Not retained makes it have an “ingui feel” and that’s quite liberating.
-
I keep getting stuck on the edge cases: what if the graphics settings change? What if you go into a different rendering mode? Generating everything every frame works well.
- 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.