Search Issue Tracker
Won't Fix
Votes
3
Found in
2020.2.0a12
2020.3.36f1
2021.3.4f1
2022.1.6f1
2022.2.0a17
2023.1.0a1
2023.2.0a1
2023.3.0a3
Issue ID
UUM-9534
Regression
Yes
FBX Model colors are imported incorrectly when importing with Linear Color Space
Reproduction steps:
1. Open the attached project
2. Drag the "Test1.fbx" file from the project's folder to the Editor's Project window
3. Drag the "Text1.fbx" Model to the Scene view and observe its colors
4. Change the Color Space to Gamma (Edit > Project Settings > Player > Other Settings > Rendering)
5. Drag the "Test2.fbx" file from the project's folder to the Editor's Project window
6. Drag the "Text2.fbx" Model to the Scene view and observe its colors
Expected result: The colors are the same when the Color Space is in Linear or Gamma
Actual result: The colors are different
Reproducible with: 2020.2.0a12, 2020.3.36f1, 2021.3.4f1, 2022.1.6f1, 2022.2.0a17, 2023.1.0a1
Not reproducible with: 2019.4.39f1, 2020.2.0a11
Reproducible on: Windows 10 (21H2)
Notes:
- The Materials used on the Model are named after their correct color hex code, so you can use them to check if the Material color is actually correctly imported
- Sometimes the behavior is reversed (correct color in Linear and incorrect in Gamma)
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 GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
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.