Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.44f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
2023.2.0a3
Issue ID
UUM-27604
Regression
No
Artifacts visible when transforming any vector from world space to tangent space
Reproduction steps:
1. Open the “MikktspaceWorldToTangentRepro” project
2. Open the Assets/Scenes/SampleScene.unity scene
3. Select Assets/ReproModel.fbx asset in the Project Window
4. In the Inspector Window notice that the "Tangents" property is set to "Calculate Mikktspace”
5. Rotate the “ReproModel” GameObject in any axis and observe it
Expected results: “ReproModel” GameObject is rotated
Actual results: Artifacts are visible on the “ReproModel” GameObject after and during it’s rotation
Reproducible with: 2020.3.44f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a25, 2023.2.0a3
Reproduced on: Intel MacOS 13.1
Notes:
- The issue is also visible if the "Tangents" property is set to “Import” and on the “ReproModelWithUV” GameObject
- When the "Tangents" property is set to "Calculate Legacy" or "Calculate Legacy With Split Tangents" the issue disappears
- The issue is not visible on the “ReproModelWithUV” GameObject in 2022.2.2f1
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
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.