Search Issue Tracker
Won't Fix
Votes
5
Found in
2021.3.38f1
2022.3.29f1
6000.0.3f1
Issue ID
UUM-72321
Regression
No
Trail Renderer visual doesn't match the positions of vertices when they have been offset
Reproduction steps:
1. Open the attached “TrailOffsetTest.zip” project
2. Open the “SampleScene” scene
3. Enter the Play mode
4. In the Game view press the “Space” button on the keyboard a few times
5. Observe the Game view
Expected result: The Trail Renderer visual is offset correctly and no spikes are visible
Actual result: Spikes are visible on the Trail Renderer visual
Reproducible with: 2021.3.38f1, 2022.3.29f1, 6000.0.3f1
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- Also reproducible in the Player
- Both SetPosition() in a loop and SetPositions() provide the same result
-
Mackerel_Sky
Jul 05, 2024 08:12
Hi everyone, I downloaded 2022.3.36 and confirmed that this issue no longer persists.
-
Mackerel_Sky
Jul 03, 2024 08:28
Hey! I recently saw that this issue is getting some attention. I just downloaded it and verified that the issue persists in the latest LTS version of Unity, 2022.3.35f1. I'll wait and see if 3.36 fixes it.
-
Mackerel_Sky
May 18, 2024 11:51
More information is contained in the forum post below!
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
The issue here is that the particles spawned this frame get spawned with the new transform and then offset, which means that they get the offset applied twice.
A simple fix is just to change the order in the script, first apply the offset, then transform the position of the scene objects. This seems to work properly and it has no side effects