Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In tileset editor, attempting to paint terrain over alternative tile instead creates a new alternative tile #99764

Closed
olanti-p opened this issue Nov 27, 2024 · 1 comment · Fixed by #102640

Comments

@olanti-p
Copy link
Contributor

olanti-p commented Nov 27, 2024

Tested versions

  • Reproducible for v4.3.stable.official [77dcf97]

System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - AMD Radeon RX 6600M (Advanced Micro Devices, Inc.; 30.0.13024.5001) - AMD Ryzen 7 5800H with Radeon Graphics (16 Threads)

Issue description

Attempting to paint terrain over an alternative tile instead results with the terrain editor creating a new alternative tile. Which shouldn't happen, as the alternative tile creation is done via "Select" tab of the tileset editor.

Steps to reproduce

  1. Load attached project
  2. Open player.tscn
  3. Open TileMapLayer node
  4. Switch to tileset editing, Paint mode
  5. Select property Terrains -> Terrain Set 0 -> Dots Biome
  6. Attempt to paint this point:
    Image
  7. Be greeted with this sight:
    Image

Minimal reproduction project (MRP)

TerrainPainterBug.zip

@olanti-p
Copy link
Contributor Author

olanti-p commented Feb 9, 2025

I tracked down the issue to the "create alternative tile" button that's appended to the end of the row.

Here in this pic, it's changed up to use grey background instead of transparent.

For some reason, the button is missing the icon, is sized incorrectly and overlaps nearby squares, intercepting terrain editor input.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants