Search Issue Tracker
Fixed in 2018.2.19f1
Fixed in 2017.4.X, 2018.2.X
Votes
0
Found in
2018.2.0f2
Issue ID
1065218
Regression
No
[Graphics/Physics] RaycastHit.texCoord is very slow due to Mesh::ExtractTriangle being suboptimal
To reproduce:
1. Open the project and Enter Play Mode
2. Select the ParticleEmitter object, and change the setting "useCustomTexCoordImpl"
3. Observe in the profiler that the custom implementation is much faster than using the API
Actual: RaycastHit.textureCoord is very slow. Custom implementation is much faster than using the API.
Reproduced: 2018.3.0a6, 2018.2.0f2
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
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
Resolution Note (fix version 2018.2.19f1):
Fixed in: 2017.4.17f1, 2018.2.19f1, 2018.3.0a10