Search Issue Tracker
Fixed in 2.0.1
Votes
0
Found in [Package]
1.0.0, 1.0.5
Issue ID
1182792
Regression
Yes
Multiple warning messages are logged/spammed in the Console window when modifying alembic (.abc) asset in the Inspector window
How to reproduce:
1. Open the attached 'project-1182792.zip' project
2. In the Project window select 'alembicCube.abc'
3. In the Inspector window modify 'Scale Factor' value
Expected result: multiple warning messages are logged in the Console window
Actual result: no warning messages are logged in the Console window
Reproducible with: 2019.2.0a6, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6 (1.0.0, 1.0.5)
Not reproducible with: 2018.4.10f1, 2019.2.0a5 (1.0.0, 1.0.5)
Could not test with: 2017.4.32f1 (Package Manager not available)
Additional notes: editing 'Geometry' or 'Cameras' areas produces a different warning message than changing 'Scene' values
Modifying 'Scene': OnInspectorGUI should call serializedObject.Update() at its beginning and serializedObject.ApplyModifiedProperties() before calling ApplyRevertGUI() method.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Modifying 'Geometry' or 'Cameras': OnInspectorGUI should call serializedObject.Update() at its beginning and serializedObject.ApplyModifiedProperties() before calling ApplyRevertGUI() method.
UnityEditor.PopupCallbackInfo:SetEnumValueDelegate(Object, String[], Int32)
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
- "Problem detected while importing the Prefab file" errors on Learning Templates import
- Crash on RaiseException during Socket.BeginConnect in Player when application connection is blocked through commercial firewall
- [Linux] Silent crash when generating lighting
- Decal Projector produces artifacts when the normal and decal are projected in negative z-direction and Normal Blend is set to 1
- Undoing slider field change only resets slider position, doesn't undo the value change
Resolution Note (fix version 2.0.1):
This bug is now fixes in the latest version of the Alembic package (2.0.1-preview.1)