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
-
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.
-
We generate our command lists in parallel, then submit them in-order to the back-end that does some re-ordering/shuffling/instancing based on the back-end and then goes wide again to submit. Dependencies are explicit, but sometimes a lot of data to sort through.
- 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.