You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no workflow for images embedded in glTF files.
What solution would you like?
Targeting multiple platforms is awkward.
The asset processor should have general support for target platforms - this is not specific to images (see Bevy Asset V2 Tracking Issue #9714 under "Per-Platform Processed Assets").
Assuming that general API is added, the compressed image saver might just need some light restructuring.
The default processing behavior is inflexible.
Adding settings to ImagePlugin seems like the obvious solution, at least for the short-term.
Embedded images are not supported.
Open question, and arguably a general asset processing issue.
Also depends on if/how the glTF loader ends up working with BSN.
Maybe this gets solved as a side effect of other pipeline changes or processor improvements.
What alternative(s) have you considered?
The default processing behavior is inflexible.
Users can register their own default processor for other file extensions (but can't remove the one ImagePlugin adds).
Users can add .meta files to override the default processor.
Embedded images are not supported.
For glTFs, users can compress the images themselves or resave the glTF with non-embedded images.
What problem does this solve or what need does it fill?
#23567 and #24223 improved the compressed image workflow by adding BCn/ASTC support, mipmapping, and other features. However, there's some problems:
compressed_image_saverandcompressed_image_saver_universalfeatures).ImagePlugin:::buildregisters a default processor that automatically compresses*.jpg, *.png..tgaetc).What solution would you like?
ImagePluginseems like the obvious solution, at least for the short-term.What alternative(s) have you considered?
ImagePluginadds)..metafiles to override the default processor.