Re:Don't "optimize" conditional moves in shaders with mix()+...
by Cieric on Sunday February 09, 2025 @07:43PM
(#42995715)
In the case that does happen, then we don't apply that setting. Most of the changes applied are extensively tested and toggles like that are more often used for already broken shaders.
[ Parent
| on HN ]
Re:Don't "optimize" conditional moves in shaders with mix()+...
by chrisjj on Tuesday February 11, 2025 @04:43PM
(#43018730)
> In the case that does happen
You meant "in the case we find where that does happen"?
Little consolation for the cases you don't find because e.g. you cannot afford to play a game to the end.
Re:Don't "optimize" conditional moves in shaders with mix()+...
by Cieric on Thursday February 13, 2025 @10:50AM
(#43037109)
Fair enough, I can't say anything I've done has ever caused an issue like that (A new ticket would have been made and sent to me.) But I also can't say that it has never happened, so I'm not really in a position to disagree. We do have a good QA team though and we have an "open" beta program that also catches a lot of issues before they become more widely public.