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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment