The flee behaviour is meant mostly as a last option when there's nothing they can do – like when they're being attacked by a turret on an unreachable island. I suppose it makes some sense for suddenly-armed landmines as well, but I agree that they should first look for an alternative target. So fixe...

Thanks for the report. Biters are actually not supposed to chase you across the entire map for the reasons you mentioned. I changed it so that if the player is far enough away, they'll path toward the point where the fire originated – this should be reasonably close to where they took damage, and it...

Thanks, fixed in 1.1.50.

Thanks, it will show the progress bar in 1.1.49.

Thanks, fixed in 1.1.49.

The comment is wrong. Maybe it was right at one point and then things changed internally, I don't know. In any case, the actual behaviour is that every fwd2bwd'th step is a backward step. So the lowest value that makes sense is 2, which means that every 2nd step is a backward one, so it's symmetric....

Well X.org has no business freezing no matter what Factorio – or any other program – does. I'd blame the AMD driver, especially since Googling “linux amd freeze” returns a bunch of results describing an issue similar to yours.

Does dmesg or journalctl contain anything interesting?

It's because Companion Drones contains a spider leg definition that has scale set to 0, which then causes a division by zero in the game. Fixed for 1.1.44, thanks for the logs!

This is correct behaviour. Most of the biters on map are disabled to save resources, which can look quite stupid if you look closely but that's how it works.

I can't reproduce this on Linux either. It's possible that the CPU spike lags the whole system and the mouse event the game receives is generated from the new location of the mouse.

JohnTheCF wrote: ↑

Wed Sep 22, 2021 12:59 pm

Is "ban recommendation" automatic ban or it just prompts admins whether to ban or let the player connect?

If the feature is enabled on the server, the server will automatically ban any user our server recommends for a ban when they try to join.

So there must be some extra element that made it not work, and it's yet unclear what that element is. I guess that the issue here may be the placeholder of a path with is interpreted not as it should... Well it's interpreted correctly for other people, yet on your computer it isn't. So the question...

Well no, if you just extract the archive and run the game, it should work: [lily] /tmp % tar xf factorio_alpha_x64_1.1.39.tar.xz [lily] /tmp % cd factorio [lily] /tmp/factorio % ./bin/x64/factorio 0.000 2021-09-10 16:29:39; Factorio 1.1.39 (build 58937, linux64, full) … So there must be some extra e...

It is permanently fixed, you just managed to break something somehow and didn't tell us what you broke or how.

I don't honestly know, I have no experience with prime-run, sorry.

I would try the standalone version of Factorio to see if Steam somehow interferes – Steam is still 32-bit and Factorio is 64, so that could potentially cause issues.

0.679 Error MessageDialog.cpp:211: Unable to show message dialog. SDL Error: [No message system available] I think this error is quite telling. It seems that Factorio can't talk to the rest of the windowing system to even display an error message box. When you say you used Manjaro before, does that...

Thanks, fixed in 1.1.38.

Thanks, should be fixed in 1.1.36.

Unfortunately, for now the game requires glibc and we have no plans to provide an additional build. Switching from glibc to musl may be something to consider in the future, but absolutely no promises.

Baughn wrote: ↑

Wed Mar 24, 2021 8:48 pm

If this is the changelog for .29, what's the one for .30?

We, uh… released .29 without any of the fixes in it. So these are the changes in .30. .29 was the same as .28, except with a different version number.