Closed rparrett closed 3 years ago
Although I'm still not completely sure about the mechanism by which this occurs, I have been seeing an issue with projects using bevy_webgl2 and custom pipelines specifically in Chrome (stable, beta, and canary) on macOS 11.2.3 (intel, radeon).
https://github.com/vleue/bevy_zhuose_qi (the fire shader specifically) https://github.com/Nilirad/bevy_prototype_lyon/
Are affected, but bevy itself seems to generally work fine.
It seems that the CameraViewProj and and (any other uniform) both end up bound to (0, 0). This is resulting in a "grey screen, no errors" situation.
This change set fixes the issue in both projects for me.
Although I'm still not completely sure about the mechanism by which this occurs, I have been seeing an issue with projects using bevy_webgl2 and custom pipelines specifically in Chrome (stable, beta, and canary) on macOS 11.2.3 (intel, radeon).
https://github.com/vleue/bevy_zhuose_qi (the fire shader specifically) https://github.com/Nilirad/bevy_prototype_lyon/
Are affected, but bevy itself seems to generally work fine.
It seems that the CameraViewProj and and (any other uniform) both end up bound to (0, 0). This is resulting in a "grey screen, no errors" situation.
This change set fixes the issue in both projects for me.