Search Issue Tracker
Fixed in 14.0.2
Fixed in 13.1.8
Votes
0
Found in [Package]
12.0.0
Issue ID
1367447
Regression
No
Editor has unstable FPS when VFX graph is open
How to reproduce:
1. Open the user attached "1366167_FailureTest.zip" project
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. Change the Profiler to "Edit Mode"
4. In the Assets folder open the "Slowdown graph" VFX graph
5. Focus the Profiler window
Expected result: CPU Usage does not spike and is low ~1.0-2.0ms
Actual result: CPU Usage visibly spikes and is unstable ~4.0ms to ~20.0ms, sometimes higher ~100.0ms
Reproducible with: 10.7.0(2020.3.23f1), 12.0.0 (2021.2.3f1, 2022.1.0a15)
Couldn't test: 2019.4.32f1 (crashing when opening the graph)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 14.0.2):
Fixed in: 2022.2.0a12
Resolution Note (fix version 13.1.8):
Fixed in: 2022.1.8f1