koobas.hobune.stream
Unity's typical end-to-end pipeline of frame rendering
Hi,
For example let's take a build for Windows. Can anyone provide a good explanation of what happens during a single frame rendering (in all levels - Unity, DirectX, GPU, ...)?
From what I know: The app calls Draw() methods, they call DirectX API, which interacts with GPU, which processes the geometry and executes shaders ... and in the end we see that image on the screen.
Thanks in advance!
The manual has a nice page on Execution Order. Not quite as detailed as what you're looking for but I'm not aware of anything that shows that.
Thanks Dave,
Yes, that's not what I'm looking for - neither the level of details nor the "parties" involved. As a Unity developer I'd like to get a solid understanding of how different "parties" (Unity, DX, GPU) play together at runtime. To start with, a loose explanation with reasonable amount of details would be very illu$$anonymous$$ating.
