Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.3.0f3
Issue ID
981387
Regression
Yes
ParticleSystem.Update produces low performance when VR is enabled
To reproduce:
1. Open the attached project;
2. Open "Bug" scene;
3. Make sure Virtual Reality is enabled (Edit > Project Settings > Player > XR Settings);
4. Enter Play mode;
5. Find the ParticleSystem.Update in the Profiler
Expected result: ParticleSystem.Update takes ~0.00ms.
Actual result: ParticleSystem.Update takes multiple ms and produces low performance when VR is enabled.
Reproduced on versions: 2017.3.0f3, 2017.3.0p1, 2018.1.0a7.
Not reproduced on versions: 2017.2.1p1, 2017.3.0f2.
By design: We cannot simulate the particle system until the previous frame is finished drawing it (otherwise we risk modifying data that the render thread is still using).
VERIFIED Fixed 2018.3.0b5
Comments (1)
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
Nikodemus
May 28, 2019 13:46
This is still an issue in 2019.2.03b!