yuzu/yuzu-emu.github.io
1
0
Fork 0
mirror of https://github.com/yuzu-emu/yuzu-emu.github.io.git synced 2025-08-01 14:42:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update index.md

Browse source
This commit is contained in:
Honghoa 2021-09-10 15:38:32 -03:00 committed by GitHub
parent aa516ad80e
commit d557561ab1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
site/content/entry/yuzu-progress-report-aug-2021/index.md
View file

@ -27,10 +27,9 @@ Also, do note that, in some rare cases and conditions, it can still happen.
The cause of the problem boils down to the drivers of *a certain vendor* not properly reading shader attributes near a `demote` or `discard` instruction.
Among the many programs that run in the GPU to render graphics, fragment shaders are in charge of calculating the colour of every pixel written into the frame-buffer that will be sent to your screen.
In some cases, these shaders are used instead to perform subordinate calculations, such as derivatives.
This is a problem, however, as fragments shaders are *always* expected to write into the frame-buffer.
Since the colour data of these shader instances are uninitialized, this is undefined behaviour that will most likely result in rainbow-puke graphics being sent to your screen.
Among the many programs that run in the GPU to render graphics, fragment shaders are in charge of calculating the colour of every pixel written into the frame-buffer that will be sent to your screen. In some cases, these shaders are used to perform subordinate calculations instead, such as derivatives.
This is a problem, however, as fragments shaders are *always* expected to write into the frame-buffer. When used like this, the colour data of these shader instances remains uninitialized, which is undefined behaviour that will most likely result in rainbow-puke graphics being sent to your screen.
This is where the `demote` and `discard` instructions come in to the rescue.
They are used to mark these fragment shaders, so that the colour of every shader instance that is demoted is ignored, keeping the thread alive to perform calculations while the frame-buffer remains untouched.