godotengine / godotengine/godot
Tileset collision polygon does not appear when clicking away after drawing the polygon
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
Tested versions
- Reproduce in v4.3.stable.official [77dcf97d8]
System information
Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - AMD Radeon RX 6750 XT (Advanced Micro Devices, Inc.; 32.0.12011.1036) - 12th Gen Intel(R) Core(TM) i5-12600KF (16 Threads)
Issue description
When clicking away after drawing the collision polygon, it will not show up on the tile in the tileset. If you click the square surrounding the tile in the drawing area it will show the polygon in the tileset over that tile.
Note: Here I've been using Compatibility but this also happens in Forward+.
https://github.com/user-attachments/assets/1e9ce277-1a7b-445c-ab8b-3ef06a35eb6b
Steps to reproduce
- Create a tileset
- Add a Physics Layer
- Press the "Add polygon tool" and start drawing the polygon
- Click outside the drawing area after enclosing the polygon - Polygon is missing
- Click the gray (or whatever it's color is on your system) area surrounding the tile in the drawing area - Polygon is present
Minimal reproduction project (MRP)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached tileset_collision_polygon_bug.zip minimal reproduction project and reproduce the missing polygon after clicking outside the drawing area. Inspect the tileset editor collision-polygon workflow to identify where the polygon is committed or refreshed. Done means a completed polygon remains visible on the tile after clicking outside the drawing area in both Compatibility and Forward+ modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100