Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0f1
2023.3.0a14
Issue ID
UUM-56243
Regression
No
Animated custom properties are not accessible in the Editor when imported from an FBX file
Reproduction steps:
1. Create a new project
2. Import the user-attached “ExportScene01_Text.fbx” file by dragging and dropping it to the Project window
3. Select it in the Project window
4. Ensure that the “Import Animated Custom Properties” option under the “Animation” tab in the Inspector is checked
5. Scroll to the bottom of the Inspector and click on the “Apply” button (if it is greyed out, skip this step)
6. Expand the imported FBX file in the Project window and select any of the 2 animations available
7. Inspect the animation in the Animation window and look for the property “my_prop”
Expected result: The property 'my_prop' exists and its curve can be seen
Actual result: The property 'my_prop' does not exist
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a14
Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested
Notes:
- To ensure that the FBX has the actual property data, open the fbx in any text editor (like VS Code or Notepad) and search for “my_prop”. If it is found, the property exists in the FBX but is not recognized by the Unity Editor
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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Resolution Note:
While investigating this ticket, I made my own model with an animated custom property exported from Blender. Initially, this also did not work, but after exporting the model from Maya, the animated custom property appeared in the Animation window.
I then looked at the code that imports properties and found that the property was not getting imported due to missing the flag marking it as a user defined property. To check for this flag, I opened both the customer's fbx file and the one I made and located the custom properties in both. I found that my file had an "A+U" parameter next to the property name while the customer's only had an "A+" parameter.
Adding the "U" to the customer's file made the property show in editor.