• State Accepted Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 137 subscribers
  • Views 19818 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bad astc textures with astc-encoder

Andrei

Hello.

I'm using the latest version of astcenc.exe from https://github.com/ARM-software/astc-encoder and have problems with several textures. 

For example:

astcenc.exe -c "Build_Foam.tga" "Build_Foam.astc" 8x8 -fast

astcenc.exe -d "Build_Foam.astc" "Build_Foam.astc.tga"

https://www.dropbox.com/s/vbgouzlqrf799g8/Build_Foam.tga?dl=0

https://www.dropbox.com/s/r11hzq3op7igj7f/Build_Foam.astc.tga?dl=0

But if I specify -hdra flag then the astc textures are ok. What I'm doing wrong?

Parents
  • 0 Arm Employee Badge in reply to Andrei

    The decompressed data for an ASTC file on the target device should always return 4 channels - but for Luminance + Alpha end points the RGB values will be identical (see section 3.8 in the ASTC specification in the GitHub repo).

    I'm not aware of any command line option to disable endpoints (although the HDR end points won't be used unless you enable an HDR mode).

Reply
  • 0 Arm Employee Badge in reply to Andrei

    The decompressed data for an ASTC file on the target device should always return 4 channels - but for Luminance + Alpha end points the RGB values will be identical (see section 3.8 in the ASTC specification in the GitHub repo).

    I'm not aware of any command line option to disable endpoints (although the HDR end points won't be used unless you enable an HDR mode).

Children
No data