Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a1
2019.1.10f1
2019.2.0a1
2019.3.0a1
Issue ID
1173531
Regression
No
Changes in Scene triggers Mesh data optimization when building AssetBundle using ScriptableBuildPipeline
Steps to reproduce:
1. Open User-supplied project ("ScriptableBuildPipelineIssue.zip")
2. Select AssetBundle - > Build, notice the mesh optimization job
3. In the Project window -> Sprites -> MyAtlas change the padding property
4. Repeat step 2
Expected: the mesh optimization does not reoccur
Actual: mesh optimization does not reoccur
Reproduced in: 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Not reproduced in: 2017.4.30f1, 2018.4.5f1
Note: *Can't build the Asset Bundle due to errors
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
- “Create and publish WebGL builds” link leads to “Sorry about that, we can't find the page you're looking for.” page
- " Suspected crash in FXC. " shader compiler errors are thrown in a new project when creating a project in Hub with a very long name but below the maximum character threshold
- Long cloud names stretch the space in Hub when the Project dropdown is opened
- OpenGLES3 Graphics API can be used with the "Linear" Color space on unsupported GPUs resulting the error spam
- [Windows] Recommended and Downloaded Learn tabs are empty and have scrollbar
Resolution Note:
MyAtlas is referenced by SampleScene4, changing MyAtlas invalidates the cache for the bundle containing SampleScene4. Since the output of scenes are required as an input to Mesh data optimization, it was running again to see if any of the meshes need to be rebuilt due to optimizations changing. In this case the result is that no optimizations have changed, thus the only rebuilt bundle is SampleScene4. This can be verified by looking at the timestamps of the resulting bundles. This is working correctly as expected.