blackhornet's Forum Posts

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

  • 2 Jun, 2020
  • Quote

  Sorry, I've come late to the party. So what isn't working in your example?

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

  • 2 Jun, 2020
  • Quote

  Can you use another file service? 4shared wants to change notifications in my OS, and I'm not going to let it do that! Dropbox is the safe standard.

  .

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

  • 1 Jun, 2020
  • Quote

  Yes, that's the flow to follow. I can't answer what the errors could be. The thing to keep in mind is that this all takes time, so you want to be sure you block the user from doing anything before you get "On leaderboard displayed". You would use that event (and error) to unblock the user (if that's appropriate).

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

  • 1 Jun, 2020
  • Quote

  The 'On' triggers should always be at the top level of the event sheet. You don't want them 'under' the calling event. That's what makes this async. You make the call, then outside you add success and fail triggers, and keep going from there. You should have six individual triggers, a success and fail for each of the three calls you make.

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

  • 1 Jun, 2020
  • Quote

  fredriksthlm is correct. You are not calling the interface correctly. All of those calls are asynchronous, which means you have to wait for the trigger to occur before proceeding. If it worked before, then you just got lucky, but given that you have a second authenticate 'in case the first one fails' implies that you have had issues before, and 'fixed' it with a second call. That's not the fix.

  You may need to alter your code to block events while the async calls run.

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

  • 31 May, 2020
  • Quote

  The range is 0 to 4, so you want: floor(min(x,99)/20)

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

  • 31 May, 2020
  • Quote

  You can use a Timer that toggles visibility, and just have it start and stop based on input, with the added step of making the muzzle flash invisible, just to make sure, when you stop.

• You do not have permission to view this post

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

  • 28 May, 2020
  • Quote

  Works for me too. Not all keyboards are designed the same, and they are not designed to be game controllers. There are only so many keys you can hold down at the same time, before it just doesn't work. You will find other threads discussing this. You should reconsider your interface.

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

  • 28 May, 2020
  • Quote

  http://www.blackhornettechnologies.com/Construct2Stuff/Samples/LockTimer_lukezero.zip

  See if this helps. I can explain details, but see if this is what you want first.

• 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

  • 28 May, 2020
  • Quote

  If you can isolate out just the door mechanism, I can help sort it out. Timer is much more versatile than the system events.

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

  • 27 May, 2020
  • Quote

  You can't/shouldn't use Every X seconds, or Wait in a function. Use the Timer behavior.

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

  • 24 May, 2020
  • Quote

  For each fixes this.

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

  • 23 May, 2020
  • Quote

  zeropad(floor(timer/60 % 60),2) & ":" & zeropad(floor(timer% 60),2)

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

  • 21 May, 2020
  • Quote

  Don't break up the logic. Check for On tap first, and then use sub events to check "Pause" Else "Play".