Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
Issue ID
967405
Regression
No
Animation recorder: Error in console when recording MonoBehavior scripts or third party plugin components
GitHub issue: https://github.com/Unity-Technologies/GenericFrameRecorder/issues/42
Description copy:
Having a custom MonoBehavior script assign to my object and set the recorder to record it, we get errors in the console. Also true for cinemachine components (or 3rd party plugins).
All the errors seem to be related to marshalling types.
Error:
ArgumentException: Cannot marshal CinemachineMixingCamera to a native Unity::Type!
Steps to repro:
1. Import the attached package
2. Load the Scenes/Recorder_Bug scene
3. Try to record the "Character Movement" component from the "UnityCharacter" object
- Note that any simple MonoBehavior scripts show the same issue.
4. Also try to record the "Cinemachine Virtual Camera" component of the "CM vcam1" object
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- 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
Add comment