Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
Issue ID
1063505
Regression
No
Problem recording custom components
Bug coming from @metroidsnes in the forum:
https://forum.unity.com/threads/feedbacks-for-experimental-feature-gameobjectrecorder-2017-1.467852/page-3#post-3570587
-------
Hi, I have some problems with recording custom components.
1. Recording does not always work
2. Custom component order on the target gameobject influence which component is recorded
All this is visible on the video. First I try to record the component which I could record before but this time it doesn't work. Then I change component order on the gameobject to show that other component is recorded than the one binded. At the end I revert the component order and the component which wasn't recorded previously, now works.
Video: https://www.youtube.com/watch?v=m7azgTN8lSk
Project: https://1drv.ms/u/s!ApyPqduXdyo-kqRN3ebkAyO2N_hbgg
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment