Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.2.0f1
2023.3.0a14
Issue ID
UUM-57061
Regression
No
FBXImporter Preset settings are not applied when importing an FBX asset
Reproduction steps:
1. Open the “ImporterRepro“ project
2. Open the Preset Manager window (Edit > Project Settings > Preset Manager)
3. Add a new Preset field to the FBX Importer by clicking the “Add to the list“ button
4. Set the Filter property to “Test123“
5. Make sure the Preset property is set to “ModelStaticImporter”
6. Import the “Test123” asset to the project
7. Observe the “Test123“ asset’s Import Settings in the Inspector window
Expected result: The “ModelStaticImporter“ Preset settings are applied
Actual result: The Import Settings remain unchanged
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.2.0f1, 2023.3.0a14
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Notes:
Restarting the Editor after setting the Preset field fixes the issue and the Preset settings are applied when importing the asset
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.