A GDC 2015 talk in which Natalya Tatarchuk describes the multithreaded renderer Bungie built for Destiny. It covers the low-latency architecture across platforms, its successes and its challenges.
Why Hacker News points people here: HN commenters cite it as the go-to talk on a job-system-based multithreaded game engine architecture.
“I think this is the video the parent mentioned, in case anyone is interested”
Identifies the video the parent comment mentioned
Full comment
Thanks. Apparently fallout4 has a bunch of bugs on higher-end PCs because and I was wondering why they would couple things like that. I guess the harsh restrictions of gamedev explain it a bit then... btw, I think this is the video the parent mentioned, in case anyone is interested: this video
Cites itcpetersoApr 2017
“I saw some GDC talks about the multithreaded game engine for Bungie's Destiny game.”
Cited talk on Destiny's multithreaded engine architecture
Full comment
Are there any AAA game studios using or evaluating Rust yet? I saw some GDC talks about the multithreaded game engine for Bungie's Destiny game. Given the debugging and QA challenges of their multithreaded architecture, something like Rust's ownership model seems like a good fit. Does the Rust toolchain support Xbox and PlayStation? * Destiny's Multithreaded Rendering Architecture: this video * Multithreading the Entire Destiny Engine: link
Cites itmeheleventyoneSep 2020
“The renderer talk is here”
The renderer talk using a job system
Full comment
I believe it’s only been mentioned in passing and likely will be talked about at conferences soonish. Here’s a HN thread from when it was first talked about: link There was an early talk about using a job system to run the Destiny renderer and then this one for the whole engine which is a very similar premise to the way DOOM(2016) and then DOOM Eternal evolved. link The renderer talk is here: this video