mapeditor/tiled

Do you want to work on this issue?

You can request for a bounty in order to promote it!

地图卡顿 "map lag" #3656

AFoolLove posted onGitHub

我有一张大小为256*256的地图,从1.10开始,缩放的越小,使用鼠标中键拖动地图查看时,它就越卡顿。 我尝试回退到1.9.2,1.9.2不会出现这个问题

To Reproduce 创建一张大小为256*256的地图,使用任意图块进行填充 Ctrl+滚轮进行缩小 鼠标中键按住进行拖动地图

Specifications:

  • OS: Windows 10
  • Tiled Version: 1.10, 1.10.1

Google Translate:

I have a map with a size of 256*256, and since 1.10, the smaller I zoom, the more it freezes when I use the middle mouse button to drag the map to view it. I try to fall back to 1.9.2, 1.9.2 does not have this problem

To Reproduce Create a map with a size of 256*256 and fill it with any tiles Ctrl+wheel to zoom out Hold down the middle mouse button to drag the map


I can reproduce this. Large maps with a lot of tiles seem to have more hitching/lag when panning zoomed out. This affects both MMB drag, and space+drag.

The main difference between 1.9.2 and 1.10 is the switch to Qt6, so perhaps it's something to do with that.

posted by eishiya about 2 years ago

The main difference between 1.9.2 and 1.10 is the switch to Qt6, so perhaps it's something to do with that.

In that case, it would be interesting to know whether the problem is also reproducible with the 32-bit Windows builds, which are still using Qt 5.15.2. They are the "Windows 7-8" builds at https://github.com/mapeditor/tiled/releases/tag/v1.10.1.

posted by bjorn about 2 years ago

Windows 7, Tiled 1.10.0 here. I reproduced the steps : create a 256x256 map, fill it with the bucket tool with one tile, zoom out with ctrl-wheel to 1%, and I can drag the map with the middle button without any freeze or slow.. except small ones (and high cpu usage) when I drag it outside of the viewport (I mean, when part of it is "hidden" behind other parts of the app like the toolbar on the top of the screen, or the properties panel on the left) : small freezes. I tried with a 1024x1024 window, same result except longer freezes when part of the map is out of sight (1-2s). In both cases, if the map stays fully visible, no noticeable freeze / cpu usage peak.

posted by firstmiddlelast about 2 years ago

In both cases, if the map stays fully visible, no noticeable freeze / cpu usage peak.

This is normal because in this case the visible map is simply moved on the screen, instead of being re-drawn. This is an optimization, which is not possible when moving the camera makes a previously invisible part of the map visible.

But in that regard, nothing should have changed between 1.9 and 1.10.

posted by bjorn about 2 years ago

Fund this Issue

$0.00
Funded
Only logged in users can fund an issue

Pull requests