- Home /
Baking data and move project
Hi, I would like to know one thing. I may choose texture compression, so I choose quality to 100% That's taking a lot time, especially with many textures and switching first time platform. But later It's quite quick. My question is: If I put this on asset store, client will have those data baked and will wait between switching platform as me on secong time (2-3 minutes) or as at first, which takes almost 4 hours? I've got i7 4790k and I may put it all on night to make it easier for other users, and I would like to avoid responding from other users like: "your asset freezes unity on import".
Answer by Baroque · Jan 25, 2017 at 06:13 AM
Texture compression happens on the user's end, unfortunately.
It's also frustratingly single-threaded and there's nothing you can do to speed things up.
The only way to skip the import step right now is to build the textures into an assetbundle and load that instead. If this is for the asset store, your users would probably prefer the flexibility of the original files, even if it does take a long time to import.
Your answer

Follow this Question
Related Questions
16-bit compression makes textures transparent? 1 Answer
How to disable texture wrapping caused by compression? 2 Answers
Assigning UV Map to model at runtime 0 Answers
Import Image larger than 2048x2048 1 Answer
Modifying textures like TextureImporter does with normal maps importer, but run a custom shader 1 Answer