Factorio Forums

I Had roboport's set to a large construction/logistic area (4000 each) via a base edit to lay down a large blueprint (~400k entitites). laying the existing blueprint worked fine (if slow), but trying to create a new blueprint of ~8000 entities crashed the game, as shown below in a screenshot.

removing the custom roboport settings fixed the error.

Well 400k entities is really a lot, I don't have idea what could happen with the lua. The crash itself might be related to something we fixed in 0.12.20, so please update to 0.12.21 before reporting it again.

repeated the crash on create blueprint with 12.21: the offending lua script piece appears to be a custom roboport I made for personal use with a large logistics_radius:

CmdrKeen wrote:repeated the crash on create blueprint with 12.21:

the offending lua script piece appears to be a custom roboport I made for personal use with a large logistics_radius:

Code: Select all

    -- per one charge slot
    charging_energy = "200kW",
    logistics_radius = 4000,--The offending code
    construction_radius = 50,
    charge_approach_distance = 5,
    robot_slots_count = 7,

Could you upload your save file and mods (if any)? I'd like to see if I can reproduce this on my computer.

Here's the save and the mods used. since data/base was edited for this base, the edited files are in another zip.

the save point is below the structure that I tried to copy and caused the crash.

the data/base overwrites should be all you need to create this crash.

I looked at the crash and from what I can see it's eating all the video memory and dyeing. Because you've set the roboport radius to 4000 it's trying to render the selection data for every entity within 4000~ tiles of your player * count of roboports in the blueprint (77~?) * the number of roboports and entities you have in the world. All that is *way* more than a standard video card can support and even mine with 4 GB of video memory capped out and died.

So, this stays in the "won't fix" - but at least you know why it happens now

yea- figured it'd stay in the won't fix category. It might be worth it to have a limit to the value that can be put there- like the AI search radius limit of 100 units.

Yes, we should limit the value to something reasonable.