Steps to produce: Minecraft Java Edition 1.19.4 with Optifine installed, load shaders that uses temporal effects (like PTGI, irradiance cache, and so on), press F3+R to reload shades, or smaller window size as described below.
Since driver 23.7.2, there is an issue that greatly affect some Minecraft Java Edition shaderpacks. If the clear in every frame is disabled for some buffer, then the first frame of this buffer will be extremely strange. Below image provides the image after reloading shaders, using the shader from https://github.com/GeForceLegend/SEUS_PTGI_GFME . Since the first frame is filled with random data, GI on hand becomes extremely bright (ground initial data will not pass depth check so GI on ground looks correct).
Another thing might relates to it is the strange output when smaller window size. When using the shader provided above and resizing window to smaller, screen will be filled with extremely black and white area, and irradiance cache on reflection will also become strange. Is the pointer of buffer changes without initialization, making shaders reading polluted data, and then creates tons of nan or inf?
There are additional images: I modded another shader, and reading a buffer with clear disabled that is never writed. The first image is loading the modded shader after loading the unmodified one, I get the last TAA frame from the unmodified shader with some noise (part of this noise looks like data from other buffer). Since the TAA data comes from unmodified shader, but current loaded shader is the modified one and it never writes to this buffer, this frame never changes even if moving player camera. And if I reload shader for more times, or launching game with modified shader on, then the result is a pure black image with noise looks like data from other place.
Possible reason in my opinion: Optifine (the shader loader mod of Minecraft Java Edition) does not clear buffer when declare a buffer, but clear it on the begin of every frame; but if disable the buffer clear on the begin of each frame, this buffer is never cleared. Maybe on the driver before 23.7.2, or other vendors' card, the buffer is cleared on declaration; but from driver 23.7.2, declare a buffer will not clear its memory, unless developer call a glClear manually.
Tested on machine:
1 Solution
