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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment