-
-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grayscale textures (LumaU8) showing up in red #931
Comments
It seems to be related to images producted from numpy arrays with python's PIL library |
This could be fixed by either rendering with a special shader for grayscale images, or since many other common formats like rgb8, bgr8 and rgb16 all have a clone and convert step, "unsupported" image types like Luma could be converted as well. A PR would involved changing
|
jzimmerman135
changed the title
Texture is only showing up in red
Grayscale images (LumaU8) showing up in red [EDITED]
Jul 24, 2023
jzimmerman135
changed the title
Grayscale images (LumaU8) showing up in red [EDITED]
Grayscale images (LumaU8) showing up in red
Jul 24, 2023
jzimmerman135
changed the title
Grayscale images (LumaU8) showing up in red
Grayscale textures (LumaU8) showing up in red
Jul 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to render a calibration background, but the black and white marker textures are being drawn in red instead of white for some reason.
I don't think it's a problem with wgpu because I got it to work in bevy earlier.
This is a minimum reproducible version. I'm on MacOS with Arm64 M1.
These images were created with the opencv api.
The text was updated successfully, but these errors were encountered: