Search Issue Tracker
Fixed
Fixed in 6000.2.0a10
Votes
1
Found in
2022.3.61f1
6000.0.46f1
6000.1.0b14
6000.2.0a8
Issue ID
UUM-102710
Regression
Yes
A NullReferenceException error is thrown when extracting textures from an FBX
How to reproduce:
1. Create and open a new project
2. Import any FBX file with embedded textures
3. Click on the imported FBX
4. In the Inspector, select the “Material“ tab and click “Extract Textures“
5. Select any path to extract the textures to, and continue
6. Observe the Console
Expected result: Nothing is logged
Actual result: A NullReferenceException error is logged
Reproducible in: 2022.2.0a6, 2022.3.61f1, 6000.0.46f1, 6000.1.0b14, 6000.2.0a8
Not reproducible in: 2022.2.0a5
Reproduced on: Windows 11 Pro (24H2), macOS 15.3.2 (by reporter)
Not reproduced on: No other environment tested
Notes:
- The textures seem to get extracted correctly
- Part of the error reads: “NullReferenceException: SerializedObject of SerializedProperty has been Disposed.“
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment