4 ms·

Long post about rendering. Not a single pretty image. What gives?

• arianvanp 9y ago
  It's more about generic code structuring and scheduling than some breakthrough in shader or path tracing technology. It's worth a read
• phkahler 9y ago
  Yeah, I started skimming and at the end got the impression it was a thought piece and the author hadn't even coded anything yet. I also kept wondering why the new terminology instead of "scene graph". There's probably a difference, but I didn't find it compelling enough to read in depth.
  • jbister 9y ago
    A scene graph and a "render graph"/Frame graph in Frostbite terminology are not the same. I would recommend checking out: http://www.gdcvault.com/play/1024656/Advanced-Graphics-Tech-Moving-to http://www.gdcvault.com/play/1024656/Advanced-Graphics-Tech-... and https://www.gdcvault.com/play/1024612/FrameGraph-Extensible-Rendering-Architecture-in https://www.gdcvault.com/play/1024612/FrameGraph-Extensible-... for a more in depth view. I would describe it as such: A scene graph specifies _what_ needs to be drawn, while a render graph specifies _how_ it should be drawn and what the dependencies of each step in drawing is. For example, a render graph is used to reduce the number of image layout transitions in a frame by looking at what layout is expected for each operation and figuring out where to put the layout transitions, instead of letting a human place the layout transitions which will inevitably lead to unnecessary transitions when the scene becomes complex enough. I didn't think this article was bad even if it is maybe less concrete than the slides I linked.
• jochung 9y ago
  It's not about what you render, but how you render.