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

XyFreak

Members
  • Content Count

    400
  • Joined

  • Last visited

  • Days Won

    32

Posts posted by XyFreak

  1. @payonel The uuid library appears to be accessing bit32, which for whatever reason has not been defined. See here:

     YusLKt8.png

    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...

  2. @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 :P

    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 :P

  3. 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.

  4. 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 :P

    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.

  5. @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.

  6. 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.

  7. 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.....

  8. Big Reactors Grid Control Version 4.2.8 has been released!

    Changelog:

     - Use threads/coroutines for heavy calculations on calibration data. This'll fix the "too long without yielding" errors.
     - Hopefully fixed an issue where the controller gets confused by the massive internal energy storage of draconic evolutions energy relays.
    
    NOTE: If you see errors regarding the controller not being able to find "thread" you'll have to upgrade your OpenOS!

    If you're upgrading, you'll have to re-download the installer because it is now fetching an additional package!

  9. Ok guys I have a working solution in the pipeline... It might break old OpenOS instances though so you better be prepared to upgrade that / reinstall the computer ;)

    I'll see if i can squeeze in another smaller bugfix as well so stay tuned - fix should be out either in an hour or tomorrow :P

×
×
  • Create New...

Important Information

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