Search Issue Tracker
By Design
Votes
0
Found in
5.2.0b4
Issue ID
715688
Regression
Yes
The brush to paint terrain does not correspond with the mouse position
To reproduce:
1. Open attached project
2. Open Untitled scene
3. Select terrain
4. Select Paint details
5. Try to paint cubes
Expected result: Mouse position correctly corresponds with brush position
Actual result: They don't
Screencast http://screencast.com/t/Cz9ziPAm5kVt
By Design because:
In the problematic scene, the Terrain component is using TerrainData1 while the TerrainCollider component is using TerrainData (you can inspect the terrain data reference on TerrainCollider easily, but you need to switch your inspector panel to Debug or Debug-Internal to see the terrain data object on Terrain component).
Since at runtime some projects switch terrainData of the collider differently to achieve some gameplay mechanism, it is also not viable to force TerrainCollider always use the same terrainData of Terrain component.
Therefore in this case I'd recommend just assign TerrainData1 to TerrainCollider and reopen the scene. And no further warning/fixes will be done.
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