This combinator has become stuck and is no longer processing:
As you can see it's input is connected to it's output so that it feeds back onto itself, and it is also connected to a constant combinator outputting 1, and so it should count upwards. However, the display remains static, always showing an input of 147 and an output of 146.
I wish I could say how it got into this state but I have no idea. I note that if I build a new power pole and use a green wire to connect the input of the combinator to the new pole, the combinator begins working as expected, even though the new wire connects it to nothing.
Whole game save attached because I have no idea how to reproduce this, but the state does persist when I reload the save so maybe something can be learned from the save file.
[boskid][2.0.12] Decider combinator stopped working
[boskid][2.0.12] Decider combinator stopped working
- Attachments
-
- glitched_combinator_2.zip
- (16.57 MiB) Downloaded 2 times
Re: [boskid][2.0.12] a decider combinator has stopped working
Thanks for the report. I managed to find one case where a decider combinator could get stuck and it was related to marking it to deconstruct and cancelling the deconstruction. This case is now fixed for 2.0.14. I cannot confirm this is the exact way you got it stuck so i will assume it is.
Re: [boskid][2.0.12] a decider combinator has stopped working
Arithmetic and selector combinators can also become similarly stuck when marked for deconstruction then cancelling it / undoing it.
I'm assuming the fix applies for them as well?
I'm assuming the fix applies for them as well?
Re: [boskid][2.0.12] a decider combinator has stopped working
Yes, this fix applies to them as well, also this fix applies to them freezing and unfreezing.
Re: [boskid][2.0.12] a decider combinator has stopped working
This may be what happened. Some time before I had been in remote view and accidentally clicked with the deconstruction planner instead of the red wire, and so wanting to cancel that, I pressed escape, but that just took me out of remote view and left me with a very large selection on Nauvis, and so then when I released the mouse button I had deconstruction planned a large portion of my base, which I then canceled with control-z.boskid wrote: ↑Thu Oct 31, 2024 2:20 pmThanks for the report. I managed to find one case where a decider combinator could get stuck and it was related to marking it to deconstruct and cancelling the deconstruction. This case is now fixed for 2.0.14. I cannot confirm this is the exact way you got it stuck so i will assume it is.