Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.68f1
6000.0.62f1
6000.2.12f1
6000.3.0b10
6000.4.0a4
6000.5.0a1
Issue ID
UUM-126476
Regression
No
VFX Graph Prewarm Time field displays different number of decimal places when edited via text drag
Reproduction steps:
1. Create a new project
2. Install Visual Effect Graph package in the Package Manager
3. Create Visual Effect Graph Asset (Create > Visual Effects > Visual Effect Graph)
4. Select any of the templates in the Create new VFX Asset window and double-click newly created Asset to open VFX Graph window
5. Click on triangle icon next to Compile button
6. Change Prewarm Time value by moving the slider or pressing the arrow keys and observe the field value
7. Change Prewarm Time value by clicking and dragging directly on the “Prewarm Time” and observe the field value
Actual result: Changing the value with the slider or keyboard shows up to two decimal places (e.g. "1.59”), but dragging on the text shows up to seven decimal places (e.g. "0.6997994")
Expected result: Changing the value by dragging on the text shows up to two decimal places just like changing the value with the slider
Reproducible with: 2022.3.68f1, 6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a4, 6000.5.0a1
Reproduced on: macOS Sequoia 15.4 (M4)
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
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.