Search Issue Tracker
Won't Fix
Votes
2
Found in
2023.2.15f1
6000.0.0b12
Issue ID
UUM-66896
Regression
No
FBX models are unwrapped when the "Generate Lightmap UVs" setting is disabled and the project contains a lot of FBX models
Triage note: This was assigned to the Enlighten area which is wrong. I suggest that someone looks into the asset import problem first. Then, if it turns out that there is a lighting issue, please pass it on to the Light Transport Team with investigation notes.
Reproduction steps:
1. Delete the library folder from the attached “ASDQWE” project
2. Open the project
3. Wait ~1 hour and search for "UnwrapCL.exe" processes
Expected result: There are no such processes
Actual result: There are numerous such processes
Reproducible with: 2023.2.15f1, 6000.0.0b12
Could not test with: 2021.3.36f1, 2022.3.22f1 (Could not downgrade the project due to package and asset dependencies)
Reproducible on: macOS Sonoma 14.3.1 (Intel), Windows 11 (user’s)
Not reproducible on: No other environment tested
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.