mipmap levels can be 0 and they should be interpreted as 1#11767
mipmap levels can be 0 and they should be interpreted as 1#11767superdump merged 10 commits intobevyengine:mainfrom
Conversation
doonv
left a comment
There was a problem hiding this comment.
I feel like we should give a warning when the mipmap level is invalid instead of just silently fixing the problem.
|
I agree that a warning would be nice. Unsure if we can get away with a |
We could make it only happen when |
Head branch was pushed to by a user without write access
|
Now it should be properly done, sorry for the spam, I thought everything was ok, but 2 minute later rust analyzer came back with more problems |
|
Looks like CI is still missing an import of |
Thanks, didn't check all features. Still learning how to work with git/github and this project. I am a mercurial person |
|
I don't know how to get around the duplicated versions problem, I guess there is not much I can do. Seems to be |
|
Yeah, the duplicated dependencies is not your problem: it's the result of us updating versions. Won't block the merge though. |
|
Is there anything else I can do to get this merged? |
| /// Load a bytes buffer in a [`Image`], according to type `image_type`, using the `image` | ||
| /// crate | ||
| pub fn from_buffer( | ||
| #[cfg(all(debug_assertions, feature = "dds"))] name: String, |
There was a problem hiding this comment.
This is a public API, so this will break bevy plugins using it if the "wrong" build configuration is enabled by the user.
tracing allows attaching this information to a Span instead, which is a better way to do this (the warn_once! will include the span's fields).
Objective
Loading some textures from the days of yonder give me errors cause the mipmap level is 0
Solution
Set a minimum of 1
Changelog
Make mipmap level at least 1