Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0f2
Issue ID
928231
Regression
No
[Timeline] Prefab loses a track in timeline when it's instantiated from Asset Bundle
To reproduce:
1. Open project attached by the user
2. Build asset bundle in project window (right mouse click -> Build Asset Bundles)
3. Open "Source" scene in Source folder
4. Hit play and notice that prefab changes its Y position
5. Open scene "Player" in Player folder
6. Hit play and notice that the same prefab instantiated from Asset Bundle remains still
7. Open timeline editor and notice that there is no track for instantiated prefab
Expected: Prefab instantiated from Asset Bundle should behave exactly the same as prefab which was manually placed to the scene.
Actual: Prefab instantiated from Asset Bundle looses its track in the timeline.
Reproduced with: 2017.1.0b1, 2017.1.0f3, 2017.2.0b2
Note: Instantiating prefab via script with Instantiate() method works as intended.
Comments (3)
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
julian_cruz
Aug 30, 2018 20:15
This fix landed in Unity 2017.4, I suggest using that version due to is our LTS version at this moment.
ohbado
Jan 20, 2018 08:25
When will patches for Unity 2017.1 be released?
hoopsnake
Aug 31, 2017 19:30
What editor version is this fixed in?