Reactor Control not registering all Rods
Opened this issue · 9 comments
I created a 13x13x5 reactor with 25 rods. The control block is only acknowledging 10-22 rods (variable upon breaking the control block and putting it back).
There are no errors in the console and neither in Forge log unfortunately.
I am attaching the power tap block to a TE Redstone energy conduit and using refined uranium as a power source.
Please note that energy output is unchanged regardless of how many rods are registered on the Control GUI. simple GUI bug?
Awesome mod btw. Cannot wait for more mechanics!
If I restart minecraft,it seems the GUI is registering all 25 rods. However if I break any block the issue happens again. Again there is no change in the power output at all.
I think this is a GUI bug :)
Sort of. It's likely a problem with the assembly code. The other control
rods are probably "owned" by an erroneously-created controller which
spawned during the breakage of the machine. Restarting clears all the data
and makes it one machine again.
On Jun 29, 2013 10:10 PM, "Tickbuz" [email protected] wrote:
If I restart minecraft,it seems the GUI is registering all 25 rods.
However if I break any block the issue happens again. Again there is no
change in the power output at all.
I think this is a GUI bug :)—
Reply to this email directly or view it on GitHubhttps://github.com//issues/19#issuecomment-20236378
.
Interesting. Can you post a screenshot of the top of your reactor so I can
replicate your control rod arrangement?
On Sat, Jun 29, 2013 at 5:19 PM, Tickbuz [email protected] wrote:
I created a 13x13x5 reactor with 25 rods. The control block is only
acknowledging 13-18 rods (variable upon breaking the control block and
putting it back).
There are no errors in the console and neither in Forge log unfortunately.
I am attaching the power tap block to a TE Redstone energy conduit and
using refined uranium as a power source.
Awesome mod btw. Cannot wait for more mechanics!—
Reply to this email directly or view it on GitHubhttps://github.com//issues/19
.
Thanks for the report, I think I know the underlying cause. Will
investigate.
On Jun 29, 2013 6:55 PM, "Tickbuz" [email protected] wrote:
http://imageshack.us/photo/my-images/855/p7q.png/
http://imageshack.us/photo/my-images/692/36ko.png/
—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/19#issuecomment-20233209
.
Turns out this a pretty nasty low-level issue on the client. Still working on a fix.
Fix found and checked into BeefCore. It was an exceptionally nasty low-level bug involving how the minecraft client handles block updates vs. how the server handles block updates.
Fix will be in 0.1.13A.