-
Notifications
You must be signed in to change notification settings - Fork 622
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
DXT -> BCN? #1271
Comments
My preference would be to create a new I don't personally have plans to add support for other block compression formats, but PRs are welcome! |
Starting the revision from a clean slate in a new crate sounds preferrable for me as well. Note it's possible retro-fit the current implementation to instead use a crate. The only implementation that we (sadly) can't readily change is the A new crate could expose many more internals, as long as it's not a public dependency of |
I think it's better to map BC5 to R8G8, because not all textures use the "green" channel as alpha. e.g. normal maps |
@Waelwindows thanks for catching that! It probably isn't worth adding R8G8 as a format just to handle BC5, given that for decoder output La8 actually just means "a two channel format where even bytes are one channel and odd bytes the other". But you are right that the documentation should say that clearly somewhere so that users don't get confused |
I was just wondering if it would be a good idea to switch from
Dxt*
naming scheme toBcn*
in order to match Microsoft? Also, are there any plans to supportBC4
andBC5
sinceL8
andLa8
would map well to them?The text was updated successfully, but these errors were encountered: