02-01-2019, 05:28 PM
I've come up with a solution that I hope to implement after I've completed a working model. Here's a summary of the difference:
John's system
1) A user presses a button at a station and a binary number representing the destination is broadcast across the entire network.
2) ALL junctions decode this number and point their tracks in the direction of the station represented by the number.
Simple, elegant and if you are the only one using the system it works like magic. When I told John at the outset that this will fail as soon as another person presses a button while somebody is traveling he told me that redstone signals won't propagate over unloaded chunks. Not quite that simple though, as we have demonstrated.
Kata's system
1) A user presses a button at a station loading a memory module with the path necessary to get to the station represented by the button.
2) The user places their cart and presses the launch button which uses the memory module to set the track and send the signal on to the next (specific) junction.
3) The signal reaches the next junction, loads into that junction's memory module and waits for the user's cart to arrive.
4) The user reaches the junction triggering it to read the memory module, set the track and send the remaining signal on according to the signal data.
5) Return to and continue at (3) until the destination is reached.
I have replaced John's serializer (the component that turns multiple signals into a single binary number) with a decoder (the component that returns a binary signal to multiples)/programmable memory circuit/serializer combo so my system will still use John's buttons to program the memory but requires far less redstone to accomplish the task. I still need a big multiplexer design to send the signals in the proper directions but that won't be difficult to put together. Stand by for information on my first working model for testing!
John's system
1) A user presses a button at a station and a binary number representing the destination is broadcast across the entire network.
2) ALL junctions decode this number and point their tracks in the direction of the station represented by the number.
Simple, elegant and if you are the only one using the system it works like magic. When I told John at the outset that this will fail as soon as another person presses a button while somebody is traveling he told me that redstone signals won't propagate over unloaded chunks. Not quite that simple though, as we have demonstrated.
Kata's system
1) A user presses a button at a station loading a memory module with the path necessary to get to the station represented by the button.
2) The user places their cart and presses the launch button which uses the memory module to set the track and send the signal on to the next (specific) junction.
3) The signal reaches the next junction, loads into that junction's memory module and waits for the user's cart to arrive.
4) The user reaches the junction triggering it to read the memory module, set the track and send the remaining signal on according to the signal data.
5) Return to and continue at (3) until the destination is reached.
I have replaced John's serializer (the component that turns multiple signals into a single binary number) with a decoder (the component that returns a binary signal to multiples)/programmable memory circuit/serializer combo so my system will still use John's buttons to program the memory but requires far less redstone to accomplish the task. I still need a big multiplexer design to send the signals in the proper directions but that won't be difficult to put together. Stand by for information on my first working model for testing!
I've gone out to look for myself. If I return before I get back, hold me until I get there.
