emoaeden's Forum Posts

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 25 Feb, 2016
  • Quote

  You should disable default keys too when doing this.

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 25 Feb, 2016
  • Quote

  Like This ?

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 23 Feb, 2016
  • Quote

  It is pretty simple, and here is a CAPX to help you out.

  Sound Game

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 23 Feb, 2016
  • Quote

  I have a few examples I've done over the years, but you should try this one.

  Inventory, using an array and no mouse

  Keys are Up Down Left Right, no W A S D.

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 23 Feb, 2016
  • Quote

  Post a CAPX and I'll give it a shot

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 18 Feb, 2016
  • Quote

  This is a quick and messy version. Realistically you should put in code to check if you are using a touch device or mouse device.

  Ta da !

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  You guys are awesome ! Yep that is indeed the issue. I think it's 'cause I'm calling a function which calls another function, which then calls itself.

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  zenox98 Really ? 'cause here's the full CAPX and it is as slow as a dog on both my PC and mobile.

  Link

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  Ummmm, will this help you at all ?

  Fingers Crossed

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  I like to use the following formula

  20*log10((VolumeSFX/10)*(VolumeMaster/10))

  Where VolumeSFX is for game sound effects and VolumeMaster is for the master game volume.

  You can also use the following for game music.

  20*log10((VolumeMusic/10)*(VolumeMaster/10))

  Let it also be noted, that VolumeMaster is a variable that is changeable, as is VolumeSFX or VolumeMusic. I like using a slider or (+) or (-) buttons, instead of just inputting the value.

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  Try having it set the box.angle to touch.angle might not do the job properly, but will introduce you to using the .angle property.

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  This should do the job, albeit will be messy when it lands, but it does what you have asked. To clean up the bricks and such, you will need to sort that out for yourself.

  Have Fun !

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  Kyatric and is Asmodean are both correct.

  Ceil() is great for rounding up integers while floor() is great to round down integers.

  Take your value x and use (floor(x*100)/100), granted round will do the same in this example; but floor is better for if the number has lots of decimals.

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 16 Feb, 2016
  • Quote

  So I have something beautifully coded (which I have removed in the attached CAPX), but it is just ridiculously slow.

  As it stands, it shows it uses 75-95% of the CPU (according to the debug window)

  Any idea where I have stuffed this up ?

  Slow CAPX File

• • emoaeden
  • 
  • • Joined 18 Jul, 2012
    • 
    • 51 topics • 377 posts
  • 1

  • 11 Feb, 2016
  • Quote

  emoaeden's example is a great formula. Just remember it's current health, and initial size at a 100 percent. Health*(256/100)

  imothep85 : The reason it's 256 is because it's 256 pixels wide, so if you have bars that are longer or shorter, just make sure you adjust accordingly. Probably an obvious statement, but just in case you're super new, thought I'd point it out