Search Issue Tracker
By Design
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.1.21f1
2022.2.0b13
2023.1.0a16
Issue ID
UUM-19088
Regression
No
Visual effect is in the wrong position for a few frames when using Point Cache
Steps to reproduce:
1. Open the “test987654” project
2. Open “Scene_Firework” scene, which is in _Scenes folder
3. Enter Play Mode
4. Press F1 and observe the firework in Game view
Expected result: The fireworks are shooting up in a one straight line
Actual result: For a few frames visual effect’s position is in the left of the firework
Reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.21f1, 2022.2.0b13, 2023.1.0a16
Reproduced on: macOS Monterey 12.2 (Intel)
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
- Directional shadows render only according to first Directional Light when the second Directional Light is the brightest light
- Entities are jittering when Temporal Anti-aliasing (TAA) is applied
- The drawing order of Transparent objects is incorrect when changing the Material from Opaque to Transparent with GPU Resident Drawer enabled
- Sprite animations do not update when Animator parameters change in the Player
- [iOS] Memory increases significantly when a TMP Text component has a lot of text
Resolution Note:
The issue is a consequence of using the block "Add Position from Map" without providing the point count. It can easily be avoided by checking the "Use Point Count" property and linking the point count from the point cache to the block.
More information:
The point cache in the attached project has 362 points, while the generated texture containing the data is 20x20 (400 points). Because no point count is provided, the size of the texture will be used to generate the random indices. When an index greater of 361 is used, the sampled data will be invalid.
I would recommend always providing the point count when sampling from a point cache.
Please refer to the description of "Use Point Count" found on the documentation:
Use Point Count (Bool): When enabled, you can specify the number of points contained in the attribute map. This is useful when the number of points actually contained in the attribute map is smaller than the texture size. If disabled, the block considers that the number of points is equal to the size of the attribute map texture.