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

tileset painting z-index issues in editor #4070

Closed
hyperglow opened this issue Mar 15, 2016 · 4 comments · Fixed by #4088
Closed

tileset painting z-index issues in editor #4070

hyperglow opened this issue Mar 15, 2016 · 4 comments · Fixed by #4088

Comments

@hyperglow
Copy link
Contributor

Ubuntu Linux 64bit

Tiles don't get painted in correct order in the editor. This happend the first time after I painted several tiles without problems. Maybe its the tilesize? The running game shows the correct tile z-depth... Check the screenshot.

Steps to reproduce:
auswahl_008

Link to minimal example project (optional but very welcome):

@bojidar-bg
Copy link
Contributor

👍 I can reproduce, sometimes newly painted regions of the tilemap would cover existing graphics with a higher z-index and position in the tree.

Edit: Actually, I'm talking of a bit different issue, but I guess the two are connected.

@hyperglow
Copy link
Contributor Author

I tried to recreate in a new scene and i got the same problem.
zip of the project is here:
iso_test.zip

@bojidar-bg
Copy link
Contributor

Looks like it's an issue with quadrants repainting 😄


Edit, I'll put other findings here aswell

Edit 2 - already fixed, all notes are now commented out

@bojidar-bg
Copy link
Contributor

@hyperglow ~ Playing around with your demo, if you do

extends TileMap

func _ready():
    set_process_input(true)

func _input(event):
    if event.type == InputEvent.MOUSE_BUTTON:
        set_cell(30, 0, -1)

And click on the screen in-game the same issue occurs.

@akien-mga ~ -topic:editor +topic:core

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

Successfully merging a pull request may close this issue.

4 participants