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

Big Reactors Grid Control

Recommended Posts

Hey XyFreak. I'm back!

Used to use this program a good while ago and then went away from Minecraft. I'm back now and still very grateful that you wrote this excellent piece of software.



Now my questions are:
Any chance of Mekanism Induction Matrix support?
How does the software handle a turbine connected that isn't supported by an active reactor? I've connected mine and it's started it up so seems good but I've only just connected it. I've got a reactor connected as well - but it's passive. I'm producing steam for the turbine with compression dynamos with specialisations and augments because they're daaamn OP.

Link to post
Share on other sites
4 hours ago, XyFreak said:

@xBlizzDevious

Induction matrices are already supported :P I haven't tested your steam thingy. It might work as long as you don't use active reactors at all. Just try it out.

Yeah, with just my passive reactor and the turbine connected, it would try and slow the turbine and leave the reactor at full (I had the turbine on independent, so that probably caused that).

I just added my Induction Matrix to the network and it runs perfectly. My turbine span up to full speed and my reactor is running at optimal.

Note: you should probably update the documentation to say that it works with induction matrices as it wasn't on your list so I just thought it wouldn't work.
"Currently EnderIO Capacitors (requires the mod Computronics), Draconic Evolution Energy Storage and RFTools Power Cells are supported."


EDIT: Just noticed an error with the program. Well, more a hardcoded number than should read variables - if possible.
I'm playing All The Mods 3 and in this pack, they've changed the ratios for energy conversion. Your program is saying that my induction matrix stores ~1.4TRF but it's actually only capable of storing 448GRF. The output (weighted) figure is also wrong, saying about 230kRF/t when it's actually about 170kRF/t (according to the matrix itself).

Link to post
Share on other sites
Just now, XyFreak said:

Yeah that's definitely because you activated indipendent-mode. It makes it so the grid controller ignores the turbine and lets it do its thing.

I updated the description. Thanks for reminding me.

I realised it would be the case as I was typing it!

No problem. Did you see my edit of the previous post?

Link to post
Share on other sites

I know about that issue with ATM3. There's nothing I can do though. You can go into /usr/lib/brgc/energy_storage_componen.lua and change the ratio to 0.15 yourself. There're a lot of ways you can break BRGC by changing default configurations (e.g. you can change the ammount of steam a turbine blade can pick up) and there's no way for me to fix that because I can't read those configs ;).

 

EDIT:

I could make everything globally configurable tho... I'll have to think about that.....

Link to post
Share on other sites
Just now, XyFreak said:

I know about that issue with ATM3. There's nothing I can do though. You can go into /usr/lib/brgc/energy_storage_componen.lua and change the ratio to 0.15 yourself. There're a lot of ways you can break BRGC by changing default configurations (e.g. you can change the ammount of steam a turbine blade can pick up) and there's no way for me to fix that because I can't read those configs ;).

Yeah, I figured as much. I was hoping it could be read, though. Maybe have a config file with options that could be changed in the mod settings? Thanks for the quick reply!

Link to post
Share on other sites

Okay, now there is another crash:

[promise 381e6912-539f-5825-cbad-a79499c3c4c9] too long without yielding
stack traceback:
	/usr/lib/promise.lua:37: in function 'on_failure'
    /usr/lib/promise.lua:52: in function </usr/lib/promise.lua:50>
    (...tail calls...)
    [C]: in function 'error'
    machine:11: in function <machine:4>
    /usr/lib/matrix.lua:76: in fuction 'get'
    /usr/lib/matrix.lua:127: in fuction 'mult'
    /usr/lib/polynomial_interpolator.lua:14: in function 'QRstep'
    /usr/lib/polynomial_interpolator.lua:56: in function 'interpolate'
    /usr/lib/brgc/reactor_passive.lua:137: in function </usr/lib/brgc/rector_passive.lua:134>
    [C]: in function 'xpcall'
    machine:751: in function 'xpcall'
    /usr/lib/promise.lua:50:in function </usr/lib/promise.lua:49>

 

Link to post
Share on other sites
On 2/23/2018 at 3:50 PM, XyFreak said:

Big Reactors Grid Control Version 4.2.8 has been released!

 


NOTE: If you see errors regarding the controller not being able to find "thread" you'll have to upgrade your OpenOS!

 

Is there an easy way to instill an older version. I'm playing on a server running a 1.7.10 pack and don't see the pack upgrading OpenComputers anytime soon.

Link to post
Share on other sites
13 hours ago, Molinko said:

@RGB_Leader, XyFreak is referring to OpenOS, the open source OS of Opencomputers. Not the mod or mod pack. You can find it on GitHub.

 

13 minutes ago, BrisingrAerowing said:

@Molinko That's not what he meant. He wants to install an older version of BRGC, as the pack he is on doesn't have an OC version with the thread library, and isn't likely to update OC.

Sorry for not making that clearer. The pack I'm on is running version 1.6.2.12 of OC. I'm not sure if it would have the correct library or not. Any suggestions on what I can do?

Edited by RGB_Leader
Wording
Link to post
Share on other sites

@RGB_Leader You can try this program from the forums by @Nexarius. You can download it from pastebin or github using an internet card and the pastebin or wget program. This has worked for me in the past although I cant speak as to how far back compatibility will be possible. Anywho, it's worth a shot as I have had similar issues before with a version of OpenOS not having the thread library and this worked great for me. Good luck :) 

Link to post
Share on other sites

@RGB_Leader Or you could just update OpenComputers. Just download the latest version from Curse: https://www.curseforge.com/minecraft/mc-mods/opencomputers/download/2508602 (this is a direct link to the latest OpenComputers for Mc 1.7.10)

and replace the old one in the mods folder of your pack. (assuming you are playing in single player).

Link to post
Share on other sites

Guys, please be careful with OpenOS-updater as it's - as far as I know - doesn't take care about MC and OC compatibility. I tried several times to update OpenOS and sometimes my computer was wrecked up. It works when certain conditions met, but before you do that, craft a test computer before (even a t1-t2 enough) and test it to not tear down the machine that responsible for the power supply of your whole base. 

Link to post
Share on other sites

@payonel Well the way the docs are worded / i understood them the thread API would take care of yielding / resuming. But it doesn't do that / can't do that. You still have to yield yourself (with os.sleep). I know this was a misconception on my part ;)

And looking at the LUA C API everything makes sense: you can't interrupt the LUA VM without terminating the current context. Now... since I'm doing matrix operations here I can't just put sleeps everywhere and call it a day: it'd litterally take ages to complete so my only hope is that I can do at least one interpolation op per timeslice so the program won't run into "too long without yielding" issues.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

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