Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2023.2.0a1
Issue ID
UUM-25386
Regression
No
“Property _TRANSPARENCY already exists in the property sheet with a different type: 3“ error when importing a FBX file with a default material with a shader
How to reproduce:
1. Open the attached project “FBXImportIssue.zip“
2. Observe the error in the Console
Expected result: No error in the Console
Actual result: “Property _TRANSPARENCY already exists in the property sheet with a different type: 3“ error in the Console
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0a26
Reproduced on: macOS 13.0.1 (Intel)
Note:
- User reported that the error call comes from “PhysicalMaterial3DsMaxPreprocessor.cs” line 209
- The error no longer appears after importing the model to Blender and exporting back to Unity
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.