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

SashaGelert

Members
  • Content Count

    11
  • Joined

  • Last visited

Posts posted by SashaGelert

  1. Could someone give a better explanation of this GUI, preferably with some screen shots?  since the Wiki tends to me lacking in user tutorials?

     

    Specifically: why can i draw two lines from each server to the case, does this allow multiple connections per side?

     

    and a personal, possibly related issue: Server 1 has power, but servers 2-4 wont boot, claiming they have no power, is this related?

  2. not bad.  apart from some much needed code-rearranging (drove me nuts reading Vex's original code) you just nerfed the reactor calibration for your own function, yay simple :)  Seems you still dont have it checking your EIO cap bank yet though.

     

    for myself, custom modpack 1.7.10 forge 1614, because it still has all the best mods!

     

    I just tore apart XyFreaks BRGC, which is a nice beginning point for a Gui, but his reactor controller could use a few more features for my liking.  

    https://oc.cil.li/index.php?/topic/918-big-reactors-grid-control/?hl=reactors

  3. This is a project I've been meaning to undertake for a few weeks now, then couple days ago i found a loophole in EnderIO Photo-voltaic Panels that turns everything into OP energy :-) BUT! it never hurts to have a project to work on, so still dabbling with this in my free time.

     

    Couple of questions though:

     

    Turbine Questions:

    --What Size? (outer shell dimensions please)

    --Coil block count?

    --Coil block type?

    --How are you routing steam between reactor/turbines (specifically which mod set of pipes, or direct contact?)?

     

    General Questions:

    --What Minecraft/Forge/Mod versions are you working with?

    --Don't you need a second graphics card to use both screens at once? or did i miss a recent change?

    --Does it need to be on two screens, or would one be acceptable, perhaps able to switch between a 'summary' and a 'detail' view of the system?

  4. The issue is that Ender IO is *NOT* a bundled cable, each end connector is ONE color, thus ONE signal, not bundled like ProjectRed, or the older RedPower2.  It is the fault of Ender IO, not Open Computers that there is no support for such a feature as this.  

     

    best solution I've been able to build for this is to use framed bundled cables from Project Red to build a sort of 'Bridge' between the two systems.

     

    dec092c7fe.png

     

    Absolutely let us know if you can find a better or more compact solution!

  5. I have to question the need for this based on your example?  If white turns on, turn black on, logically if white turns off you want black off right?  why not just connect the two colors with a bare piece of wire or such?  could you give us a bit more detail?

     

    --Are you looking for direct, manual control of the wires if needed?
    --Are you looking to monitor the wires via screens?

    --Do you intend to use this on a tier 1, 2, or 3 computer system (and corresponding screen?)

  6. I... I am curious as to why someone would put such effort into a custom OS, just to abandon the project because the community as a whole hasn't indulged in it!  It is still a very worthwhile project and would help many others trying to do this for their first time, especially as when one looks over the Wiki, most every page could do with a proper dedicated tutorial.

  7. First off, Love how compact this bios is, I've spent the last three days trying to reduce the event API into something a microcontroller can implement, and this does it wonderfully!  however, a few notable issues I've found:

     

    Hello!

    Thanks for the BIOS. For me, it has a problem:

    I have a drone with skex.

    I connect to it, using client.lua, then disconnect with ctrl-alt-c. If I do it this way, all the output from my drone would be doubled for every next client.

    Tested it little bit:

    http://i.imgur.com/QwZjd8n.png

    :)

     

     

    The reason this happening is actually In the client. The client calls event.listen to register a handler and when you quit the program like that then the program doesn't finish executing and thus can't unregister the handler.

     

    This is still a valid issue in skexBIOS 0.1.2 with client 1.0:  while the client listens for a 'quit' message from the microcontroller... this message is never sent, the microcontroller's method of shutting off is to simply brick itself

    local run = true
    [...]
    while run do
      local cmdt = splitonspace(read())
      if cmdt[1] == 'q' then
        run = false
      elseif
      [...]
      end
    end
    
    
    

    Nothing occurs after the microcontroller shuts down, nothing is sent back to the client letting it know to stop the listener or close the modem port.

     

    I'm also surprised the files aren't up on a dedicated pastebin or github for the current version, since even though we can download from the homepage. most people are likely to submit to pastebin in order to import them into their minecraft world anyway.

     

    There are a few other adjustments that could be made to the programs, especially client side, so definitely looking forward to the next version (if i don't make my own before then :P )

×
×
  • Create New...

Important Information

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