/explore
|
You are here 
|
simonschreibt.de | ||
| | | | |
fgiesen.wordpress.com
|
|
| | | | | This post is part of the series "A trip through the Graphics Pipeline 2011". Welcome back! This post deals with the second half of pixel processing, the "join phase". The previous phase was all about taking a small number of input streams and turning them into lots of independent tasks for the shader units. Now... | |
| | | | |
timur.hu
|
|
| | | | | Mesh and task shaders (amplification shaders in D3D jargon) are a new way to process geometry in 3D applications. First proposed by NVidia in 2018 and initially available in the "Turing" series, they are now supported on RDNA2 GPUs and are part of the D3D12 API. There is also an extension in Vulkan (and a vendor-specific one in OpenGL). This post is about what mesh shadig is and next time I'm going to talk about how mesh/task shaders are implemented on the driver side. | |
| | | | |
logins.github.io
|
|
| | | | | Compute Shaders in D3D12 Why Talking About Compute Shaders Direct Compute has been part of DirectX since version 10. Its usages are multiple, but in general we can use the compute pipeline whenever we want to calculate something without the need of a rasterizer. This ability to generically adapt to any type of calculus makes the compute pipeline really useful in many areas, not only for real-time applications, but also for many science-related computations. In science, every operation that involves the word "GPGPU" (General Purpose GPU) has some kind of compute shader usage in it: high performance computing, physics simulations, classification, image processing are just to scratch the surface among the multitude of use cases. In a game engine, compute shader... | |
| | | | |
feertech.com
|
|
| | | In which we write our first simple machine code | ||
