[0.11.17] [Rseding91] Map editor locks up at large scales

This subforum contains all the issues which we already resolved.
total_nonsense
Manual Inserter
Manual Inserter
Posts: 1
Joined: Fri Mar 06, 2015 7:31 pm
Contact:

[0.11.17] [Rseding91] Map editor locks up at large scales

Post by total_nonsense »

This problem occurs reproducibly on OS X 10.9.

1. Create new scenario - generator parameters don't mater.
2. Zoom out as far as it goes. Choose tile brush tool, choose any water tile, set size to 600
3. Paint over a large area; it doesn't matter whether with multiple clicks or as a single long drag.
4. Try to move around with WASD keys.
5. Repeat.

The map editor will always eventually freeze after some repetitions of this. Making sure to only paint in already-generated parts of the map (e.g. not running so far off the edge that it goes into ungenerated area) doesn't help. The game doesn't beachball, but no interaction (including an attempt to quit) is recognized and the process must be force-quit. Nothing shows up in the log. CPU usage spikes, mostly in kernel_task, some in the factorio process. Changing graphics settings makes no difference. Restarting the computer doesn't help. I have no mods, and the scenario pack is disabled.

Edit: Adding hardware information:

MacBook Air 13" Mid-2013 (MacBookAir6,2)
OS X 10.9.5
1.7 GHz Intel Core i7
8GB main RAM
Intel HD Graphics 5000, 1GB VRAM
kovarex
Factorio Staff
Factorio Staff
Posts: 8298
Joined: Wed Feb 06, 2013 12:00 am
Contact:

Re: [0.11.17] Map editor locks up at large scales

Post by kovarex »

Ok, it is related to to edit of chunks that are next to not generated chunks on the left part of the screen, I was able to reproduce it once.

But as this is really very special case, and I don't want to break something now, I'm moving it to minor bugs.
kovarex
Factorio Staff
Factorio Staff
Posts: 8298
Joined: Wed Feb 06, 2013 12:00 am
Contact:

Re: [0.11.17] [Rseding91] Map editor locks up at large scales

Post by kovarex »

It is related to one bug I just fixed recently, I believe.

So it should be fixed for 0.12.5
Post Reply

Return to “Resolved Problems and Bugs”