Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.0a2
2019.1.4f1
Issue ID
1159544
Regression
Yes
Unity Player crashes when accessing Physics.Raycast.hit.textureCoord
How to reproduce:
1. Open the "case1159544_repro" project
2. Build and Run it
Expected result: Unity Player does not crash
Actual result: Unity Player crashes
Reproducible with 2019.1.0a2, 2019.1.6f1
Not reproducible with 2018.4.2f1, 2019.2.0b5, 2019.3.0a5
Note1: Only reproduces in the player
Note2: I'm not sure if it's not reproducible in 2018.4. It's possible that during the version downgrade process the project is somehow corrupted because I could not reproduce the issue on 2019.1.0a5 when downgrading from 2019.1.0a11, but then I was able to reproduce the issue on 2019.1.0a5 when downgrading from 2019.1.0a9. The earliest version that I could reliably reproduce on is 2019.1.0a2.
-
Resolution Note:
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #1006742