I reproduced it, but just once in 10 minutes of trying.
Unfortunately I’ve no idea what could cause this, it is not even sure it depends on the shader, which may just trigger an underlying problem with Retroarch.
Under those conditions, it is really hard for me to debug, so if this issue is important enough ® for you, since you are able to reproduce it more than me, and it appears that it worked fine in the past, I ask you to try to bisect the issue and find the shader commit when it first started to happen.
I always make a commit for every single bit I change in the shader, so if you find the moment it broke (assuming the culprit is the shader), I will know what to change.
Bisection works like this:
- Find a commit ( good ) in the past where it worked.
- Find a recent commit ( bad ) where it doesnt.
- Test a commit ( test ) in the middle between the good and bad
-
If it works => Repeat 1,2,3 but with good = test
It it does not => Repeat 1,2,3 but with bad = test
- Stop repeating when there is no more to test.
At that point you can tell me the commit hash (that alphanumeric string near the <> symbol) that broke things.
Since it halves the commits to test in each step, usually it resolves pretty quicly, 10 tests at most, I’d say.
On github commit list is here
To download a commit snapshot from the past, click on the “<>” simbol to the right of the commit description as you see in the following shot:
…then hit green “<> code ∨”, and then “Download ZIP”
If you are comfortable with the command line, the process is far more quick than dealing with the github gui manually:
koko@thinkbook# git clone https://github.com/kokoko3k/slang-shaders
koko@thinkbook# git bisect start
status: waiting for both good and bad commits
koko@thinkbook# git bisect bad main
status: waiting for good commit(s), bad commit known
koko@thinkbook# git bisect good 64e9449
Bisecting: 130 revisions left to test after this (roughly 7 steps)
[2ad165e6bad70badbcdcbdd2d1ad84cb880126e2] Bloom limiter was using the wrong parameter
Test the shader, and tell git if the test has been good or bad, it will pick new commits for you to try each step, and in the end it will tell you where the problem lies, this is just an example:
[11:41:05] cd ~/koko-aio-slang
koko@thinkbook# git bisect bad
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[99d1f7262d712cc8be58ad5e22201f3e5e70bdeb] Better explain what tate mode related parameter does.
[11:41:10] cd ~/koko-aio-slang
koko@thinkbook# git bisect good
Bisecting: 1 revision left to test after this (roughly 1 step)
[97c01cb249fc4db9f58f9236b71540d6438a3570] Halation: Always apply to the whole image Dont modulate its strength on bright, since it doesn't look good under some circumstances (eg: big white text on black background)
[11:41:14] cd ~/koko-aio-slang
koko@thinkbook# git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[9931ad5ee768048dfdd7f5145b2abf6fda60b8c1] Implemented halation effect
[11:41:17] cd ~/koko-aio-slang
koko@thinkbook# git bisect bad
9931ad5ee768048dfdd7f5145b2abf6fda60b8c1 is the first bad commit
commit 9931ad5ee768048dfdd7f5145b2abf6fda60b8c1 (HEAD)
Author: Antonio Orefice <[email protected]>
Date: Wed Sep 24 12:34:21 2025 +0200
Implemented halation effect
config/config-user-optional-template.txt | 1 +
docs-ng.md | 16 +++++++++-------
shaders-ng/bloom_pass_4.slang | 32 +++++++++++++++++++++++++-------
shaders-ng/config.globals.inc | 4 ++++
shaders-ng/config.inc | 16 +++++++++-------
5 files changed, 48 insertions(+), 21 deletions(-)
