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

tileMap ERROR: No cached rect #89144

Closed
jonSP12 opened this issue Mar 4, 2024 · 5 comments
Closed

tileMap ERROR: No cached rect #89144

jonSP12 opened this issue Mar 4, 2024 · 5 comments
Labels

Comments

@jonSP12
Copy link

jonSP12 commented Mar 4, 2024

Tested versions

Godot_v4.3-dev4

System information

windows 10 vulkan foward+

Issue description

no cache rect for tile coords:
doesnt crash but error will pile up
bug

Steps to reproduce

  • in scene lvl_b1
  • select tileMap node
  • deselect ( highlight selected TileMap Layer )
  • frist tileMap sheet ex: ( autoTileTest.png )
  • select the frist 3 by 3 square group
  • paint / rotate(X) / paint / rotate(X) / paint.... 3x
  • press select tool icon select all painted tiles
  • ctrl + C / then leter D
  • paint / rotate(X) / paint rotate(X) / paint... 3x
  • press select tool icon select all painted tiles / delete

Minimal reproduction project (MRP)

tileCrash3.zip

@AThousandShips
Copy link
Member

You already made a report for this issue, please update it instead of making a duplicate issue

@AThousandShips AThousandShips closed this as not planned Won't fix, can't repro, duplicate, stale Mar 4, 2024
@jonSP12
Copy link
Author

jonSP12 commented Mar 4, 2024

You already made a report for this issue, please update it instead of making a duplicate issue

Godot_v4.3-dev4

@AThousandShips
Copy link
Member

AThousandShips commented Mar 4, 2024

That doesn't matter, don't make a new issue for each version please, especially when it's just a new dev version, even if it was on 4.2 instead of 4.3 it shouldn't be a separate report

@jonSP12
Copy link
Author

jonSP12 commented Mar 4, 2024

That doesn't matter, don't make a new issue for each version please, especially when it's just a new dev version, even if it was on 4.2 instead of 4.3 it shouldn't be a separate report

i though the other one was closed

@AThousandShips
Copy link
Member

Even if it had been the information should be put there first :)

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

No branches or pull requests

2 participants