Search Issue Tracker
Fixed in 2022.2.18f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a12
Votes
0
Found in
2022.2.13f1
2023.1.0b10
2023.2.0a9
Issue ID
UUM-32413
Regression
Yes
VFX globalTime variable constantly grows when using Playables API
Reproduction steps:
1. Open the attached project “VFXbug”
2. Open the scene “Assets/Scenes/SampleScene”
3. Enter the Play Mode
4. Observe the Console Window
Expected result: The logged values are looped from 0 to 1
Actual result: The values are constantly increasing
Reproducible with: 2022.2.0a17, 2022.2.13f1, 2023.1.0b10, 2023.2.0a9
Not reproducible with: 2022.2.0a16
Couldn't test with 2020.3.47f1 (The globalTime variable is not implemented), 2021.3.22f1 (The globalTime variable is not implemented)
Reproducible on: Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment