Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

The signal doesn't seem to be propagating from the latch, am I doing something wrong?

(2 edits)

I rebuilt that and the latch propagated a signal as expected

the bottom left circuit is flashing, right?

EDIT:

I re-created that machine and got the same behavior. Block detector on the welded mode sends low power signals. The latch just happens to be where it goes from 1 to 0. This is intended. You can scan the wire on the input to the latch and see it has a charge of 1

Thanks, I didn't realize the latch doesn't refresh the signal. What about situations like this (the block detector is set to any)?


I had it against a wall and used right click to move it away, then the wires coming out of the block detector became stuck. If I let a block fall in front of it it would update and the wires would be off after the block passed. Also the top wire seemed to update to off for a moment while the block fell a little bit but wasn't in front of the detector yet.

When blocks get un-frozen after you place them, the update order is pretty arbitrary so you'll get a lot of blocks that change as soon as they get updated. This is pretty low priority, but I could always blast un-freezing blocks with more updates.

Is there any situation were errors from picking up and placing a contraption will not quickly resolve itself once some blocks start moving around near it?

Not that I can remember, but I will let you know if I see anything like that

(4 edits)

Does signal drop depend on the blocks it passes through? This one seems to be dying a lot earlier than the latch one:

EDIT: Thought it was a signal drop issue since using a toggler next to the block detector did what I expected, but after messing around a bit it might be an update issue since it would work sometimes and break if I moved it. This is more annoying to work around because updating blocks near the block detector didn't help. I'm not sure what fixes it since I tried placing blocks around the ports but that didn't help either.

Here's also a different case I saw where dropping something on the block detector didn't update the signal it was outputting:


I also wasn't able to figure out how to make this one update.

EDIT2: If I drop the block sideways then one wire is activated


EDIT3: If it sees 3 adjacent ones then it's enough to cross the gap and power everything

I guess this might be some feature for detecting the number of blocks, for now I'm working around it by putting two transistors behind it

(1 edit)

Having another issue that probably has to do with update order, the on pulse at the port gets dropped (when the actuator extends after retracting) so it doesn't detect the negative edge. It's connected for the delay of two transistors so I feel like it should go through.


(1 edit)

another one, this one spontaneously stops working when it passes over the gaps in the ceiling (set to detect machining)