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

3288 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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
  5. 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.
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. @ZeroNoRyouki The program assumes that whatever fluid gets produced, can be consumed by any connected turbine as long as it doesn't cap out the internal capacity. The power balancing might actually be an issue - but the fix would be: Don't attach ports if you don't need them.
  11. @BattyCynris Sorry for the delay i JUST got the email notification that you posted something. You are running into an OpenOS issue that should be fixed by now (see posts a bit "earlier" on this page). Please update OpenComputers and then reinstall OpenOS.
  12. You need to have all energy storage devices connected that sit immediately behind your generators (note all generators need to be able to feed all of them - dedicated storage devices for each generator are not supported). Intermediary energy devices don't REALLY matter but it'd obviously give the controller a better understanding of how much power you actually have. The wheighted is a rolling average where the factor is determined by how full your energy storage is ( formular is `wheighted_rft = (1 - (energy_stored / storage_total)) * current_rft + (energy_stored / energy_total) * wheighted_rft` ). That value is then used to determine how much power should be produced. The reasoning behind this is simple: If there's a lot of energy stored, react slowly cause there's energy stored - no need to up fuel consumption, is there? If there's less and less energy, the controller needs to react faster to changes in energy demand to not cause a power failure.
  13. Hi @GenSmicer The order to connect everything from a CLEAN INSTALL is: Turn on the turbines to make sure steam can be consumed. Connect the reactor. Wait for calibration to finish. Connect the turbines. That should be everything you need to do. What does "it also never really showed a number" mean? There is indeed an issue with RFTools power storage as it caps out at 2^31-1 RF stored (limitation of the API they use).
  14. I just realized that timers had a drifting problem since forever by the looks of it: Even since before the commit that broke things, if a timer called something that let time pass (i know this is bad anyways but it CAN happen), it would actually fully delay the deadline of successive timers (instead of just delaying the timer once). Here's another patch --- C:\Games\MultiMC\instances\Draconic Computers 1.12\.minecraft\saves\BRGC\opencomputers\a201b7a4-e2fd-4565-8b4b-79a6993a7e62\lib\event.lua.bak +++ C:\Games\MultiMC\instances\Draconic Computers 1.12\.minecraft\saves\BRGC\opencomputers\a201b7a4-e2fd-4565-8b4b-79a6993a7e62\lib\event.lua @@ -62,7 +63,11 @@ -- nil keys match anything if (handler.key == nil or handler.key == signal) or current_time >= handler.timeout then handler.times = handler.times - 1 - handler.timeout = current_time + handler.interval + -- we need to make sure the timer doesn't drift but at the same time doesn't get rescheduled + -- immediately if it's execution had been delayed significantly (>= handler.interval * 2). + repeat + handler.timeout = handler.timeout + handler.interval + until handler.timeout > current_time + handler.timeout -- we have to remove handlers before making the callback in case of timers that pull -- and we have to check handlers[id] == handler because callbacks may have unregistered things if handler.times <= 0 and handlers[id] == handler then I decided to go with a loop instead of math based, because the most likely case is this loop getting executed exactly once. Solving this with math would require math.floor which would propably be slower than this most of the time.
  • Create New...

Important Information

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