Request: ARAY tmp -> BRAY lifetime

  • cip
    5th Feb 2012 Member 6 Permalink
    Suggestion: ARAY tmp value becomes the inital lifetime of short-life BRAYs it creates. Setting tmp to 0 or less uses default BRAY life of 30, leaving existing saves unaffected. No imposed maximum value. No effect on solid or brown BRAYs.

    I believe there is a solid argument for this. ARAY is useful in small, fast electronics because it can carry a signal through or adjacent to many other electronic elements without affecting them, and because it can instantly and simultaneously activate multiple electronic elements. However, throughput is often bottlenecked by BRAY fade time. Allowing shorter BRAY lifetimes will allow for small, low-latency circuits with considerably higher throughput.

    FILT/INWR may be used for fast recharge times, but this solution is not possible in circuits that rely on solid BRAYs, such as ARAY RAM and ARAY/FILT or ARAY/INWR ROMs (since FILT and INWR prevent solid BRAYs). This solution is also not currently reliable in general because of a glitch that complicates the use of SWCH in FILT lines, which is described here.

    This will add many possibilities for fast electronics, and, to my knowledge, won't break existing saves either. 

    -C
  • therocketeer
    5th Feb 2012 Member 0 Permalink
    @cip (View Post)
    very good idea. This adds yet another dimension to ARAY technology, I fully support this. And the best thing is, no saves would be broken =D
  • Darkyhard
    5th Feb 2012 Member 0 Permalink
    Well, what if the temperature will be negative? Also, it still could break some saves, or at least it WILL have effect on it. My alien gun has ARAY pointer that heats to crazy temperatures. This would make the beam to stay forever,
  • vanquish349
    5th Feb 2012 Member 0 Permalink
    @Darkyhard (View Post)
    tmp is not the same as temp. tmp stands for temporary and temp stands for temperature. tmp is a variable that elements use to store data in. so it most likely wont break saves
  • Darkyhard
    5th Feb 2012 Member 0 Permalink
    How do we set it then? I tried to set WATR's tmp to 2, but nothing really happened.
  • lillepallt
    5th Feb 2012 Member 0 Permalink
    @Darkyhard (View Post)
    using console/property tool, i dun think water got any useful tmp variable but filt, dlay and wifi does .__.

    On topic, this is a great idea :D, it's like a new form of electronic logics beyond real life.
  • Demoman200
    5th Feb 2012 Member 0 Permalink
    that sounds like a great idea. won't break any saves, allows for super-fast aray shooting, or even bray bridges that stay forever! +1!
  • dooperwt
    29th Jun 2012 Banned 0 Permalink
    This post is hidden because the user is banned
  • boxmein
    29th Jun 2012 Former Staff 0 Permalink
    @dooperwt (View Post)
    TMP, not temp.

    Every particle has some "variables" bound to it, so it would use them in simulation.
    Type - tells what particle it is
    Ctype - tells clones what particle to clone, other stuff with other elements
    Life - tells how many updates the particle will "live", used in various contexts
    Tmp - used for various purposes, represents particle "mode" for FILT
    Tmp2 - second Tmp, if one isn't enough
    Temp - temperature ( heat ) of particle.
    @cip (View Post)
    I wholeheartedly agree. That's a splendid idea. Though tmp=0 should default to the value regular BRAY has now. Red BRAY has a life of 2, btw.
  • Raphi
    29th Jun 2012 Member 0 Permalink

    Very very extrem super cool idea!

     

    I work much with aray and this could make electronics so much faster!