Search Issue Tracker
Won't Fix
Votes
6
Found in
2018.4
2019.4.10f1
2020.2
Issue ID
1280356
Regression
No
Trail's starting point is incorrect when it's rendered with BakeTrailsMesh and using World Space
How to reproduce:
1. Open the attached project's Scene labeled "issue"
2. Enter the Play Mode
3. In the Game View, observe the trails
Expected result: Particle System trail and trail rendered with ParticleSystemRenderer.BakeTrailsMesh look the same
Actual result: Trail rendered with ParticleSystemRenderer.BakeTrailsMesh has a different trail starting point from the referenced Particle System when trails use World Space
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b5
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
i dont know if we can fix this. i'm tempted to say it's by design, but i agree it's an undesirable situation.
the problem appears to be that the particle travels along the Z axis, but the baked trail also tries to face the Z axis, because it is baked using the main camera, which is pointing down the Z axis.
Unfortunately we aren't able to prioritise trying to devise a fix for this at the moment.
You should be able to see a correctly baked trail if the trail travels along a different axis compared to the one the camera is facing.