Good point, it’s getting better, but often print statement debugging is not available in shaders either, and you have to resort to the visual form of print debu

Good point, it’s getting better, but often print statement debugging is not available in shaders either, and you have to resort to the visual form of print debugging: outputting a tinted color. Crude, but often enough it’s plenty effective. Personally, I mentally put shader tint debugging in the same category as CPU print debugging.