setup: placing four chemlabs set to lubricant next to each other in oil set up.
powered labs and supplied heavy oil to labs. attempting to hook up pipes results in auto-clamp thinking there is a fluid-mismatch. (nearby pipe has lubricant, but new pipe placement on next chem lab in the setup doesn't connect.... so you have to disable autoclamp in order to add machines to a pipe network.

Sounds like a feature and not a bug. Got a screenshot or snippet?

essentially, autoclamp prevents similar-fluid pipes from connecting to a chem lab that is outputting the same fluid.

if that is what it is supposed to do, sorry i mis-read the description

i understand it is supposed to prevent different fluids from connecting and mixing, but if the chem lab is outputting the same fluid as is in the pipe, it will still sometimes not connect properly, placing a pipe at a corner where a lab and a pipe meet connects the new pipe to the existing line, filling it with fluid, but won't connect to the lab (that is ALSO trying to output that same fluid). if however you first connect a single pipe to each of the chemlabs' outputs individually, and then go about joining them, they'll connect. but if a fluid pipe contains fluid and is one space away from a chem lab, sometimes placing a pipe won't connect the lab to the network. (even if they're the same fluid)

note that since the feature can be toggled, it's really a minor/non-issue, but i wasn't sure if it was intended to function this way or if it's a consequence of how lua/factorio works or is a bug?

Can you screenshot what you mean? I might be able to explain it better. Use snipping tool to cut.out the area that's doing it and upload to imgur or something.

Can you add me on discord? TheStaplergun 2.0#6920

gif of action: https://gfycat.com/WateryAdolescentBeauceron

Oh. I see.thats very strange I will look into this behavior.

After looking at it, I've realized this is due to it referencing fluidbox at index point 1, which likely isn't that output port, therefore making it think it doesn't match. I will look into the possibility of figuring out which port it's connecting to, but this may actually be unlikely.

This is fixed.