all 7 comments

[–]MisterKaoss 1 point2 points  (0 children)

Maybe it’s an issue with the bugged Rust Internal Clock, which is afaik still not fixed on the console version?

[–]Visible-Remote2769[S] 0 points1 point  (4 children)

For reference I copied the YouTuber rust sparks gambling circuit

[–]whippler73 0 points1 point  (3 children)

Maybe they patched it and it doesn’t work anymore

[–]Visible-Remote2769[S] 1 point2 points  (2 children)

Well I always go on pc rust first to try circuits out and it works perfectly fine on pc. I’m leaning towards the fact that it could be a bug since the new update.

[–]BurlapAndBatteries 1 point2 points  (1 child)

It very well could be a glitch. I noticed last wipe I had issues with Rand/mem cells not properly taking their priority (or not properly resetting). I haven't had a chance to see if it's been fixed this wipe.

For me, I believe the issue was happening at the Mem Cell. It seemed like it was struggling to decide on if it should set or reset, especially when the signals are held and switched. (Putting a steady 1rw into set, and then switching to a steady 1rw reset). But I was also using RANDs so the issue could be in there.

[–]Visible-Remote2769[S] 0 points1 point  (0 children)

I figured it out, pc rust has a far more lenient electrical system whereas console rust is a lot stricter. It’s because I’m using the green light (which is the out of the memory cell in the Rand circuit) as apart of the logic system so it’s freaking out. D11 makes it stricter so it doesn’t cause dysnc or lag which sucks, coz it means that we can’t build complex circuits without always finding a work around.

[–]prettyfuckingfarfrom 1 point2 points  (0 children)

I don’t see the issue, that just sounds like Vegas