Search Issue Tracker
Won't Fix
Votes
1
Found in
4.3.3f1
Issue ID
593203
Regression
No
Rarely mesh will not be animated on the mobile device
Sometimes the object is not animated on the mobile device, however the issue is not reproducible after running the same scene in the editor and rebuilding the application.
Reproduced on:
Google Nexus 5 Android 4.4.2
Reproduced with:
Unity Version 4.3.3f1 (c8ca9b6b9936)
Unity Version 4.3.4f1 (e444f76e01cd)
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
SeelOfQuality
Aug 06, 2014 01:32
More details from another case we've seen:-
* Either the 'run scene in editor before build' workaround is unreliable, or in larger scenes it is necessary to load not only the scene the non-animated model appears in but for the model itself to appear on-screen and be animated in the editor.
* In cases where a bad build occurs, the output .apk file (or .obb file, if using split application binary) is slightly smaller than a correct build from the same project. Possibly the animation data itself is missing from the build(?)
SeelOfQuality
Aug 01, 2014 02:02
We have seen this issue occur in multiple completely separate 4.3.4f1 projects on both Mac and Windows PC using both Android Free and Pro. In these cases there were only a small number of scenes, making it easy to use the work-around of running once in the editor, but it seems like this bug could cause subtle but severe problems in a larger/more complex project.