Jump to content

is the refiner bug back or am I doing something wrong


Recommended Posts

As before when this was a problem for a time: the water in the refiner gets much too hot causing output pipes to break. Then the current refining job finishes with no liquid output, and the water temp continues rising. Only viable option winds up being to deconstruct it, and then 500 kg of steam explodes everywhere causing a big mess to clean up.

image.thumb.png.6414fabc199f1fa3cf56ed64c80b6a16.png

Since I missed this one last time it was a problem, can anyone make a recommendation on how to deal with it? I'm trying to make steel so hatches aren't a viable substitute.

1 minute ago, Grimgaw said:

Use colder liquid. You could cycle your 40C sink/toilet pH20 a few times before sending it back to sieve.

I'm sending 32C liquid. In one refining cycle the output temp goes above 100C and breaks the output pipe.

Colder still? Seems incorrect.

It's a bug where any used coolant still in the refinery when another job is completed heats up in addition to new coolant. The screenshot shows 697kg of new coolant and 490kg of used coolant. Each job uses 400kg of coolant. I would guess 100 kg of used coolant was waiting to exit the refinery when the previous job was completed. That coolant heated up again becoming superheated and broke the pipes once released.

The work around is to not use the refinery so long as any used coolant is still inside. The easiest way to do that is with an element sensor on the first exit pipe connected to the refinery through a not gate. If there is liquid in that first exit pipe segment, there is probably used coolant inside and the refinery should be disabled. If you want to use the refinery before automation becomes available, don't queue jobs and manually do one job once the used coolant has exited. A liquid reservoir is useful here to provide space for that 400kg of liquid to go, previously I used large lengths of pipe.

This bug has been around for a very, very long time. It's even in the known issue thread. You can exploit this bug to create large quantities of superheated stuff by blocking the exit. Each job adds another 400kg of coolant to the used pile and keeps heating it regardless of how much is there.

Obviously you need to use coolant that can take the heat, 56C for steel with water. But I doubt that was the problem here.

23 minutes ago, Sasza22 said:

I`m not sure if that works. Pipe sensors don`t change their state if the pipe is empty afaik.

It absolutely does work. Why would I post something if I didn't know wtf I was talking about?

because the bug you describe is not the cause of the problem so clearly your posting about something you don't know about..... steel creates more heat than iron and unless your water is below 28c before you send it to the refinery, its likely to blow out lines coming out the other end because of Steel.....

Either use a different coolant (oil/petroleum) or create a thermal check valve to make sure only 28c and below gets to the refinery

2 hours ago, Kabrute said:

because the bug you describe is not the cause of the problem so clearly your posting about something you don't know about..... steel creates more heat than iron and unless your water is below 28c before you send it to the refinery, its likely to blow out lines coming out the other end because of Steel.....

Either use a different coolant (oil/petroleum) or create a thermal check valve to make sure only 28c and below gets to the refinery

The bug I describe is very much the cause of this problem. Frankly, you don't know what the hell you're talking about. If you would mouse over the heat number on the refinery you would see the real number that the coolant is raised by. Since I'm a nice guy, I will do it for you.

20180903005905_1.thumb.jpg.32057b618f2478e792046886e71cfeb1.jpg

20180903005911_1.thumb.jpg.b8640f16b450c0ad0ab2a46096dc4616.jpg

20180903011511_1.thumb.jpg.3f041af541cd806d96f004bdab9f202f.jpg

20180903011518_1.thumb.jpg.56f6126973bd5498178c42e817a96d0f.jpg20180903011920_1.thumb.jpg.3057fabcf345b7589612cae65c2d72fb.jpg

The third pic shows a refinery with 800kg of 39.8C water coolant. After a job of steel production it now has 400kg of 39.8C new coolant and 400kg of 95.8C used coolant as shown by the fourth pic. A difference of 56C! The last pic shows a second steel production job which heats both the remaining 400kg of new 39.8C coolant and the 400kg of used 95.8C coolant for a total of 800kg of used 123.8C coolant (((39.8+56)+(95.8+56))/2). Just like I said, amazing!

agree with wachunga, excatly what i have been experienced. For steal you need some cold ice biome pwater or oil based coolant.

My setup for now is that i use crude oil as coolant and send it directly into refinery - dont matter that temp goes up to 270C... :)

then file a bug report on averaged adjusted outputs because that doesn't make any sense for your refinery to do that, I don't understand how your system is doing that because mine isn't having those problems or behaving in that way.  Please file a bug report because that behavior is not what I would call expected.

its also not the bug that was being had before.  The prior bug just kept adding the new heat to the old heat value and applying that to the outgoing coolant with no averaging

so first found 40 in, 96 out, second round 40 in, 151 out, third round 40 in, 207 out

thats why the numbers threw me off, I just figured they adjust shc of water or something and I missed that detail...(happened to pwater)

12 minutes ago, Kabrute said:

then file a bug report on averaged adjusted outputs because that doesn't make any sense for your refinery to do that, I don't understand how your system is doing that because mine isn't having those problems or behaving in that way.  Please file a bug report because that behavior is not what I would call expected.

I've counted at least 3 bug reports on this very issue unchecked for more than a month.

fresh one wont hurt.  I've posted some bugs again and again and I will keep posting them about once per update each time I encounter them fresh.  Case in point the sandyblueprint bug

I first posted about it back in may/june, new bug report on it last night because its still in the preview build.

and they might just fix it "this time around" if we keep bringing it up.

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...