- 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
-
It's been a WHILE - but it is finally time... Big Reactors Grid Control Version 4.2.6 has been released! Changelogs: - Greatly reduced the number of API calls for setting reactor fuel rod levels. - Fixed a bug where the reactor controller would miscalculate the fuel rod offsets with sub 1% precision. - Fixed a bug where the grid controller would not set the reactors output rate to the optimum but leave it as is when coming out of "HOLDING CHARGE" mode. - Partially rewrote calibration code for reactors to remove "magic values". - The Tabs for "Reactors" and "Turbines" will be
- 852 replies
-
- 1
-
-
- gui
- controller
- (and 2 more)
-
Ditto, the 1.10.2 version runs fine with 9 turbines and a reactor. I also noticed that a bug i fixed in brgc makes the active reactor controller run smooth like butter now >_> I'm actually glad I was kinda forced to look at the rod level control code again... ^^"
-
@ZeroNoRyouki gotcha. (fingers crossed) If you need input/ideas on anything thread-safety related feel free to hit me up with a pm or something.
-
Oh so you have to approve posts before they trigger notifications? THAT explains a LOT. Thanks for letting me know
-
Sorry for reacting to your post just now. I just got notified about it and as you can see, a lot was going on. brgcctrl is already telling you what's wrong: You need to supply the reactors address or at least a partial address (read 3 or more characters of the address). Also the API issues we've been discussing here are propably responsible for your reactor not being (properly) calibrated so please wait a while longer until zeros fix is up on curse.
-
Hmhm, I hope this "old-direct-call-we-dont-care-about-threads-because-who-knows" doesn't imply: We're not thread-safe I'll grab it as soon as I can and run it in my test world with some larger setups. On a different note, I'm currently preparing a new release of BRGC. Here's what's in so far (subject to change): Support for mekanism induction matrix Greatly reduced the number API calls for setting reactor fuel rods Fixed a bug where the grid controller would not set the reactors output rate to the optimum but leave it as is when coming out of "HOLDING C
-
Oh yeah, that's a thing by now. I should change that as it's "way" easier
-
THANK YOU! @ZeroNoRyouki You know about that one don't you? If that fixes things... I need to run around and apologize to ppl... >_>
-
I'm not sleeping in a 'service' thread, I'm using timers
-
From what zero told us here I was under the impression that he already is using the api as it's supposed to be used. @payonel I did not know the github issue gained some steam during the last couple of days. Thanks for bringing that to my attention. You've been saying that oc is not a realtime system and i agree. if yielding after each component api call is the intended bebaviour i'd like to see that documented somewhere. Also that limit should be enforced for all mods/apis. And if that's really the case then ... let's say I'm going to be sad
-
@payonel Please check the post you quoted from ;). On the last two pages of this thread we discussed it in some more detail.
-
Hi @ZeroNoRyouki Thanks. Here's a list of things I would query but maybe it'd be a good idea to have a command that includes all non-mod-global-constants. Anyways, here we go: Active Reactors: getHotFluidProducedLastTick getHotFluidAmount getHotFluidAmountMax getFuelTemperature getFuelAmount getFuelAmountMax getFuelConsumedLastTick Passive Reactors: getEnergyProducedLastTick getEnergyStored getEnergyStoredMax (That's a mod constant right now but this should be included in case you want to change this at some point)
-
Ok here's my verdict: Since the yield bug we discovered in november is STILL not fixed, my guess is that any anomalies you see is because of that! The controller needs to fetch a bunch of stats from the reactor during the same tick, which is no longer possible due to that bug. This throws off the controller and it can't properly calibrate your reactor. I'm sorry but there is nothing I can do except saying: Early versions of ER for 1.10 still work. 1.7.10 works as well. Later versions of 1.10, all versions for 1.11 and all versions up to today for 1.12 are not supported. Don't bu
-
@afr33sl4ve I just tried to build the reactor in your schematics and it tells me it's too large. Can you double-check the dimensions of your schematics? The dimensions you put in there are for the reactor interiour. So the total size of your reactor schematics is 18x18x48
-
Since you are using mekanism: The next version will have support for mekanisms energy storage thingy btw.
- 852 replies
-
- 1
-
-
- gui
- controller
- (and 2 more)
-
Actually Additions fluid placers help ;)... I can't believe I came up with that only just now....things could've been so much easier, lol
-
That's going to take a while to build xD I'll get to it tomorrow EDIT: BTW - Could it be that you swapped cryotheum and ender around? Cause ender is good on the outside while cryotheum is better inbetween rods afaik
-
@hron84 I think I'll make it so it hides the "Reactor" and "Turbines" buttons on lower resolutions.. that should do the trick. Thanks for the TE cell thingy. @afr33sl4ve I need a way to rebuild your reactor in my test world so a schematic would be nice.
-
@dsplzion What version of draconic evolution are you on?
-
Hey guys, @afr33sl4ve I need some more info on your setup in order to figure out what's going on here. @hron84 I have to admit I've only ever tested the GUI with T3 screens. If the resulution doesn't stack with multiple screens, then yes, ever since I introduced the grid controller, you'll need T3 screens
-
Hi @afr33sl4ve. You can hit the "CHARGE" button that's in the "Grid" GUI. That'll instruct the controller to fill up the energy storage. The behaviour you're seeing is improving overall efficiency of your power-gen. I don't think there's an issue unless you're running into out-of-power situations due to this - In which case I need to come up with something.
-
@ClownApocalypse If you've actually done everything correctly, then I'll have to take a look whether the API changed or not - though I don't think it did. "Connection Failure" means exactly what you might think it means: It can't contact one of the components. Please double-check whatever you did with https://tenyx.de/draconic_control/. ESPECIALLY the configuration part. Please make sure there is no typo in the keys as well. Also please try to reboot your computer (although I'm pretty sure you already tried that ).
-
I'm pretty sure this program is also pretty slow, however, since there's not much interaction, you won't notice anything. The cycle time of that program seems to be one second. If the screen doesn't refresh every second, you're expieriencing the same issues. But since this program only turns on and off turbines/reactors, without actually regulating the components themselves, it works mostly fine. And the only user-interaction you have is shutting down the entire thing.... so.. yeah ^^
-
Hi @MetalKluG, you might've double checked the addresses, but you didn't do that for the "variable" names Looks like you misspelled "fluxGateDrainbackAddress"
-
Hi @Gravydigger, this looks like your installer download broke. Please remove it (rm brgc_installer.lua) and get it again.