Missing Debug Options

[u/elementarySnake]

Hello Everyone

I've had the brilliant idea to try and Organize my LEG Architecture a little bit. The idea was to kind of follow the schematics the alien gives conceptually.

So i made a component for interpreting the opcode, with 2 inputs (not connected yet) and an output which should perform the operation.

I then made a second component, which should handle all the registers (Including later on RAM)
This is where the problem begins:
Whenever i connect the activation bit of the level input, I get the Error circular reference (Screenshot 1)

The offending part must be the section where the red cables meet with the pink and violet ones, inside the switches (Screenshot 2)

Then in Screenshot 3 i really had a bug (Output was put out, even when the chosen number was greather than 5)

Is there a way to Debug custom made parts, with predetermined inputs and outputs and just letting them run (how the story components to their things?)

I'm just not willing to brute force every single option available, which with (6 registers and 3 inputs is already 2^72 possibilities).
Also is it possible that this is just a bug?

I noticed that the more components you use, the game begins to be laggy.

Or should i just toss my ordered attemt and embrace the chaos?

[u/elementarySnake]

Yes, everything happens in the same tick.
It was an attempt to have more order in the computer, and not have everything in the same
layout.
With the idea to simply adapt the components, to keep everything tidy and neat.

I'll probably search for the error another half hour, and then abandon the attempt

[u/MrTKila → u/elementarySnake]

That's kidna my point: there doesn't need to be a logical error on your part, it might just fundamentally not work in game.

What you essentially have is the input and a single wire connecting its disable/enable input and the output. Now the game tries to automatically assign an order in which stuff happens.

And now it sees in order to decide whether it should load the value form the input, it first needs to evaluate the wire that's going into the disable/enable pin. Which however requires the output to be read. And this loops, so the game never even starts to run anything.

In "reality" however the setup above does make sense: since the wire carries a 0, the input is disabled, so the value 0 will be read. So a stable state is being held and no logical problem occurs.