Search Issue Tracker
By Design
Votes
0
Found in
5.3.0f4
Issue ID
766010
Regression
Yes
[iOS] RaycastHit.textureCoord returns Vector2.zero on iOS
Steps to reproduce:
1. Open attached project (link in edit)
2. Build 'TestScene' for iOS
3. Build and run the Xcode project to a device
4. Click anywhere on the plane,
5. Observe debug log where each time you click on a plane, RaycastHit.textureCoord values are returned at the clicking point
Expected behaviour: Vector2 values anywhere between 0 and 1 should be returned
Actual behaviour: Doesn't matter where you click, Vector2.zero is always returned
Doesn't reproduce on Editor/Standalone/Android.
Does not reproduce with 5.1.4f1
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
Add comment