-
Notifications
You must be signed in to change notification settings - Fork 222
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
Some test images use incorrect KTXorientation key name #106
Comments
I noticed these when working on ktx2ktx2. It caused me to add a feature to drop such invalid metadata or optionally rewrite it during the conversion. I don't have a good way to fix these .ktx files as I don't have the original images. (I would really like to get those for the Yokohama cubemap). I will have to resort to a binary editor I suppose. Are you up for creating a PR with the fixes? |
No problem. I found the incorrect keys while working on a simple KTX inspection tool, which also can be used to fix the files. The real challenge was to review the changes in Git. On this subject, I'm working on a repository with custom KTX test files, including files with errors. Hopefully, that will be a useful contribution to the pool of test data for KTX tools. |
IIRC, I created |
I reported this to Imagination: https://forums.imgtec.com/t/pvrtextool-setting-incorrect-ktx-metadata/3024 |
@MarkCallow The original yokohama images are these I believe: They're JPG, but they appear to be higher quality than the KTX existing compressed versions (i.e. no terrible banding in the sky) |
Here's the ktx version: https://s3.amazonaws.com/Oculus/cubemap_yokohama_rgba32.zip |
oops... looks like I accidentally found the culprit for the original bug.... my cubemap was created using PVRTexTool, and it appears to have put the incorrect |
Thanks for the pointer to the Yokohama cubemaps. If I have time next week I'll try to create a Basis compressed .ktx2. I'd like to make new .ktx files of the ETC2, ASTC & BC3 versions as well. As I noted in an earlier comment, I posted in the imgtec forum as well. There has been no response. |
Whoops... should have read the whole thread I guess. |
No worry. The extra post in the forum will show multiple people are interested in a fix. |
I have noticed that some test images use the incorrect metadata key
KTXOrientation
(uppercase O), instead of the correctKTXorientation
:I don't expect anything to catch on fire because of this, but it seems worthwhile to mention it.
The text was updated successfully, but these errors were encountered: