"Set position to" isn't quite working...

0 favourites
  • 5 posts
  • Here's my cap:

    db.tt/61FvHuSV

    I had a camera system, but disabled it so one thing would become obvious: whenever you enter a new animation (or not -- see edit at the bottom), the sprite assigned to the invisible platform object teleports to 0,0 for a single tick. That little number in the top left increments every time the sprite's X is less than 20 -- if you walk around for a few seconds, you'll see it go up pretty quick.

    The thing is, it WON'T increment if you're testing the actual platform object's X value, meaning the problem must lie within the event setting the sprite's position to the object. It's a simple "Every tick" event, and absolutely no where else do I change the sprite's position. I'm led to believe it might be a bug or something, but I can't be sure.

    EDIT: I disabled ALL the event sheets other than 1-1 and Mario and the problem persists, so you don't have to look in any others. Actually, I just disabled all the animations and it STILL happens, so the problem isn't even in changing animations. I'm stumped.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Where are the relevant events? It is very confusing for other people to try and find their way around unfamiliar projects.

    My first instinct is that everything is working correctly but your events are set up so it takes one tick for the object's position to be updated.

  • Right, sorry -- Mario's Set position to event is the second event of the Mario event sheet, I think. If you mean something else I might have to go check.

    Even if it was taking too long to update... why would it teleport to 0,0? Wouldn't it just stay where it was for an extra tick until it can update properly? It's a simple "Every tick" event, so I don't see what else could be keeping it from updating. <img src="smileys/smiley5.gif" border="0" align="middle" />

  • Ah, this turned out to be a really weird bug. It's fixed in the next build. Thanks for the find!

  • Hah, sweet. Thank YOU for the fix! I'll await the next release with baited breath!

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)