Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.4.14f1
Issue ID
1108339
Regression
No
Mesh compression on fbx cause huge memory usage and wrong assetbundle build
Steps to reproduce:
1. Open user attached project
2. Change the mesh （in fbx named "QJC_HS_Afandian01"）compression to low and apply it
3. Click on top menu item BuildTools/build
4. using WebExtract & binary2text (on Mac: /Applications/Unity2017.4.14f1/Unity.app/Contents/Tools, on Win: Unity2017.4.14f1\Editor\Data\Tools )to extract the bundle which was built
- notice that you get a bundle taking over a gigabyte of space
Reproduced in: 2018.1.0a3, 2017.4.18f1, 2017.3.2f1
No repro in: 2019.2.0a1, 2018.3.3f1, 2018.2.20f1, 2018.1.9f2, 2018.1.0a4
Does not occur since: 2018.1.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment