Official Game Feedback

  • arK
    9th Mar 2014 Member 0 Permalink

    Current development snapshot is a mess

    fix numpad behavior - didn't fix anything, numpad is still broken

    lots of random fixes to the legacy lua api - probably introduced a bug, sim.set_property doesn't work

  • mniip
    9th Mar 2014 Developer 0 Permalink
    @arK (View Post)
    Numpad works fine here. Did you actually include the commit when fetching?
  • jacob1
    9th Mar 2014 Developer 0 Permalink
    @arK (View Post)
    In what way is it broken? I tested a lot of cases of tpt.set_property and they all still worked. Did you use sim. instead of tpt.? Because there is no sim.set_property.
  • arK
    9th Mar 2014 Member 0 Permalink

    @mniip (View Post)

     Yes, obviously.

     

    @jacob1 (View Post)

     Yep, tpt.set_property, just a typo. Index mode doesn't work: tpt.set_property('temp', 999, 1) does nothing to particle with ID 1. It works fine with x, y and w, h.

     

    UPD: huh, I guess tpt.set_property(string property, object value, string type) is also broken.

    tpt.set_property('temp', 999, 'CRAY') yeilds: console:1: bad argument #3 to 'set_property' (number expected, got string)

    Edited 2 times by arK. Last: 9th Mar 2014
  • jacob1
    9th Mar 2014 Developer 0 Permalink
    @arK (View Post)
    odd, but jacksonmj found what broke it. I must have tested it, then only after changed those few lines. Fixing it now.

    Edit: fixed now
    Edited once by jacob1. Last: 9th Mar 2014
  • arK
    9th Mar 2014 Member 0 Permalink

    Since I'm here, I might as well make a couple requests ^__^

     

    Being able to access FPS counter would be very nice. Something like: tpt.fps, sim.fps, sim.getFps(), whatever...

     

    Writable tpt.selectedl, tpt.selectedr and tpt.selecteda:

    tpt.selectedl = elem.DEFAULT_PT_CRAY -- change LMB element to CRAY

  • Schneumer
    9th Mar 2014 Member 0 Permalink

    @arK (View Post)

     you can set the fps cap, but I forgot how to.

  • jacob1
    9th Mar 2014 Developer 1 Permalink
    @arK (View Post)
    the fps counter can be easily calulated using os.time() or (much more accurate) socket.gettime(). I guess it's up to you to figure out exactly how. We could always add a function, but me, cracker64, and mniip always got around it :|

    As for setting tpt.selectedl, I guess I just sometimes forget that we don't have a way to set something as basic as that. I'll try to add it eventually, but I think I convinced Simon to update the game to a new release right now.
  • arK
    9th Mar 2014 Member 0 Permalink

    @Schneumer (View Post)

     tpt.setfpscap(100500) -- I want to know the actual FPS, not the cap.

     

    @jacob1 (View Post)

     > using os.time()

    Yeah... tpt.register_step, count frames and reset every second, I already did that. But there is no point! TPT knows the FPS, why should I count it again? That's redundant and wasteful.

     

    > I guess I just sometimes forget that..

    > I'll try to add it eventually

    Yes, eventually.

     

    > I convinced Simon to update the game to a new release right now.

    With broken numpad? Are you kidding me?

    Edited once by arK. Last: 9th Mar 2014
  • jacob1
    9th Mar 2014 Developer 0 Permalink
    @arK (View Post)
    what's broken about numpad? I don't have a numpad, and mniip told me it was fixed, so I told Simon all the bugs were fixed.

    doing fps manually is a little wasteful, but at least it works :P. It's not going to slow down your script much at all.
Locked by jacob1: Old / not enough space in first post