R0J0hound's Forum Posts

  • It just means different object instances have different values.

  • cjbruce

    Thanks, I'm glad you enjoy it.

    Pwnetheus

    I don't know the cause for the first bit. For the second it sounds like you're adding another condition instead of another event. You may want to run through a few tutorials and maybe read the events section of the manual. I'm not that great at explaining that stuff.

  • SpyDaniel

    Sorry, I'm not working on effects anymore so I won't be able to do that.

  • No, and probably won't.

    The only new feature that sounded interesting was being able to run the editor on mobile. My phone doesn't support it though.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'd assume that's something you'd email their support about.

  • Here's another implementation that matches the ftl generation best I can tell. The idea used is very similar idea to Pulstar's, it's just another way to go about it.

    https://www.dropbox.com/s/yyqwtx8pwnw8t ... .capx?dl=1

  • It was made a long time ago and in the meantime there was a change in the event system that makes it not work.

    To fix change the "dash:spawn dash" action in event three to:

    system:create dash at dash.x, dash.y

    dash set angle towards mouse.x, mouse.y

  • Make a circle sprite and resize it in the editor till the start and end positions are on the edge of it. That's your radius.

    Then run the layout and set a text object to angle(circle.x, circle.y, start.x, start.y) to get the lowAng. Do the same with the end position to get the highAng. You may need to swap lowAng and highAng if it doesn't work.

  • Hello,

    Event number 8 defines the shape of the slope: random(480)+steepness*loopindex

    Making steepness and 480 lower would make the terrain flatter.

    I guess you could make a sub-event like the following to have the steepness change every five steps.

    system: compare loopindex%5=0

    --- set steepness to random(10,100)

    At least that's the idea.

    Controls at all don't make sense in this capx because it's non-interactive. I guess you'd put you control events above event 10 and in them change either ax,ay (acceleration) or vx,vy (velocity) instance variables of the skier.

  • Yes, I guess you could say that. If something is picked it stays picked for the rest of that event and following sub-events unless another event unpicks it. Do some tests that change the frame or opacity of the objects to get a visual to understand it better.

    In that capx event 99 is a trigger that is called when an object is created, and that object is picked and any parent events are tested first. So it's probably some logic error rather than some quirk of the event system.

  • look earlier in the topic. I can't fix a quoted link.

  • Use the a sub-event with "pick nth object" for each

  • link updated

  • The second one works because the created object is still picked in sub-events.

  • Sure, that's fine if it's related to this. I'll eventually see any post in a topic I made or posted in. I'll also get an alert if you quote me or tag me with —

    If it's a different subject it's better to create a new topic and tag me if you want. That would give your question more visibility so other users more active than me can help.