Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.14f1
2022.1.24f1
2022.2.1f1
2023.1.0a21
2023.2.0a1
Issue ID
UUM-20763
Regression
No
Blender error is not specific when the Blender could not convert the .blend file to FBX file
Steps to reproduce:
1. Download the “IN-22336” project
2. Delete the “Library” folder
3. Open the project
4. Observe the Console
Expected result: The error “Blender could not convert the .blend file to FBX file.” specifies which file is not converted
Actual result: The error does not specify which file was not converted
Reproducible with: 2021.3.14f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a21
Could not reproduce with: 2020.3.41f1 (Console errors)
Reproduced on: macOS Ventura 13.0.1 (Intel)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.
Resolution Note (2023.2.X):
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.