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

Problem with convertion files (v4.3.0-alpha3) #733

Closed
Yason83 opened this issue Jul 8, 2023 · 5 comments
Closed

Problem with convertion files (v4.3.0-alpha3) #733

Yason83 opened this issue Jul 8, 2023 · 5 comments
Assignees

Comments

@Yason83
Copy link

Yason83 commented Jul 8, 2023

While performing file conversion (files attached in the archive), the command line
ktx create --format R8G8B8A8_SRGB --encode basis-lz --clevel 5 --qlevel 255 baseColor_22.png baseColor_22.ktx

Problems

  1. Fails to convert the files.
  2. The error message is not displayed.
@MarkCallow
Copy link
Collaborator

The example command says baseColor_22.png but there is no such file in the zip file. I tried with baseColor_18.png. It worked. Here is the result:

Screenshot 2023-07-09 at 21 24 51

You need to provide a lot more information about the problem. What do you mean "Fails to convert the files?"

@Yason83
Copy link
Author

Yason83 commented Jul 9, 2023

I tested on Windows11 64 (v4.3.0-alpha3)
After running the script, the result is not saved
ktx create --format R8G8B8_SRGB --encode basis-lz --clevel 5 --qlevel 255 baseColor_18.png baseColor_18.ktx2

48

@MarkCallow
Copy link
Collaborator

MarkCallow commented Jul 10, 2023

It appears to be a Windows-specific problem. I was previously trying on macOS/arm64. When I try on Windows/arm64 I get no output file and no errors as reported in this issue. I also get no warning messages from create. I didn't get any on macOS either. I'm specifying R8G8B8A8_SRGB format with baseColor_18.png as input.

In the debugger, I'm getting an access violation exception at line 815 in image.hpp. Two questions: why the violation and why does the app silently exit? @VaderY please investigate.

@VaderDev
Copy link
Contributor

Successfully reproduced it. Will look into it ASAP.

@VaderDev
Copy link
Contributor

The issue was typo that caused miss addressing. I will add additional tests to cover these and post a PR later today with the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants