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
Parents
  • Note: This was originally posted on 21st March 2013 at http://forums.arm.com

    Hi Irfan,

    I don't think it will make any difference moving to OpenGL ES 3.0 unless you *need* to use ETC2 since OpenGL ES 2.0 only supports ETC1.

    I suspect the problem must be in the texture loader code, not recognizing the output file from the Mali Texture Compression Tool.

    Can you tell us more about what engine or library code you are calling to load the textures? If I were investigating this I would try and debug the code to step through and find where the error message is generated, and which test is performed just before the error message is reported - this should narrow down which part of the file format the loader thinks is wrong.

    HTH, Pete
Reply
  • Note: This was originally posted on 21st March 2013 at http://forums.arm.com

    Hi Irfan,

    I don't think it will make any difference moving to OpenGL ES 3.0 unless you *need* to use ETC2 since OpenGL ES 2.0 only supports ETC1.

    I suspect the problem must be in the texture loader code, not recognizing the output file from the Mali Texture Compression Tool.

    Can you tell us more about what engine or library code you are calling to load the textures? If I were investigating this I would try and debug the code to step through and find where the error message is generated, and which test is performed just before the error message is reported - this should narrow down which part of the file format the loader thinks is wrong.

    HTH, Pete
Children
No data