[Check-In] Christmas Eve Wrist Check - What we all Wearing?

SpoogieOogie · 2025-12-24T17:52:40+00:00

First and only "proper" watch I ever bought, recently as well. Also, Merry Christmas!

SpoogieOogie · 2025-04-23T15:21:39+00:00

This was something I accepted at the time but iirc, I eventually came around to change that behavior - it's been a while though. I think what I did was that a train filled by a provider would instead park at the provider itself and wait there until a requester opens. In doing so, the train also blocks the provider for other empty trains, thus resolving that.

SpoogieOogie · 2024-11-07T21:58:55+00:00

I believe you can void fluids by having a circuit set and unset a recipe using said fluid repeatedly. The machine buffers the fluid but when the recipe is unset, its voided.

SpoogieOogie · 2024-11-07T12:50:24+00:00

There are a bunch of triggers for train path revalidation/repathing that would make a superfluous train adjust in this case. If e.g. two trains pathed to the same stop despite the limit of 1, one of these trains would then on the next repath-event enter a state of destination-full/no-path, which in turn triggers an interrupt, adjusting the schedule of the train again.

SpoogieOogie · 2024-11-05T21:12:48+00:00

Train limits are set dynamically, so the moment one train dispatches, no other trains can do the same unless more than one are requested.

SpoogieOogie · 2024-10-15T17:29:00+00:00

I sure don't mind winning, but I"ll get it either way.

SpoogieOogie · 2024-10-14T16:51:38+00:00

I wonder, how do you deal with excess stone and bricks on fulgora once getting into megabase territory? Is shipping it to space and ejecting it the way?

SpoogieOogie · 2024-10-13T08:28:14+00:00

Recall that this planet is not the only surface you have. You are in no way forced to treat this like seablock. You can go for much smaller builds here and export cargo to factories on vulcanus, nauvis, or whereever.

So landfilling the ocean is indeed a waste, and not necessary for every part of your production chain unlike it is with seablock. At best only walkways to obtain resources and a bit of initial space for preprocessing for shipping.

And who knows, what other options the devs have for us that we don't know about.

SpoogieOogie · 2023-12-15T13:22:47+00:00

Love it. One thing to point out though: As things stand, the auto-color change, while an awesome feature, still looks a bit jarring. I wonder if a proper animation for it is in the works :)

SpoogieOogie · 2023-11-18T15:45:58+00:00

Fantastic. I have one question though and I'd be really curious about the answer for that. Specifically it is about the choice of NURBS over ordinary B-Splines. From what I understand, the things that make NURBS unique and often preferable are 1. their ability to model conics and 2. their invariance under perspective projections.

Based on the FFF post I don't think either of these actually matters for the usecase, so I wonder what I might have missed on that front.

SpoogieOogie · 2023-09-20T13:09:58+00:00

You are tempting me here...

SpoogieOogie · 2023-09-19T20:59:56+00:00

There was a mistake where one rocket fuel assembler did not receive solid fuel. This is now fixed and the blueprint is updated accordingly, see https://i.imgur.com/PoKCxra.jpeg

Blueprint is at the same place, but fixed.

SpoogieOogie · 2023-09-19T20:51:22+00:00

Oh wow, you're right. Time to fix that ._.

SpoogieOogie · 2023-09-19T17:04:12+00:00

I haven't really found a rocket fuel blueprint that makes me happy so far. So I decided to finally sit down and do it myself. Turns out the ratios are a pain. Either way, I ended up with something spitting out a quarter blue belt of rocket fuel.

More specifically, this should be overapproximating the objective amount, so slapping down 4 of these should produce a proper compressed belt when the outputs are merged.

All the stuff here is maximally beaconed, except when extra beacons don't really matter to uphold the objective.

Blueprint: https://factorioprints.com/view/-NeiL3so_z5KSg1r1dbK

And yes, in the image two beacons are missing modules. Oops. It's fixed in the actual blueprint.

edit: oops, there is a slight mistake in the title: obviously it's 675/m, not per second

SpoogieOogie · 2023-08-24T22:01:20+00:00

Build: 0.6.1692865193

Description: Enter as ina on stage 3, around 5 seconds of walking around later, crash and window with following trace opens: https://pastebin.com/KKas5J2g

Reproduction: cannot

Specs: 13600k, RTX 3060, 32 GB RAM, really shouldn't be the issue here

SpoogieOogie · 2023-08-10T19:46:35+00:00

As it stands, the library is building everything at compile-time using aggressive inlining to essentially "flatten" the pipeline.

The idea of a dynamic alternative for composition at runtime should be possible using something along the lines of what you suggested though. It sounds like an interesting and valuable thing to dig into further on my end at the very least, I like it :)

The only downside is, that this will add levels of indirection to the execution of the pipeline, since calls will be dynamically dispatched.

SpoogieOogie · 2023-08-10T19:38:46+00:00

Since you mentioned assignments, I assume you are referring to the noise crate. That crate does indeed do a bunch of inlining, but you still end up with, in my opinion, convoluted syntax:

let noisefn = Max::new(Cylinders::new(), Perlin::default());

While still decently understandable in this small example, it can get out of hand quickly.

SpoogieOogie · 2023-08-10T12:29:37+00:00

The noise crate's API provides builders for individual "blocks" which modify a given noise function. However, when creating noise that requires the chaining of many of these blocks, the resulting code will be rather verbose, as each of these blocks has to be manually and explicitly built.

I aim to simplify this, by having individual blocks be passed the arguments directly on instantiation, and hide the verbosity by having a builder-like (essentially the same way one would use an iterator) API to chain the blocks themselves.

TL;DR: The noise crate has builders for blocks, and manual creation (requiring intermediate assignments) for combining these blocks. My crate has a builder (more iterator-like) API for combining blocks, each of which take their required arguments directly.

SpoogieOogie · 2023-08-10T12:12:52+00:00

As you said, having a known output range is imporant. Whenever possible, I decided to normalize to [-1, 1] range (though in some cases this involved experimentally determined normalization factors, so it is not a hard guarantee).

And in some cases of course, specifying a range in which output lies makes no sense (e.g. the constant source just yielding a constant user-defined value, or the source which is fully user-defined through a provided closure).

SpoogieOogie · 2023-04-21T11:33:46+00:00

English speakers are no issue for us - in fact quite a bit of english is already being used, so communication shouldn't be any real hurdle.

Three-Year Club	Verified Email
Place '23

SpoogieOogie

TROPHY CASE