that's really cool! it's amazing how intuitive and straightforward the solutions were, especially after Rseding91 told players for years that it couldn't be done!

so the DLC announced >1.5 years ago is now announced to be entering another year+ of development? haha. trying to remain relevant or something? people certainly forgot by now. maybe this is a good way to remind them. good luck!


Yet here you are, apparently not having forgot.


oh wow! super ...

so the DLC announced >1.5 years ago is now announced to be entering another year+ of development? haha. trying to remain relevant or something? people certainly forgot by now. maybe this is a good way to remind them. good luck!

MEOWMI wrote: Sun Jul 16, 2023 10:30 pm

ptx0 wrote: Fri Jul 14, 2023 4:10 am i think multiple overhaul mods have been released since then, by smaller teams, with smaller budgets.

And with way, way less polish and balance and optimization.

but as someone said earlier, "we don't know what's being made" lol

yep, lol pretty weird. i'm not even the only one who has lost interest, came back to see whether there's any news about this expansion and i can't believe it's been TWO AND A HALF YEARS since the announcement. good stuff LMFAO i think multiple overhaul mods have been released since then, by smaller ...

well, it might be that Xwayland is never getting used, even if the wayland support is disabled.


A way to know with 100% certainty is to check in the log. If you're on xwayland, it will show two XWAYLAND displays in place of your actual displays. For example, on my machine, it looks like this ...

also if you're not wanting to use the standalone copy you could try disabling the in-game Steam Overlay for the game, which can cause issues especially on Linux with X11.

Are you 100% certain that it happens on xwayland too? I can't reproduce it through xwayland.


well, it might be that Xwayland is never getting used, even if the wayland support is disabled.

Basically, i don't set any env flags to cause the crash. but the Wayland support is supposed to be ...

there's also an already-fixed condition with Wayland where the game crashes on exit, and this could be related to that.

This log does not contain any useful informations and as such there is no well defined condition when this bug report would be considered fixed or not a bug. Since there is also https://forums.factorio.com/105527 it could be a duplicate as well. Moving to duplicates until proven otherwise.


naw ...

hm, it looks like it even affects Xwayland. That's incredibly unfortunate, and it describes why the game still closes even without the new wayland support enabled? Can't figure out why it didn't happen before.

Rseding91 wrote: Sat Mar 11, 2023 8:38 pm I'll forward this to the wayland person.

Thank you! It'll be very worthwhile once it's working fully. I get higher fps on that codepath. For anyone else hitting this issue, just try disabling instant blueprint for now, and use Raiguard's "Editor Extensions" construction bots to build.

I've done more testing. This is definitely a bug in the recently-added Wayland support.

Under Plasma, with Wayland enabled:

1.1.76 - Can paste extremely large blueprints
1.1.77 - Once the blueprint finishes pasting, the game quits with "Quitting: window closed."


Under Plasma + X11:

1.1 ...

I'm using OS defaults and running Factorio without any env vars set - no (non-default) Wayland support enabled, no memory allocator changes, no libraries being overloaded.

Just normal `./bin/x64/factorio`

I've killed everything except the display server and Factorio, which leaves me 47GB free memory before starting the game, and then pasting the same large blueprint with "instant blueprint" enabled shows:

7769.254 Info AppManagerStates.cpp:1910: Saving finished
7965.319 Info AppManagerStates.cpp ...

total used free shared buff/cache available
Mem: 60119 49092 10009 535 1017 9847
Swap: 0 0 0
2158.703 Quitting: window closed.
2160.671 Time travel logging:
354.281 Player 0 ran command: game.player.force.chart_all()
406.367 Player 0 ran command: game.player.force.chart_all()
537.992 Player 0 ...

Thanks for the report. In both cases it ran out of RAM (or so the OS told it). When the game tries to allocate but is told "no" there's nothing we can do except abort the process. Typically places that are trying to allocate are right in the middle of game logic and we can't simply continue ...

I free'd a bunch of memory before starting the game back up. I tried again to paintbucket the ocean. It worked.

Then, I tried to copy a large section of an outpost, and received:

462.421 Info AppManagerStates.cpp:1910: Saving finished
588.445 Quitting: window closed.
589.636 Time travel logging ...

There was about 3GB of memory free after the game crashed so it might have run out and not handled that very well.

I replaced an ocean with concrete using the editor and received this crash:

40921.253 Player 0 ran command: game.player.force.chart_all()
40958.728 Player 0 ran command: game.player.force.chart_all()
40987.917 Player 0 ran command: game.player.force.chart_all()
43116.001 Player 0 ran command: game ...