Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.2.X
Votes
0
Found in
2020.3.39f1
2021.3.9f1
2022.1.16f1
2022.2.0b7
2023.1.0a10
2023.2.0a1
Issue ID
UUM-14809
Regression
No
FBX textures do not get extracted when clicking the 'Extract Textures' button in the Inspector
To reproduce:
1. Open the project “TestFBXImportBug”
2. Select the Sign in the Assets → Models
3. Select the Materials tab in the Inspector
4. Click the “Extract Textures” button in the Inspector
5. Choose the “Textures” folder
Expected result: The .fbx file (DirectionSign) gets extracted to the “Textures” folder
Actual result: The “Textures” folder is empty
Reproducible with: 2019.4.31f1, 2020.3.39f1, 2021.3.9f1, 2022.1.16f1, 2022.2.0b7, 2023.1.0a10
Reproduced on: macOS Monterey 12.5.1 (Intel)
Notes:
- 2022.2.0b7, 2023.1.0a10 thorws Error “NullReferenceException: SerializedObject of SerializedProperty has been Disposed” after the steps above
- “Extract Materials” button works fine
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The issue is with Blender and not Unity.
Resolution Note (2023.2.X):
The issue is with Blender and not Unity.