Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.29f1
2021.2
2022.1
Issue ID
1408805
Regression
No
RaycastHit.m_UV contains wrong data when Particles intersect with Collider
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Press the Play button
4. Observe the bright blue pixel markings on the Quad in the Game view (for over a minute)
Expected result: painted pixel markings are made on the top half of the Quad where Particles are colliding (A-E rows)
Actual result: painted pixel markings are made on the bottom of the Quad further away from the Particles (H row)
Reproducible with: 2020.3.31f1, 2021.2.16f1, 2022.1.0b13
Could not test with: 2019.4.37f1 (Collections errors), 2022.2.0a8 ('RaycastCommand.RaycastCommand(Vector3, Vector3, float, int, int)' is obsolete)
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note:
The internal properties do return the barycentric coordinates, however obtaining the texture coordinates from them might be indeed tricky. We should consider exposing them in a threaded context indeed, created a jira card to track this work for a future release.