-
Notifications
You must be signed in to change notification settings - Fork 235
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
Use of the --format flag? (v4.3 alpha) #726
Comments
It is the value to be use for the vkFormat field of the KTX file's header. Good questions. @VaderY please clarify the documentation. |
When using with The format will be used to verify and load all your input files into a texture before encoding, The |
This is a great explanation. Please add it to the docs. |
Thanks! One further question. Suppose I know the image is an ambient occlusion texture, and that the data I care about is in the R channel. I'm not sure whether the image contains other data in the G or B channels, but I'm sure those channels do not matter for my application. Could I safely choose |
Yes you can safely use |
The new
--format
flag is described in the CLI help text as:From this description I'm left wondering, "KTX format enum [of what?]". If I weren't specifying
--encode uastc
I might assume that the source texture will be encoded into the specified format. If I were, I might assume either (a) I need to choose specifyVK_FORMAT_UNDEFINED
(as required for UASTC output) or (b) some enum value that abstractly describes the structure of the input data, even if the source format (e.g. PNG) uses a very different pixel data representation.Clarification on this flag's help description would be very helpful, particularly as it is a required flag. Thanks!
The text was updated successfully, but these errors were encountered: