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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1006742