Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.5f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-42412
Regression
No
Pose variable format doesn’t change when changing its format
How to reproduce:
1. Open the user’s attached “PoseStringIssue.zip” project
2. Enter Play Mode and observe 2nd and 3rd printed lines in the Console window
Expected result: “Pose is ((0.123457, 0.987654, 0.555556), (-0.685469, 0.040838, 0.357384, -0.633042))” is printed
Actual result: “Pose is ((0.12, 0.99, 0.56), (-0.68547, 0.04084, 0.35738, -0.63304))” is printed
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproduced on: macOS 13.4.1 (Intel)
Notes:
Same results if the format is f1 or more
Reproducible if using: string.Format("Pose is \{0:f6}", pose) or $"Pose is \{pose:f6}"
Not reproducible if using: ToString("f6")
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.