- Sky
- Blueberry
- Slate
- Blackcurrant
- Watermelon
- Strawberry
- Orange
- Banana
- Apple
- Emerald
- Chocolate
- Charcoal
XyFreak
-
Content Count
401 -
Joined
-
Last visited
-
Days Won
32
Everything posted by XyFreak
-
@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.
-
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) * wheight
-
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).
-
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\opencomput
-
Ok since I need a github account I'm just gonna ping @payonel and hope he's the right guy for the job! Here's what's up: This commit here broke BRGC - and it actually broke timers in general whenever event.pull is involved. BRGC uses events and timers all over the place. The entire thing is running asynchronously. Now usually you don't want to drop to the prompt when running a program so here's what it does: function libGUI.run() while event.pull(math.huge, "libGUI_terminate") == nil do end end It just waits for a libGUI_terminate event and then cleans up stuff. Pretty e
-
Yeah at this point I'm convinced it's a bug in recent versions of OpenOS - I'm gonna file a bug report
-
Ok i traced it back to changes in /lib/event.lua - stay tuned!
-
Hey guys, I've been able to confirm this issue after updating OpenOS - unless I can say for sure it's not an issue on my end I'm not gonna bisect the OpenOS version it starts happening on tho... tbc...
-
I do not have a solution for this issue - the gui is using a timer to redraw stuff - if it suddenly stops drawning then i don't think there's anything wrong with the program. In order for me to test things out I need you to tell me the version of OC, ER and propably your forge version as well.
-
@CygnusiaX1 Can you check if its related to some mod you are using ( *hint* optifine *hint* ) - the shell cursor should be blinking if you just leave the pc on after booting @BrisingrAerowing I did but I forgot about it. `rftools_powercell` is already part of the whitelist. If your mod changes that then please add it to `/usr/lib/brgc/energy_storage_component.lua` and let me know if it works - i'll add it if it does.
-
@CygnusiaX1 the screen "updates" every second (it only redraws stuff that needs to be redrawn tho)
-
Well the design i posted is a drop-in replacement for your current design with no changes to the exterior required so you can go for that if you want to - it's up to you in the end As i mentiond in my last post: 3x3 cores or rings work very well as long as there's one layer of coolant between them
-
Nah that won't be necessary. If calibration fails that badly, that usually means your reactor has an efficiency curve where its most efficient point is VERY close to 100% rod insertion (in your case that'd be ~97%). Sorry but i don't think you can get brgc to work properly with your design. I just checked and when ran at peak efficiency, the 9x9 core is indeed a tad more efficient than 4 individual 3x3 cores ( https://br.sidoh.org/#reactor-design?length=11&width=11&height=10&activelyCooled=false&controlRodInsertion=91&layout=24C3XC3X4C3XC3X4C3XC3X15
-
If you extended your reactor you need to make sure BRGC recalibrates it or otherwise it won't know that the reactor is now different. There are multiple ways to do this: Break & replace reactor computer port (this causes the old config to still be present somewhere tho) Remove the config file ( rm /etc/br_control.cfg ) then reboot do a brgcctrl recalibrate <first three characters of reactor address here> I recommend (3) but (2) is propably easier than that and way cleaner than (1)
-
Ah ok I see what you did. The ON/OFF switch you pressed is not doing what you think it does You turned off the GRID controller, which caused the reactor control to fall back to standalone mode. Since you're draining the reactors buffer into your induction matrix, the controller assumed that you are using more energy than you can produce and thus the reactor was running full throttle. If you want to turn off the reactor you need to go to the "Reactors" (or "Combined") Tab and disable the reactor from there (click on the reactors bar). CHARGE mode only does something if you have
-
Hi @Minoslo Can you give me some more info? How is your reactor built? Active/Passive? Did you connect some sort of energy storage to the computer via an adapter? What do you mean by when you tried to put if off? Did you try to turn off the reactor via the GUI? That should just.... turn it off (reactor controller block turning red).
-
It SHOULD work with T2/T2.5 (the installer needs lots of ram) components but as always I recommend you just go with T3 stuff to make sure everything runs smoothly.
-
So the 1.7 version is built around extracting energy from the reactor and reinjecting it through a seperate circuit. As a result, the flux gate extracting energy that goes to storage is only extracting CALCULATED_OUTPUT - REINJECT So there's your problem. Your setup looks more like the 1.10 setup, in which case you should propably use the 1.10 program. (I knew i changed something important going from 1.7 to 1.10)
-
It looks like not enough power is being extracted from the reactor. DC is "immune" to config file changes as it has code in place to figure out those multipliers through backwards calculation (and sometimes they just don't matter). Is wherever you're piping the energy to able to accept that much / store that much? (I'm guessing yes but still asking )
-
It should display the RF transfer limit in green text at the bottom of its GUI
-
@Chaoschaot234 no i never got around doing that, sorry. @Electro56 If your temperature is stuck at 20 degrees then your reactor isn't even charging. Please have a look at the flux gate at the energy injector. If that's in computer mode and >0 then the flux gate is either facing the wrong way, not connected to energy or something is just not behaving connection wise. EDIT: @Chaoschaot234 regarding your edits: The GUI always selects the first reactor. If you look for a line like local controller = draconic_control.controllers[1] towards the end of the dc_gui.lua y
-
exactly you're welcome
-
no but if you're using my building guide, you should definitely follow the new one.
-
@isaacay One last thing, since you are looking at the 1.7 page - the setup on the non-1.7 page is safer and you should go for that instead. It won't change any of the logic but shutting down the reactor is... not incredibly risky anymore.