Subscribe to download
CarpetReleaseTM Cell

Understandable thanks. I was thinking i could connect unlimited hardpoint amount to passthrough.

The use of the f(x) logic blocks is to delay the signal 12 ticks (0.2 milliseconds) to allow the bombs to release one at a time. Since there's no default delay block in the microcontroller editor, I had to get creative.

The hard-point weapon type node is how the controller can know if the hard-point is loaded or not. This is because an empty hard-point will always output 0, no matter the weapon type it had before. Therefore the controllers can know to skip empty hard-points and not have to go through the cycle for the whole bay again if you stop bombing half way through.

So the goal of this system was to make it as compact as possible. For that, i decided to make each controller work on two hard-points instead of one, which cuts down on logic and allows them to only take up 1 block of space above the bomb bay, even if that bay is as densely packed as in the video.

It works just like the pass-through on a rocket launcher block or a flare block. You put one of these controllers for each two hard-points in your bomb bay, connect the numerical nodes to the weapon type node on each hard-point, then connect the launch nodes to the hard-points, and finally connect the pass-through onto the next microcontroller, forming a chain.

Dunno why but it doesnt work for me. It drops all bombs at once.
Why do you have so many f(x) logics,is there any reason?
And for what reason two hardpoint ordinances from two hardpoints should be connected? They both output same value.

i see napalm in the future with this thing and will help kill all

You already know what im going to do with this...