blackhornet's Forum Posts

  • Looks like your animation is larger than the PlayerBox, so the positioning is off. I bet if you make the PlayerBox visible, it will become self evident what the problem is.

  • Actually, I've had another look and there's a number of issues here. Lerp isn't the biggest one. Lerp really wants to go from low to high, not high to low, so you need to invert the math, which is why you have to subtract the lerp value from the original. The manual gives the math for lerp. You can try it manually.

    The real issue is Wait! Wait seems to cause more trouble than it does good. If I disable all of the waits, things work again. You have to remember that a true condition runs every tick. So for example, slajd=1 was running many times, calling Wait every time, so there are a lot of waits stacked up by the time you press the second button, which means all of those lerps moving the opacity up where still there, fighting with the slajd=2 code which is trying to move it down. That's why everything was jiggling back and forth.

    You need to change your code to use timers, which there are many threads on, to get the timed behaviour you are looking for. Here's the changes with all waits turned off for the moment, and the cytometriaprzeplywowa lerp altered. You can see it fades slowly, where all the unchanged ones disappear almost immediately.

    Also you should make sure your variables get set to zero along the way. For example, slajd=1 stays running that code forever, until you press some other button. Same for wybrany.

    sample (change the ZIP to CAPX).

  • lerp(a,b,c)

    lerp(100,0,.9)

    a - lerp(a,b,c)

    100 - lerp(100,0,.9)

  • Change your lerp(a,b,c) to a-lerp(a,b,c). If you do the math you'll see the pattern. I'm heading out the door at the moment, or I'd spend more time explaining - sorry.

  • You are clicking on the condition. Move left past the cog icon and you'll see "Add" at the top, and "Add sub-event" there. If you watch your video closely you do actually see "Add" a couple of times - you are just too quick.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • How about something along the lines of:

    <img src="http://blackhornettechnologies.com/Construct2Stuff/non90.png" border="0" />

  • Have you looked at the Breakout tutorial?

    Breakout

  • This is overkill, but I already had this for another thread. It toggles music.

    SoundSample

  • Ah, you need a ForEach: barbarossa_tweek2.capx

  • Try this thread: Image upload

  • Move 'trigger once' up to the can<=0, and move Add 1 to ghostDead to after the destroy. Also, you can avoid the Wait actions here by using the built in 'Wait time' for the fade behaviour. Even the ghost can have a fade with a wait of 1 and a fade of 0.001. Also you can move your destroy code to a 'On destroyed' event.

    barbarossa_tweek.capx

  • Click on the Projects panel, and double-click the Layout/Event-sheet.

  • One way is to store the grid coordinates on each textbox. They never change. Then use the coordinates to store the data into the array. You can then do a ForEach textbox to get the data back out of the array. Also, set the array sizes in the GUI, as the On start Set size may clear the data.

  • A layout resets it's elements when you go to it. This is expected behaviour. The fix is not to do this. You are just testing, so use a different mechanism. Look up the ChromeConsole for an easy way to write debugging text, or use a Layer, which you toggle visible/invisible.

  • SpriteIssues_8dir-stop

    Note: the Right animation is out of sequence. You'll need to shuffle.