But if you construct a scheme from blue books, working condition. (blue scheme save in 0.13.8)
Can you fix it?
Left hand, right drones.
why is true?
SIGNAL all in belt
SIGNAL all in belt
in 0.13.9 stopped working condition "all *> resource."
But if you construct a scheme from blue books, working condition. (blue scheme save in 0.13.8)
Can you fix it?
Left hand, right drones.
why is true?
But if you construct a scheme from blue books, working condition. (blue scheme save in 0.13.8)
Can you fix it?
Left hand, right drones.
why is true?
Re: SIGNAL all in belt
This is not a 0.13.9 bug, just a regular weird behaviour (I double-check it in 0.12.23).
This happens because "Everything > signal A" means "Everything except signal A > signal A" (otherwise this condition will be always false, because "signal A > signal A" = False).
As a result, if you have only one signal A in input then
"Everything except signal A > signal A" == "---Nothing--- > signal A", and this is always True by design.
This happens because "Everything > signal A" means "Everything except signal A > signal A" (otherwise this condition will be always false, because "signal A > signal A" = False).
As a result, if you have only one signal A in input then
"Everything except signal A > signal A" == "---Nothing--- > signal A", and this is always True by design.
Re: SIGNAL all in belt
yes, very weird indeed.
if you compare "everything" with a constant it acts strangely; for example, if you set a lamp to turn on on "everything" > 0 (constant value, not signal) and no signal is sent on circuit, lamp turns on!!!
if you compare "everything" with a constant it acts strangely; for example, if you set a lamp to turn on on "everything" > 0 (constant value, not signal) and no signal is sent on circuit, lamp turns on!!!