I have heard they are from "failed paths" but can we get some more discussion on this matter? In late game where massive cleansing must occur, the biters seem to just give up. What are we supposed to do besides just wait for them to despawn? I want them to get as angry as absolutely possib...

Unfortunately I don't have any additional information on this. I can't recall if it was "left blank" or if it was set to 100 or whatever it was. I was thinking if someone with source could check to see if that value gets set to some default internally, that could be useful to check but oth...

Somehow these were set to 100. I set it back to 8000 and 1000 per data/base/prototypes/map_settings.lua and now it is working fairly well /c game.map_settings.path_finder.max_work_done_per_tick=8000 /c game.map_settings.path_finder.max_steps_worked_per_tick=1000 I will follow up with additional obse...

I want to chronicle some observations: Shortly after loading the map, the fringe is apparently not covering the entire map unknown.png After removing a few stuck biters in the editor, after a few moments the fringe covers the map Screenshot from 2019-10-29 09-49-27.png I found this group that seems ...

Should the pathfinder cache look like this? Something seems a bit odd here with the display

Thank you Loewchen. Here is the file: https://we.tl/t-UlE55rWl4l

The forum will not let me upload the map. Where should I place it?

The pathfinder just gave up at some point. I'm not sure what's going on here. Map is linked (https://we.tl/t-UlE55rWl4l) with plenty of unit groups that get artilleried and just stand there and do nothing.

Similar crash doing similar things, but different assertion: Error TrainSignalLogic.cpp:110: this->reservedSignalsClose[0].signal == signal was not true Raw stacktrace: 0x9b4495, 0x9b4c18, 0x9d0fbf, 0xaa18f8, 0xee661f, 0xee71eb, 0x9fb992, 0x9fbbaf, 0xa04370, 0xee8eec, 0xee923a, 0xee9688, 0xeeec2a, 0...

I should have included that's what i was doing: deconning chunks of rails with at least a few rails and each signal type in the selection. I think the stack trace hints at that but maybe not.

You do not want my save file. Trust me. Here's a stack trace though. Factorio crashed. Generating symbolized stacktrace, please wait ... Raw stacktrace: 0xaef60b, 0xca67fd, 0x9b4c18, 0x9d0fbf, 0xc20191, 0xc20b67, 0xed4228, 0xed475f, 0xed4d72, 0xed4ecc, 0x9f0f60, 0xaab4f3, 0xed8e30, 0xc74eb4, 0x80025...

When tons of artillery is fired, unit groups increase into the thousands. The biters sit there until they can have a turn with the pathfinder to attack. The number of active entities grows, UPS drops, and in MP eventually the FPS drops to unplayable on mediocre hardware. Can the biters waiting to ha...

When the map is huge, and my FPS drops, when I try to scroll with WASD in map-view, I get lost with how fast the single tick scroll goes. Can we have something like shift to lessen the map scroll velocity for WASD keys? I'm trying to be concise without being too vague so please do not hesitate to as...

I may be wrong, but I think GPUs are pretty good at displaying the same thing many times, so though it seems like there may be overhead with this, I think the GPU deals with it without much consequence.

I just want to attemp to correct a typo here for the copypasta type like myself: /c game.player.force.max_successful_attempts_per_tick_per_construction_queue = 20 game.player.force.max_failed_attempts_per_tick_per_construction_queue = 20 As always, thanks Klonan for sharing this. And all the other W...

Another vote for broken updater and 404 on website (linux)

I usually see the value numbers in the thousands, tens of thousands sometimes, but i feel like values in the 100s of thousands are not very common. Low hanging fruit for cleaning up. The biters on that path are gone and the number is falling.

I see, Thank you for the clarification. In any case, it seems for game performance's sake, a large number would suggest it be good to go destroy the biters which are keeping that path alive.

After briefly skimming the GreedyDual concept, is that to say the larger the number for the path, the more expensive it would be to reevaluate it? So it's not that it inherently costs more to keep the path around - it would just be more of a hit to have to reevaluate it?

What does the number mean to the right of the path cache coordinate? I see the matching color at the surface coordinate shown in the path cache, but the numbers are huge on some of those. Way too long to simply be the length of the path, unless it's getting in a loop somewhere and backtracking on it...