#[0.0.7] Fluid catcher cannot transfer fluid to fluid launcher when the former is on a platform edge
22 messages ยท Page 1 of 1 (latest)
Expected behavior: Fluid catcher should work the same regardless if they are a platform input or just a regular catcher
I have also run into this issue.
On the left is a Fluid Launcher that is not pulling fluid from the fluid catcher it's attached to, On the right is a connected launcher/catcher pair that is connecting correctly.
just ran into this issue as well
[0.0.7] Can confirm I'm having the same issue and it unfortunately is ruining my 1x2 painter blueprint ๐ My work around was to use a pipe like the OP Example.
same issue, came here to report this. please fix
+1, this 100% happens, easy to replicate, differs to Belt Launchers and inconsistent with it's own Fluid Launchers (i.e you can place two launchers back to back just fine - but not a platform launcher and a fluid launcher)
Also to note: A Fluid Catcher in to a Platform Launcher works fine too.
๐ Your bug report has been verified and is now in the triage phase. We're working to reproduce and fix it.
๐ The bug you reported has been fixed and is currently in the final testing phase before being released in the next update! Thank you for helping us improve our game.
๐ Your bug report has been verified and is now in the triage phase. We're working to reproduce and fix it.
๐ Your bug report is currently in progress. It's being addressed and worked on.
๐ The bug you reported has been fixed and is currently in the final testing phase before being released in the next update! Thank you for helping us improve our game.
Notably, it does work if the fluids are coming off of a fluid unloader, but not a space pipe.
yea that's a problem I'm facing rn. works off of an extractor but not a belt
Hey there,
the upcoming 0.0.8 update provides a fix for this issue.
I'm on the 0.0.8 beta and still found the same issue - is this fixed only in the release version of 0.0.8
small chance nicko thought this was about the space belt bug that got fixed, this is something else
I can confirm the bug is fixed internally. There may be a mismatch with the tag/update. I do not believe this is on the public beta but I think we do want to include it in the 0.0.8 release. ๐