Big Reactors

Big Reactors

11M Downloads

Rector isn't ejecting waste at all.

SleeperAssassin opened this issue ยท 22 comments

commented

Was playing on a server my friend has and the reactor was running just fine. Just logged in and the reactor is no longer ejecting any wastes in either port. The only way to get it out for me at the moment is to dump wastes but then I can't work towards a actively cooled turbine reactor.

commented

Which version of Big Reactors are you running, and on which version of Forge and CoFHCore?

When you say it "wasn't ejecting", do you mean that it wasn't being ejected into attached pipes/inventories, or that cyanite ingots weren't appearing in access ports at all?

Screenshots would be helpful.

commented

A quick update to the problem. I also couldn't change the eject mode on the controller from auto to manual eject. We ended up having to break the entire reactor down and re-build it for it to clear out the stored data for what was inside it and then fix both problems after that.

commented

people these days they send a problem then they dont answer or check again expecting it to get fixed right away, they dont know how much work this is, am i right or not

commented

Sorry didn't get a notification to the respond. I can't get screenshots because it is working fine now. But what I mean is it wasn't ejecting the cyanite was coming out of the reactor at all... as in not to either access port out or in... no pipes or anything, just a basic reactor. We have the 0.4.0rc8 version and Forge version 1.7.10-1.1.0.300 and CoFHCore 3.0.0B6-32.

commented

As for Nick, dude when the problem is fixed and I don't get an email saying something was posted on it I don't check back. I understand its work... Im going to school for coding and game design. Just didn't know that he had posted. But keep assuming things about people... Working really well for you.

Have a good day.

commented

@SleeperAssassin - All right, well, I'm unable to reproduce this myself in the simple case. Either it was a one-off glitch or there's some complexity involved that neither of us understands. If it occurs again or you come up with a consistent reproduction case, please reopen the issue.

@Nick-77ab2 - Sneering at people over bug reports is rarely helpful. I'd appreciate it if you didn't do that on my bug tracker.

commented

to both of you i am sincerely sorry and did not mean what i said i was caught up in other things and was being a dick - Nick_77ab2

commented

Umm, Hi.
I've got this same issue (I would assume). I built the reactor and let it run for a while, and then I noticed that, despite having auto-eject, there were 11000mb of cyanite inside. I tried spamming auto-eject in the gui, but nothing happened, I could still empty the fuel rods, but not the waste. I can still delete all the waste with Shift. In the controller I can't switch between manual or auto-eject.

Using the pork i got: https://docs.google.com/document/d/1CpCechbL1pTXHk4Y-JTI6K5te-Cewbmy2qguDXsEFb8/pub

The reactor is 7x7x7.

Moving the save over to SP, fixed it. So I can't upload a save for you there where it doesnt work.
I cold give you my server Ip if you'd like to come try yourself?

commented

Interesting. The debug output says you've got 8993mb cyanite and the rest is yellorium. Does a server reboot fix it, or does this happen all the time?

commented

Reboot doesnt fix it, I eneded up tearing it down and rebuilding it to make it work. Really strange that moving the save to a singleplayer world fixes it...

commented

Hmm. Sounds like some issue with serialization or something. Let me know if you manage to find a way to reproduce the problem consistently, please.

commented

I've just encountered this issue on FTB using Direwolf20's modpack for 1.7.10.

I logged into a server where I had left my reactor running. It's a 5x5 square, 3 blocks high (1 row casing, 1 row fuel rod/coolant, 1 row casing). I put 4 ingots in and had left the server earlier in the day. Logging in now and I can't switch from Auto-Eject to manual. It was also already in manual mode and should have stayed there since I have no automated system for refueling/waste removal.

I can turn it online/offline, but can't change auto-waste setting. Haven't done anything to it yet except tried adding more fuel to see if there was a problem with that (there wasn't).

Anything you want to see while it's broken? I can leave it like this.

commented

Just wanted to add I'm having the same issue using DW20's 1.7.10 modpack (version 1.0.3). I too can leave the reactor like this for a while if there are things you would like to know.

commented

Would you mind using the debugging tool (looks like a steak with some gold/green on it)? Rightclick the reactor with the debugging tool in-hand, then shift+rightclick. Grab the output from your logs and post it here, please.

commented

Thanks for your response, erogenousbeef!

For some more information: I did manage to get the Yellorium out. My reactor is a 7x7x5 with 5 fuel rods, cooled with liquid enderium.

I pasted the full log at http://pastebin.com/NcCHCXcP, this is from the latest.log file.

Partial log that contains the relevant (I think) information:

[18:07:37] [Client thread/INFO]: [CHAT] [SERVER] Beef Debug Tool:
[18:07:37] [Client thread/INFO]: [CHAT] class erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPart
[18:07:37] [Client thread/INFO]: [CHAT] Assembled: true
[18:07:37] [Client thread/INFO]: [CHAT] Attached Blocks: 182
[18:07:37] [Client thread/INFO]: [CHAT]
[18:07:37] [Client thread/INFO]: [CHAT] Active: true
[18:07:37] [Client thread/INFO]: [CHAT] Stored Energy: 0.0
[18:07:37] [Client thread/INFO]: [CHAT] Casing Heat: 19.998854
[18:07:37] [Client thread/INFO]: [CHAT] Fuel Heat: 20.002245
[18:07:37] [Client thread/INFO]: [CHAT]
[18:07:37] [Client thread/INFO]: [CHAT] Reactant Tanks:
[18:07:37] [Client thread/INFO]: [CHAT] Capacity: 48000[0] fuel: NULL
[18:07:37] [Client thread/INFO]: [CHAT] [1] waste: cyanite, 33000 mB
[18:07:37] [Client thread/INFO]: [CHAT]
[18:07:37] [Client thread/INFO]: [CHAT]
[18:07:37] [Client thread/INFO]: [CHAT] Actively Cooled: false
[18:07:42] [Client thread/INFO]: [CHAT] [CLIENT] Beef Debug Tool:
[18:07:42] [Client thread/INFO]: [CHAT] class erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPart
[18:07:42] [Client thread/INFO]: [CHAT] Assembled: true
[18:07:42] [Client thread/INFO]: [CHAT] Attached Blocks: 182
[18:07:42] [Client thread/INFO]: [CHAT]
[18:07:42] [Client thread/INFO]: [CHAT] Active: true
[18:07:42] [Client thread/INFO]: [CHAT] Stored Energy: 0.0
[18:07:42] [Client thread/INFO]: [CHAT] Casing Heat: 19.998854
[18:07:42] [Client thread/INFO]: [CHAT] Fuel Heat: 20.002245
[18:07:42] [Client thread/INFO]: [CHAT]
[18:07:42] [Client thread/INFO]: [CHAT] Reactant Tanks:
[18:07:42] [Client thread/INFO]: [CHAT] Capacity: 48000[0] fuel: NULL
[18:07:42] [Client thread/INFO]: [CHAT] [1] waste: cyanite, 33000 mB
[18:07:42] [Client thread/INFO]: [CHAT]
[18:07:42] [Client thread/INFO]: [CHAT]
[18:07:42] [Client thread/INFO]: [CHAT] Actively Cooled: false

commented

I logged in a few minutes ago, and the reactor appeared to be functional (I hadn't touched it in a long time). After running it for a bit and leaving the area, then returning, it seemed to have broken again. I have the before and after logs:

BEFORE:

[20:51:22] [Client thread/INFO]: [CHAT] [CLIENT] Beef Debug Tool:
[20:51:22] [Client thread/INFO]: [CHAT] class erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPart
[20:51:22] [Client thread/INFO]: [CHAT] Assembled: true
[20:51:22] [Client thread/INFO]: [CHAT] Attached Blocks: 67
[20:51:22] [Client thread/INFO]: [CHAT]
[20:51:22] [Client thread/INFO]: [CHAT] Active: false
[20:51:22] [Client thread/INFO]: [CHAT] Stored Energy: 2359610.8
[20:51:22] [Client thread/INFO]: [CHAT] Casing Heat: 19.996447
[20:51:22] [Client thread/INFO]: [CHAT] Fuel Heat: 19.997845
[20:51:22] [Client thread/INFO]: [CHAT]
[20:51:22] [Client thread/INFO]: [CHAT] Reactant Tanks:
[20:51:22] [Client thread/INFO]: [CHAT] Capacity: 4000[0] fuel: yellorium, 1707 mB
[20:51:22] [Client thread/INFO]: [CHAT] [1] waste: cyanite, 293 mB
[20:51:22] [Client thread/INFO]: [CHAT]
[20:51:22] [Client thread/INFO]: [CHAT]
[20:51:22] [Client thread/INFO]: [CHAT] Actively Cooled: false

[20:51:18] [Client thread/INFO]: [CHAT] [SERVER] Beef Debug Tool:
[20:51:18] [Client thread/INFO]: [CHAT] class erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPart
[20:51:18] [Client thread/INFO]: [CHAT] Assembled: true
[20:51:18] [Client thread/INFO]: [CHAT] Attached Blocks: 67
[20:51:18] [Client thread/INFO]: [CHAT]
[20:51:18] [Client thread/INFO]: [CHAT] Active: false
[20:51:18] [Client thread/INFO]: [CHAT] Stored Energy: 2359610.8
[20:51:18] [Client thread/INFO]: [CHAT] Casing Heat: 19.996447
[20:51:18] [Client thread/INFO]: [CHAT] Fuel Heat: 19.997845
[20:51:18] [Client thread/INFO]: [CHAT]
[20:51:18] [Client thread/INFO]: [CHAT] Reactant Tanks:
[20:51:18] [Client thread/INFO]: [CHAT] Capacity: 4000[0] fuel: yellorium, 1707 mB
[20:51:18] [Client thread/INFO]: [CHAT] [1] waste: cyanite, 293 mB
[20:51:18] [Client thread/INFO]: [CHAT]
[20:51:18] [Client thread/INFO]: [CHAT]
[20:51:18] [Client thread/INFO]: [CHAT] Actively Cooled: false

AFTER:

[21:06:29] [Client thread/INFO]: [CHAT] [CLIENT] Beef Debug Tool:
[21:06:29] [Client thread/INFO]: [CHAT] class erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPart
[21:06:29] [Client thread/INFO]: [CHAT] Assembled: true
[21:06:29] [Client thread/INFO]: [CHAT] Attached Blocks: 67
[21:06:29] [Client thread/INFO]: [CHAT]
[21:06:29] [Client thread/INFO]: [CHAT] Active: true
[21:06:29] [Client thread/INFO]: [CHAT] Stored Energy: 4619241.0
[21:06:29] [Client thread/INFO]: [CHAT] Casing Heat: 59.082413
[21:06:29] [Client thread/INFO]: [CHAT] Fuel Heat: 62.33238
[21:06:29] [Client thread/INFO]: [CHAT]
[21:06:29] [Client thread/INFO]: [CHAT] Reactant Tanks:
[21:06:29] [Client thread/INFO]: [CHAT] Capacity: 4000[0] fuel: yellorium, 882 mB
[21:06:29] [Client thread/INFO]: [CHAT] [1] waste: cyanite, 2118 mB
[21:06:29] [Client thread/INFO]: [CHAT]
[21:06:29] [Client thread/INFO]: [CHAT]
[21:06:29] [Client thread/INFO]: [CHAT] Actively Cooled: false

[21:06:32] [Client thread/INFO]: [CHAT] [SERVER] Beef Debug Tool:
[21:06:32] [Client thread/INFO]: [CHAT] class erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPart
[21:06:32] [Client thread/INFO]: [CHAT] Assembled: true
[21:06:32] [Client thread/INFO]: [CHAT] Attached Blocks: 67
[21:06:32] [Client thread/INFO]: [CHAT]
[21:06:32] [Client thread/INFO]: [CHAT] Active: true
[21:06:32] [Client thread/INFO]: [CHAT] Stored Energy: 4629093.5
[21:06:32] [Client thread/INFO]: [CHAT] Casing Heat: 58.67587
[21:06:32] [Client thread/INFO]: [CHAT] Fuel Heat: 61.891254
[21:06:32] [Client thread/INFO]: [CHAT]
[21:06:32] [Client thread/INFO]: [CHAT] Reactant Tanks:
[21:06:32] [Client thread/INFO]: [CHAT] Capacity: 4000[0] fuel: yellorium, 873 mB
[21:06:32] [Client thread/INFO]: [CHAT] [1] waste: cyanite, 2127 mB
[21:06:32] [Client thread/INFO]: [CHAT]
[21:06:32] [Client thread/INFO]: [CHAT]
[21:06:32] [Client thread/INFO]: [CHAT] Actively Cooled: false

commented

That is a very interesting log. Looks like this isn't related to a different serialization problem. Thanks for posting that.

I'll probably have to modify the tool to get additional info. Let me see what I can do - I'm on the road at the moment.

commented

Restarting the server made all the cyanite eject somehow, probably because it was set to auto output. I'll try to reproduce the issue.

commented

hey same issue here as olafski the gui buttons for the control panel dont even respond to eject or not to eject waste its stuck on eject waste but it will not eject waste untill serve restart and eventualy the reactor fills up with waste i have a inlet and outlet tried forcefully pulling items out with a extracting pipe. with a chest on it as well. tried everything it so in short GUI buttons for waste is locked up and stuck on eject waste will not eject waste to blue outlet port which is empty

can i just compile your git and test it out?

commented

You're welcome to compile the git any time you like. It's open source, after all.

I'm hoping to get some time to do a build this weekend, so fingers crossed for a release then.

commented

btw it says rector not reactor, i was confused for a second xD

commented

meh i spelled engrish wrong anyway beef your git works fine it fixed the issue i compiled and ran it on my server thats a very stable build on your dev branch