Arima's Forum Posts

  • Great idea. Construct has been needing something to really show off what it's capable of. I know there's a lot of impressive stuff out there, but it takes so long to make a finished game, a lot of it goes unseen!

  • Personally I would do the check when a collision occurs between an NPC & the hero, why check if the hero is above an NPC that is on the oposite side of the Layout.

    Don't do that, collision checks are way more CPU intensive than simply checking a value. Use what Arcticus suggested.

  • For an on leave condition, you can simply check for the state again. Like:

    If value 'mode' = "standing"

    (subevents)

    • Trigger once (on start)
    • on jump pressed, set mode to "jumping"
    • if mode does not equal standing (on leave)

  • I think it's faster the way Ashley mentioned as well. One less step.

  • The automatic font splitter does some of that, and makes for easy importing.

  • Sorry, should have been more thorough. Turns out it's specific - it doesn't happen by itself, but if comparing the speed of an object with custom movement, it does. The .cap's on the tracker, if you want to test it. https://sourceforge.net/tracker/?func=d ... id=1003219

    Awesome with the fast updates! Looking forward to 1.0!

  • Moving an event with the system - compare value condition deletes the condition from the event. Posting to the tracker.

  • Bug found - might want to hold off on this version. When moving an event that has a sub event, I get an error: "An invalid object in a condition was referenced."

    Posting to the tracker.

  • You could also always add 1*timedelta to the timer variable.

  • Man, I can't tell you how many times that's happened. "You mean it's already built in?!"

  • The question that was being discussed in chat was someone thought that while the GPL didn't cover our creations in construct, the runtime wasn't part of our creations, therefore bundling something like the DX9 redist with one of our creations, since it was using the runtime, wasn't allowed.

  • Ah, but did you have to upgrade DX9 first?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Wow, they don't even bundle the newest version of the older versions of DX? It's like they're trying to bug people on purpose. Which they have admitted to doing in the past.

    Yeah, that whole 'can't be bothered to upgrade DX9' issue is what bothers me the most about it. I'm trying to make a commercial casual game, and I fear that'll stop a lot of people from trying/buying.

  • Always doesn't have anything to do with timedelta. Always means for each tick (a pass through the events) the event is run - which means it will run as many times per second as the frames per second, which can vary, which is why timedelta's so useful.

    If you have an event always - set sprite x to sprite.x+1, then the sprite's speed will vary depending on the fps. Timedelta makes it so it's how many pixels per second, not pixels per frame - like this: always - set sprite x to sprite.x+(100*timedelta) will move the sprite 100 pixels per second.

  • ...

    I really shouldn't be surprised anymore when I find out construct already has something built in. Yet it keeps surprising me. Awesome!