blackhornet's Forum Posts

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 19 Apr, 2014
  • Quote

  The problem is you have a white background and can't see the relative movement. Put any tiled background in behind and you'll see that it is working.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 19 Apr, 2014
  • Quote

  Because you can't see that it is scrolling. If the background had been there, you would have seen what was going on immediately.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 19 Apr, 2014
  • Quote

  It's because you have ScrollTo but no background as reference (and your platform/floor is on the HUD layer). Place a tiled background in behind and you'll see what's going on.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 17 Apr, 2014
  • Quote

  The bullet can not be guaranteed to be pixel perfect. Bullets move X pixels per tick. If that rate is 'fast', the collision will not happen at the wall edge. This has been discussed on other threads.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 16 Apr, 2014
  • Quote

  The problem is you are getting multiple collisions per Nondestsolid. Not sure why, but adding an extra flag to indicate when the collision has already been processed seems to fix the problem.

  Edit: actually I think it may be because you change the animation to "land". This then resets the collision property, and it 'collides' again. That makes some sense to me.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 16 Apr, 2014
  • Quote

  Just restart the timer in the 'On timer' event.

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 16 Apr, 2014
  • Quote

  It may be a r166 bug. I reported a problem with functions being called twice. I don't see the problem you are describing, but I'm at r167 already.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 16 Apr, 2014
  • Quote

  BRaxe:

  Mirror the axe

  Set Rotate speed -200

  Set Rotate acceleration -100

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 16 Apr, 2014
  • Quote

  Use the Timer behaviour rather than Every X second. You have complete control over it.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 15 Apr, 2014
  • Quote

  Look at the Timer behaviour.

  https://www.scirra.com/manual/167/timer

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 15 Apr, 2014
  • Quote

  Got it! The problem is, by using Move at angle, you are not guaranteed nice integer Player position values. If you dump the player coordinate, you see they are not always even multiples of 32. As a quick fix, do:

  Every tick -> Set Player position to round(Player.X), round(Player.Y)

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 15 Apr, 2014
  • Quote

  My suggestion would be to add some logging. Use Browser.Log to dump out your moves and even the map so you can see the data change. The problem will probably pop right out once you can see the data easily.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 15 Apr, 2014
  • Quote

  A temporary local variable.

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 15 Apr, 2014
  • Quote

  Just store that fact that the 'clearabove' flag has been set (local variable), then rather than trying to further pick below that point, you need to move back up a level and pick the non-'clearabove' blocks and then set the 'clearabove' flag.

  So,

  Pick overlaps

  ->Pick with 'clearabove'

  -->Set temp = true

  ->If temp=true

  -->Pick not 'clearabove'

  --->foreach

  ---->set'clearabove'

• • blackhornet
  • 
  • • Joined 28 May, 2012
    • 
    • 57 topics • 4,431 posts
  • 1

  • 15 Apr, 2014
  • Quote

  Then you'll have to post your CAPX, as it should work.