Search Issue Tracker
Won't Fix
Votes
2
Found in
5.6.1p1
Issue ID
932350
Regression
No
Every texture becomes fixed size after build when Load Behavior on SBSar is set to Bake
To reproduce:
1. Download and open attached "sbsarBakeBug.zip" project.
2. Expand "model_sbsar" asset to view all the textures.
3. Notice the size of each texture(respectively 1024x1024, 512x512, 1024x1024, 512x512).
4. Select "model_sbsar" asset and check "Override for Android" option to true.
5. Set "Load Behavior" option to "Bake and Keep Substance" or "Bake and Discard Substance" and press Apply.
6. Build application for android.
7. Notice that All textures under "model_sbsar" are 512x512 size.
Expected result: Textures do not change their size after build.
Actual result: Textures change their size to 512x512.
Reproduced with: 2017.2.0b3, 2017.1.0f3, 5.6.2p4.
Notes: Textures get corrupted with 5.5. When Load Behavior is set to any other than "Bake" everything works correctly. Also reproduces on Standalone. To reproduce follow the same steps only for standalone platform.
Comments (2)
-
LaFabula
Aug 21, 2017 16:12
Same here. Renders substances unusable in unity.
-
chromecat
Aug 09, 2017 10:30
Me too having this issue. When this will be fixed?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2018.1.X):
No longer applicable since Substance support was removed from 2018.1.