Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f3
Issue ID
853931
Regression
No
Texture2D.GetPixel ignores Tiling and returns a color as if the texture had default Tiling
The project has a Sphere that casts a ray at the textures and calls Texture2D.GetPixel at collision point, but when its cast at a texture with non-default Tiling it ignores the Tiling and returns a wrong value.
To reproduce:
1. Open the attached project
2. Open console window
3. Enter play mode
4. Move the "Raycaster Sphere" game object over the texture with default tiling
5. Notice the messages in the consoles as Texture2D.GetPixel returns the correct color
6. Move the "Raycaster Sphere" game object over another texture that has non-default Tiling
7. Notice that this time messages in the console report the wrong color
Reproduced on: 5.6.0a3, 5.5.0f1, 5.5.0b11, 5.4.3f1. 5.3.6p7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
- Shadows created by real-time Spotlights are rendered at a very low resolution on terrain when HDRPAsset Lit Shader Mode is set to Forward or Both
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
Add comment