Skip to content
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

Saving an RGBE9995 texture slice to PNG fails (all pixels transparent) #3151

Closed
reduz opened this issue Nov 26, 2023 · 2 comments
Closed

Saving an RGBE9995 texture slice to PNG fails (all pixels transparent) #3151

reduz opened this issue Nov 26, 2023 · 2 comments
Labels
Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue

Comments

@reduz
Copy link

reduz commented Nov 26, 2023

Description

Attempting to save a texture slice in RGBE9995 format to PNG fails, resulting in transparent image.

Steps to reproduce

Take a RGBE9995 texture being inspected and save it:

image

Result is a transparent texture (pasted here, but its transparent..):

image

Texture should expected to be visible (converted to RGB).

Environment

  • RenderDoc version: 1.29
  • Operating System: Ubuntu
  • Graphics API: Vulkan
  • GPU: Gefocre 1650
@baldurk baldurk added Bug A crash, misbehaviour, or other problem Unresolved Waiting for a fix or implementation labels Nov 27, 2023
@baldurk
Copy link
Owner

baldurk commented Dec 5, 2023

I am also unable to reproduce this. I don't have your exact case, but saving an RGB9E5 texture to png works as expected to me, the pixels have proper data and aren't transparent. I can't tell if your png was intended to be black-transparent and that's the bug, or if you just had transparent pixels with valid data in RGB and it's been corrupted somewhere on the way to the github issue.

image

a.png

(image resized for visibility, here's the original: a.png ).

Can you please share a full and complete reproduction case I can use to reproduce your exact issue, as it may be something more specific than you have detailed here.

If you have another system available, it would also be helpful to check on a different driver or GPU in case this is a driver issue. You didn't say which driver version you're using, so it would also be worth checking to see if a driver update is available.

@baldurk baldurk added Need More Info More information is needed from a user to work on this issue and removed Unresolved Waiting for a fix or implementation labels Dec 5, 2023
@baldurk
Copy link
Owner

baldurk commented Jan 5, 2024

Closing this due to lack of activity from the reporter and no further information to investigate.

If you are the reporter and this bug is still a problem for you, or you are someone finding this issue and you believe this bug is still a problem and you have more information to share, please do not comment here and instead please open a new issue. You can reference this issue if you wish, but opening a new issue prevents confusion of accidentally linking two unrelated bugs and means that each issue can be handled in a clean process.

@baldurk baldurk closed this as completed Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue
Projects
None yet
Development

No branches or pull requests

2 participants