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


  • Content Count

  • Joined

  • Last visited

  • Days Won


XyFreak last won the day on December 2 2018

XyFreak had the most liked content!


About XyFreak

  • Rank
    Leading Member

Contact Methods

  • Minecraft

Recent Profile Visitors

3604 profile views
  1. There's a comma missing at the end of the "fluxGateDrainbackAddress" line
  2. Hi @KnockOutGamer There is no additional work required for 1.12.2. If you get the message, you propably have a typo somewhere.
  3. @stealth95l The grid controller drains your energy storage until it's below 20% and then carges it until it's 95% full. It does so by tweaking energy production to be just shy of what you are actually consuming for discharging and just a bit more when charging. The assumption here is that for charging, less production is more efficient overall, and keeping your energy storage filled for longer improves responses to sudden power surges. Note that it will always drive your components at their peak efficiency, unless you have passive reactors in your system and are requesting more energy than you can efficiently produce. Meaning: Turbines will always run at peak efficiency or are halted. Reactors SHOULD always run at peak efficiency except when you just need more power.
  4. @stealth95l Well it's just blindly dividing by 0 so... *cough* woops. 0 would be wrong btw - it should propably display "---" or maybe "not connected". @bjonnfesk You have OpenOS 1.7.4, which is bugged - you'll need to update OpenComputers or use the OpenOS updater. This has been discussed here quite a bit. BRGC is not on a public git repo because I never wrote a "build script" so I just checked in the entire OpenOS installation *cough* and use my package builder to build and upload the different libs and packages from the running installation *cough*. ( I should get that cold checked )
  5. There is no particular safety check in place - it's just that the system itself stops working properly at some point. There is code in place to mitigate some of it but unfortunately it's something that's nothing I can easily fix. The internal capacity is based on the reactors size but caps out at 50B. What you could do is build a second reactor and BRGC is gonna split the load.
  6. The main issue is that the internal steam capacity is limited to 50B so as soon as you hit >25B/t steam and it's no longer possible to level out at 50% (25B) everything kinda goes downhill.
  7. Hi @Freedbot, the issue is that BRGC has issues with certain reactor designs when you attempt to push past 50% total capacity. You could try to recalibrate the reactor with all turbines connected and see if that helps.
  8. No you will either have to use a loooong cable and chunkload a the entire cable or use some kind of mod that allows direct OC connectivity wirelessly
  9. When I tried to update my test instance I noticed that no new version of OC has been uploaded to curseforge yet. That means that the timer bug is still a thing in your OpenOS installations So the "fix" is to downgrade OC (and reinstall OpenOS afterwards) or do the thing at the bottom of my post here That would explain why @ZeroNoRyouki runs into issues as well as all of your "calibration stuck" issues. I'm sorry but that is something I can't fix.
  10. Please post a schematic of your reactor so I can investigate the issue. Calibration never took longer than 3 minutes for me (passive reactor). Active reactors calibrate really fast tho.
  11. Can you try a "brgcctrl service reactor runOnce" and see if an error occurs? Also a screenshot of the reactors GUI and the layout would be nice.
  12. Welp - your setup is a lot bigger than my test setup then xD I'll look into it. My guess is that they run into an error while they're being spun up to optimal rpm? I'll try to free up some time to build a new setup and debug the issue. Also... maybe scrollbar
  13. Scrolling support, eh? maybe Sounds easy, right? Fricking hard to actually do. If your turbines run straight into "error" mode then you have more turbine blades for your coil. BRGC assumes that if your turbine has enough blades to support X mB/t then your coil does too. EDIT: That being said - if that's not the case and everything SHOULD work but its not then its a bug
  • Create New...

Important Information

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