Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.3.X, 2019.1.X, 2019.2.X
Votes
25
Found in
2018.3.13f1
2019.1.0f1
2019.2.0a11
Issue ID
1144643
Regression
Yes
Editor throws error when importing native 2.7x .blend file, imported file is not recognized
To reproduce:
1. Open user's attached project ("Blank_Project_2019")
2. Reimport all Assets
-- Error in the console, file is not recognized
Expected: File is imported, no error is shown
Actual: File is not imported, error is shown
Reproduced with: 2019.1.0f1, 2019.2.0a11
Not reproduced with: 2017.4.25f1, 2018.3.10f1, 2019.2.0a10
Note:
- Issue is reproducible even with newly created .blend file
- An error is thrown in the console:
"Blender could not convert the .blend file to FBX file.
You need to use Blender 2.45-2.49 or 2.58 and later versions for direct Blender import to work."
Fixed in:
2019.3.0a1
2019.2.0a14
Fix note:
In order for the fix to be effective, Blender 2.8 instead of 2.79 must be set as default program to open native .blend files.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment