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
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
Add comment