Would this mean reverting the current thruster behaviour too? I don’t really have any strong opinions on this topic, but I’ll miss how easy it is to run thrusters at 10% consistently. (Due to them not sucking in fluid up to 100%)


Thrusters are an interesting case, because they already have a ...

I have been thinking about this for a long time, and the solution I am leaning towards is to re-introduce isolated buffers for passthrough entities as it was in 2.0, but setting the volume of the segment portion of such an entity to zero. This solves the double-fluids and hidden-buffers issues ...

Thanks for the report, but this is not a bug. The "pipeline" only includes the pipes, not the pumps.

No problem. Indeed, the bookmarks are a mod portal feature only, so they only appear on the portal-related tabs.

I am unable to reproduce. I launched the standalone 2.1.11 space age build, logged in, and I can see the bookmark button just fine.

Thanks for the report, this has been fixed for 2.1.12.

Side note: In 2.1 regular copy/paste with large strings should work fine on X11.

This (and several other IPv6 issues) are happening because our networking stack incorrectly tries to route all v4 traffic through a v4 socket and all v6 traffic through a v6 socket, instead of routing v4 through the v6 socket when v6 is in use.

It's on my list to fix, but it's lower priority than ...

This is working as intended - the flush pipeline button only flushes the pipeline, which is the set of connected pipes. The pumps are not members of the pipeline.

Moving to feature requests.

For what it's worth, I tentatively plan to add fluid contents and a flush button to the pump GUI, since I ...

This appears to have been the same root cause as 134235.

Fixed for 2.1.12.

AFAIK most simulations are made with 1080p 16:9 screens in mind because this is what the vast majority of players play on.

I am afraid that it does not fix the plan where the far most consumer may never receive fluid. I would prefer these 3 cases to work the same, like they did in 2.0, I think it was easier to figure out for new and casual player. The 2.1 change may make the EM Plant not an easy replaceament for ...

Thanks for the log. This might be because you're running plasma 6 on X11, which unfortunately I cannot easily test. I need to figure out a better system for testing various desktop environments and distros before I can look at this. For now, just copy/paste or drag the text.

For 2.1.11 I have changed passthrough assembling machines (EM plants) to consider the whole fluid segment as available fluid for crafting. This will serve well enough until I can come up with a more permanent solution.

Ah, SDL is logging to stdout/stderr instead of the log file, so you will need to run it from the terminal in order to get the sdl event log output.

What I am looking for is to check whether or not it is receiving SDL drag-and-drop events.

Could you please test it with SDL_EVENT_LOGGING=1 and post that log, as well as test X11 vs. Wayland? I suspect this is an SDL bug.

Wild shot in the dark: are you using xwayland-satellite? If you are, and the game is running on X11, then drag-and-drop won't work.

non-sucking machines could simply be treated as a pipeline segment with an internal buffer size large enough to hold at least one (or even more) craft's worth of fluid. This would solve the issue of lacking a crafting buffer while keeping the pass-through connection fully operational.The only ...

Your log appears to be from Windows, so this isn't a linux-specific issue.

This was completely intentional and I thought it was a neat trade-off, but I have seen nothing but negative reactions to this, so I will look into solutions.

I should note, however, that even if I change EM plants to suck actively like directional connections, they won't be able to self-balance ...

We have updated the experimental branch on steam to use Steam Linux Runtime 4.0, which ships with a newer glibc. Please check if this fixes the problem for you. We will keep looking into ways to lower the glibc requirement for the standalone version.

I wasn't able to work on it because I didn't have an IPv6 address in my apartment (and my Ubiquiti router didn't support v6 over Wireguard for some insane reason), but I just moved two weeks ago and my new ISP has full v6 support, so I will be able to work on this once my other tasks are done.