post bugs here by jacob1

jacob1

189 / 28

29th Sep 2012

16th Mar 2014

Post any bugs you find here. But there aren't as many bugs that are really bugs and I don't already know about than when this first started, so also use this as a general conversation save, or to ask / tell me anything. #1 most commented save in tpt!

problems jacob1 bugreport glitch fix 960847 tptpp bugs tptplusplus glitches

Comments

• 

  QuanTech 8th Sep 2017
  @catmaster did you set the DTEC's ctype to PHOT? Is the PHOT farther away from the DTEC in pixels than the DTEC's tmp2?
• 

  catmaster 8th Sep 2017
  idk... for me dtec not detect phot
• 

  Tron205 8th Sep 2017
  Jacob. Can you make lua consoole in tpt less buggy? And make a proper script editor for it, because im tired of doing dofile() all the time.
• 

  jacob1 7th Sep 2017
  I would use sim.partProperty(i, "type") to get the type of a particle by ID
• 

  jacob1 7th Sep 2017
  It is strongly recommended to not use tpt.parts for anything besides quick lua commands. Definitely don't use it in the update function of an element. It's far slower than sim.partProperty or tpt.get_property. It's just left in because it's very easy to use
• 

  QuanTech 6th Sep 2017
  tpt.parts is an array that contains particle data. You can use the iterator from sim.parts() to print out the x and y coordinates, like: for i in sim.parts() do print(tpt.parts[i]["x"],tpt.parts[i]["y"])
• 

  Tron205 6th Sep 2017
  How do i find a particle on screen by ID?
• 

  Atomic10 6th Sep 2017
  Isn't the illuminati symbol's code "163" or something?
• 

  jacob1 6th Sep 2017
  Tron205: i is the ID of a particle that exists somewhere on the screen. Do whatever you want with it (check the type, change a property, whatever)
• 

  Tron205 5th Sep 2017
  for i in sim.parts() do print(i) end; -- What do i do with "i"? Is there a table that contains all current particles.