Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

XyFreak

Members
  • Content count

    338
  • Joined

  • Last visited

  • Days Won

    27

XyFreak last won the day on March 2

XyFreak had the most liked content!

3 Followers

About XyFreak

  • Rank
    Leading Member

Contact Methods

  • Minecraft
    MC_XyFreak

Recent Profile Visitors

2175 profile views
  1. XyFreak

    Big Reactors Grid Control

    The installer is just badly written and needs to copy everything to ram first *cough* BRGC needs less ram to run than the installer needs ^^;
  2. XyFreak

    Big Reactors Grid Control

    @greenrhino33 You need more ram for the installer. Also T1 screens and gpus are not supported (if you intend to use the gui that is)
  3. XyFreak

    Big Reactors Grid Control

    @cookieman768 Sounds like you changed the reactor layout after connecting the computer port. I suggest either removing the configuration file (and restarting) or breaking and replacing the port.
  4. XyFreak

    Big Reactors Grid Control

    That depends on (a) your current energy demand and (b) the mode the grid controller is running in at that moment. Since you're >50% the grid controller propably started in DECREASING CHARGE mode, meaning it'll drain your storage until it reaches 20% and then charge it up to 95%, then drain it to 20% again etc etc... If you connect multiple turbines it'll try to minimize the energy drainage / charging rate to keep your setup running more efficiently. Ofc if your energy demand raises above what you can actually produce, everything will kick on to maximize the remaining uptime of your grid.
  5. XyFreak

    Big Reactors Grid Control

    @Bjoerniboii SUSPENDED means the controller (you're running GRID mode, right?) decided that your turbine does not need to be run. Most likely because there's a net gain of energy in your energy storage (INCREASING CHARGE) or because your turbine would charge your energy storage in DECREASING CHARGE mode. EDIT: It may also be the case that your turbines internal energy storage is saturated
  6. XyFreak

    Big Reactors Grid Control

    Fixed, sorry but ACME DNS verification can be a bitch if your TTL is 86400 seconds :/
  7. XyFreak

    Big Reactors Grid Control

    Yeah there seems to be an issue with Lua 5.3 and linux servers. From what I can tell OpenComputers falls back to LuaJ for 5.3 on linux or something. But that is PURE speculation. When I fix my desktop linux I might do some more testing on that.
  8. XyFreak

    Big Reactors Grid Control

    So you already correctly deduced that your OpenOS is too old. I can't help you with the updater though, sorry. You might want to ask for help in the OpenOS-Updater thread.
  9. XyFreak

    Big Reactors Grid Control

    reactor_ctrl.lua line 84 - just add some numbers
  10. XyFreak

    Big Reactors Grid Control

    No, using Big Reactors or Extreme Reactors doesn't matter. If you use steam for something else this IS gonna be a problem cause the program makes all kinds of assumptions based on how much steam is required by the turbines. It does indeed compensate but that's mostly for error correction not for making up for missing numbers
  11. XyFreak

    Big Reactors Grid Control

    Lemme ask you as well: Is there a way I can look into the issue myself / firsthand?
  12. XyFreak

    Big Reactors Grid Control

    I don't think so as the GUI displays the hot fluid tank as full - which wouldn't happen if the bug was active in your case... is that fortunate or unfortunate tho? xD
  13. XyFreak

    Big Reactors Grid Control

    Welp - that clearly rules out any fluid related issues...
  14. XyFreak

    Big Reactors Grid Control

    @Chrisszzyy sorry for not noticing the part where you statet you already recalibrated. I guess I was too focused at thinking what MIGHT help and not double checking. I noticed that your output poly has a max of 9453 mB/t while the reactor I built from your image has 6521 mB/t . Also the calculated optimum is set to 0.01 (wrong) while it has a proper value for me. Is there a server I can reproduce your issues directly on? I'm a bit at a loss here but I also noticed something else with extreme reactors yesterday: @ZeroNoRyouki I'll ping you as well since you might want to know what's going on here. When I first start up my minecraft and load a single player world for the first time, the APIs related to querying the hot fluid state are broken. Both the old and the new ones. The reactor I built from @Chrisszzyys description has a steam tank holding 31400 mB. While this is reported correctly, the current amount of hot fluid is not. The API maxes out at 6250ish mB for that reactor. I'm not 100% sure of whether it just caps out or actually scales but it might do both. The APIs behave normally as soon as I reload the world. Restarting minecraft causes this issue to appear again. All active reactors are affected. Even newly built ones. If this also happens on a server then this might already be the issue (since you can't reload the world without restarting the server - in which case the issue comes up again). The ER version I use is 0.4.5.49 and zerocore 0.1.2.2 The issue CAN be confirmed using BRGC as well as it will display the hot fluid tank as not full when it is - in fact - completely full. @Moobien please excuse me if i ask stupid questions or anything. Your reactor looks fine (size wise) so I'm wondering if there might be an issue with fluid transfer. The reactor is definitely hitting a ceiling before it even gets a chance to take its first measurment - it wouldn't error out otherwise.
  15. XyFreak

    Big Reactors Grid Control

    @Chrisszzyy Thanks, I just built your reactor in my test world and it worked flawlessy. Here's what I think happened: You kicked off everything at once, as you should be able to. This caused the turbines to speed up and the reactor to start calibrating at the same time. Then your turbines went overspeed and got shut down, suddenly causing the reactor to overproduce steam causing calibration to terminate. During the last phase something went wrong when calculating the output curve. I can only suggest you rerun the reactor calibration, assuring the turbines won't suddenly fail. Can you post your br_control.cfg as well? The generated config should look similar to what I here so we can test whether or not my theory is plausible. ["d69713ac-bbb2-4ed1-bda5-6e2b11017210"] = { outputOpt = 0.21747975557943, rodLevelMin = 0, outputReversePoly = {coefs={0,0.00015333991938894}}, outputPoly = {coefs={0,6521.4590172277}}, }
×

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.