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

XyFreak

Members
  • Content Count

    380
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by XyFreak

  1. Yes, definitely. Right now 1.12 is propably the most important version... I guess.
  2. @payonel I figured I can do that after seeing your commit. I'm debating whether I actually want to include hacks affecting _G in BRGC tho..... maybe I will just to avoid this issue coming up more and more.... tough call ^^ thanks tho EDIT: It's done, I put it in my "promise" library (where uuid is used)
  3. @payonel sweet I'm glad we're finding real issues now and not just me being supid / jumpy
  4. Ok the issue has been fixed @Dreytac @sanovskiy, sorry for missing that... that was stupid of me...
  5. @payonel The uuid library appears to be accessing bit32, which for whatever reason has not been defined. See here: EDIT: please note that I can NOT reproduce this with version 1.7.1.43 EDIT2: I took a quick look and it appears bit32 has been removed from lua 5.3, so uuid will work in lua 5.2 mode but not 5.3...
  6. @sanovskiy I also found the issue thanks to @Dreytacs screenshot. I feel stupid now. My linter even warned me about this... gonna be fixed in a few minutes EDIT: NVM the "few minutes" part, my test world no longer loads...
  7. @Moobien Looks like you ran into an OpenOS bug. Please report it to the OpenComputer guys One COULD do that but i won't. For now. @SpaceBeeGaming That's good to hear
  8. @ZeroNoRyouki awesome! thanks @Moobien yeah i'm looking for the issue in screenshot 2. However you ran brgc_gui there which lowered the screens resolution so i can't see the top of the stack trace, which is what i actually need :P. I assure you the error should pop up even without running the GUI so...i need a screenshot for that However I think your explanation gave me a hint to what's going on.... shouldn't happen but might. Lemme take a look. Still, I'd really like a screenshot where brgc_gui never ran / was terminated before the issue occurred
  9. Ok I just ninja updated BRGC. It's now using the new API but can still use the old one. If one or two ppl could confirm that stuff is still working for you that'd be great. I've also tried to make the "too long without yielding" issue less likely to occur so... there's that. Without knowing what exactly is causing https://i.imgur.com/1eV8hJj.png don't actually want to call it RELEASE! time yet tho.
  10. @Moobien can you please run BRGC without the GUI so you can screenshot the full error? That'd really help. Thanks
  11. I feel like i fixed that one eons ago. What LUA version is your OC CPU set to? It should work with both but...you know.... EDIT: the format one. The third one is something else
  12. Hey @m_2018 The default presets take quite a while to get going. What's "slowing you down" is the energy saturation target. As you can see, it's kept at a constant 50%. As fuel conversion increases, energy generation increases as well so that's where the gain in energy generation comes from. You can set the saturation target to something lower (without touching the throttling) to speed everything up if you want. The default presets are only meant for making sure everything is fine tbh ... i thought more ppl would jump on the maxrf/t train EDIT: If you don't want to mess with any setting and just throw in a number, use 25% for the target saturation. That'll get things going a lot faster.
  13. @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.
  14. Since the threads library didn't really do the thing I expected it to do I'll remove the dependency on that sooner or later. I'm not at home right now tho and thus won't be able to update anything for the next week.
  15. Are you kidding me? The thread API is supposed to not have that problem! And that right there is running in a thread.... You're on 1.7.10, right?
  16. 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.....
  17. 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.
  18. @xBlizzDevious Induction matrices are already supported 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.
  19. Please redownload the installer. It has changed since the last release. The version you have doesn't download the "promise" package
  20. @SpaceBeeGaming Nothing that can't be solved by some abstraction I can just check for the presence of certain functions and then use them if they're available. No big deal.
  21. Your computer propably doesn't have enough RAM to process the br_grid_control package.
  22. Nice^^ 1.02 drainback is not safe for servers tho but even getting that up to 1.05 or even 1.1 won't really reduce the numbers that much.
  23. @Aquila_chrysaetos The link itself was wrong so i fixed that. You'll have to use the link from the page. Also your browser might've cached the page so try to do a force refresh (SHIFT + F5 i think?). https://tenyx.de/draconic_control/draconic_simulator_64.exe (spot the difference :P)
×
×
  • Create New...

Important Information

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