-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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 edition has slower framerate than usual #12391
Comments
Tried again tilemaps on latest master, noticed the same slowness. |
We have now entered release freeze for Godot 3.0 and want to focus only on release critical issues for that milestone. Therefore, we're moving this issue to the 3.1 milestone, though a fix may be made available for a 3.0.x maintenance release after it has been tested in the master branch during 3.1 development. If you consider that this issue is critical enough to warrant blocking the 3.0 release until fixed, please comment so that we can assess it more in-depth. |
I think I could confirm on 2-5 days old master (showing version rc3), as I'm on a lower-perfomance machine right now. I was able to work around it by setting a smaller quadrant size. |
@bojidar-bg that's weird, I have the slowdown even without modifying the tilemap, by just moving the cursor around. |
Ok, then I guess I confirmed something else, not this 😄 |
Godot 3.0 Windows 10 64 bits
nVidia 940M
I noticed a very slow framerate when editing tilemaps (just panning or moving the tile cursor is enough to notice).
Here is a video where I try to show it (watch til the end):
https://www.youtube.com/watch?v=trGway9DoqU
You can clearly see that the 3D editor runs smoother, and the 2D editor also runs smoother if the tilemap isn't selected. Checking "update always" improves framerate a bit (cc #11030) but in this case it isn't the only factor.
Repro:
Create a tilemap with a simple tileset and select it to bring up the editor, notice slowdown even before drawing tiles. It looks like it happens when the tile cursor moves, but I'm not sure.
The text was updated successfully, but these errors were encountered: