Mekanism Tools

Mekanism Tools

87M Downloads

Fusion reactor fails to generate power on Server Client

Closed this issue ยท 16 comments

commented

Issue description

When the fusion reactor is started, the Plasma immediately heats up, however, the casing does not heat up, and no energy is produced. This bug was experienced in the latest version of ATM10. Find attached images of the issue.

Image

Image

Image

Image

Steps to reproduce

  1. Build a Fusion reactor in any configuration of ports/glass/frame within one chunk
  2. Insert the hohlraum and ignite using lasers
  3. If on the server client, the fusion reactor will not produce any power, but will sustain the reaction

I have tested the following

  1. Tested in an SP world, and the fusion reactor generated power
  2. Tested various configurations of the reactor itself with and w/o reactor glass or additional ports, no change
  3. Tested with chunk unclaimed, no change
  4. Tested providing DT fuel alongside Deu and Trit, no change
  5. Tested initially in a compact machine, then broken down and moved to the overworld, no change
  6. Tested different injection rates (2,40,48,98), no change
  7. Tested watercooling, no change
  8. Tested starting the reactor after restarting the server, no change

Minecraft version

1.21.1 (Latest)

NeoForge version

21.1.168

Mekanism version

10.7.14 (Latest)

Other relevant versions

The server is running ATM10 version 2.47

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

No response

commented

Someone on the discord had this on ATM, breaking and replacing the controller block fixed it for them.

Likely a bug due to something else in ATM

commented

Hey Thiakil,
I have broken and replaced the control block and the entire structure before because it has solved issues in the past.
I just broke the control block and replaced it again as you suggested just now, but this has not resolved the issue.
Thanks anyway,

commented

wait, you didn't forget the Hohlraum, did you?

commented

ah, no, i see the animation that shows it ignited.
try moving the reactor slightly. But otherwise, ATM may have screwed with the configs and broke it, or another mod is interfering

commented

I have moved the reactor 4 times and tried it both in the overworld and within a compact machine just to see if the DIM was messing with it. I think the issue is more related to something different between MP and SP, as I tested making a reactor within a SP world, and it ran fine, yet I run into this issue on MP.

commented

there must be something weird on the server or ATM10's server pack, as there's nothing that makes the transfer of heat from plasma to case conditional in vanilla Mekanism.

Image

commented

Image

Works fine for me on ATM10

commented

Hey, so as of the newest update of ATM10 that came out a few days ago, this bug no longer occurs. I would be happy to provide the previous versions' files if you would like to continue investigating. We rebuilt the fusion reactor yesterday on the new patch, and it is working as intended.

commented

Can you show us the configuration of ports on the failed reactor? There may be a bug specific to that.
And I'd there still an entangoloporter involved?

commented

As noted in the original report, the issue persisted no matter the structure of the reactor. I tested it with 3,6, and 8 ports respectively, with and without reactor glass and changing the orientation of the ports and laser focus matrix. Fuel delivery was done through 2 different entagloporters running on two different networks with all sides for the different modes disabled, excluding gas on output to the port. Power was meant to be extracted by a flux plug. A point of note is that the owner of the entangloporters was a friend rather than myself, however, I had trusted access.

commented

Huh. Interesting, we were thinking it may be the entangoloporters inadvertently sucking out heat, but aparrently not

commented

hmm I can't reproduce it on 2.47 either.... At 40 rate it still boots fine

Image

commented

I honestly don't know what to say other than updating to 3.0 fixed the issue. I have no more information to provide, and given that you cannot seem to recreate it, I am putting it down to some form of download corruption at some point. I am closing the ticket as there seems to be no way to progress any further investigation into the now resolved issue.

The only difference I can see in your own testing is that it is on Multiplayer LAN rather then Third Party. But other then that I am out of ideas

commented

What do you mean "third party"?

commented

Image

commented

Odd, probably the same thing, just that I spun on the server on my computer