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
- Mesh Renderer Component uses default editor when applying custom editor
- Editing a Template is not disabled when the Template signature is in progress but if the Template is edited the Template signature fails
- Changing Signing organization on a Template still shows the same organization in the Hub
- [Android] Navigation bar does not go away when tapping on the screen to close the keyboard
- "InvalidOperationException" is thrown when clicking "Ctrl+Z" after opening Gradient Editor
Resolution Note (fix version 2018.2.19f1):
Fixed in: 2017.4.17f1, 2018.2.19f1, 2018.3.0a10