Tokinsom's Recent Forum Activity

  • +9999

    The player in one of my projects has 200+ frames, 2 parts, and 3 image points. For the love of god, please add this!

  • Project files, server, XML, CSV, JSON (array, dictionary, etc). Take your pick :) There is info on all of this in the manual.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Bump.

  • Er..Pretty sure you'd get the same results in CC or anything else. 1 particle per tick simply isn't enough for a seamless trail.

  • Using every tick or 0.01 seconds or w/e doesn't spawn particles fast enough to make a seamless trail. I use the loop (which also moves the beam for pixel-perfect collisions) to spawn the particles at a very high rate and that's where the problem lies. For the record they are destroyed shortly after so there's never more than ~20 particles per beam.

    I tried giving each beam a variable that is subtracted by n*dt and creates a particle / resets itself each time it goes below 0. It helps but I still get about twice the particles at 0.1 time scale..

  • I'm using a for loop to create a seamless beam trail / laser similar to this with small particles. Works great but the lower the time scale is, the more particles that are spawned. I can't just use every tick or milliseconds because they don't spawn the particles fast enough to make the trail seamless so..any ideas?

    Here is a .capx.

  • I was actually going to suggest this but using a dedicated object for layout variables works just as well o.o

  • If you save as a project folder you can overwrite the project files outside of C2. They must first be added in C2 though. Not the best system..

  • Other side of the country :\</p>

  • Yep. To add to the score you can set the key to itself + a number. Alternatively you can store data in a dictionary or array since it's more manageable, and then save the whole thing to a webstorage key.

  • This bug is a side effect of the fix that was made in r120 in response to my "Platform Behavior Bug (Gliding over platforms)" report. I believe it's lines 596-570 or somewhere around there that causes it. I removed them so I can't check without re-installing.

  • +1 Same goes for moving an event below another event that has sub events; it just becomes another sub event!

Tokinsom's avatar

Tokinsom

Member since 6 Jun, 2010

Twitter
Tokinsom has 11 followers

Connect with Tokinsom

Trophy Case

  • 14-Year Club
  • Entrepreneur Sold something in the asset store
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • RTFM Read the fabulous manual
  • Email Verified

Progress

20/44
How to earn trophies