alastair's Forum Posts

  • Maybe if the next stable is rebranded as Construct 4, then it would make sense.

    Since normally these kinds of huge changes and incompatibles are what happen when we go from Construct 1 to 2, or Construct 2 to 3.

    Nobody in the community is super happy with this but it is what it is.

    Do you think it's because we didn't provide enough feedback?

  • My question was more about having an option within Construct's export window. Like how it worked before r450.

    Anything else feels like a regression.

    I think NWJS should still be available as an option in the next Stable, even if it's in the depracated category. No point removing it yet.

    At least until such a time that parity is achieved with other export options.

  • Ashley can you add an option in the export window for WV2: to bundle the browser with it, so the game is self contained? Like normal native games do. NWJS was able to do that. Thanks

  • John and Mary were invited to join an exclusive club that was allowed to play in the event.

    Ben and Tim were excluded from playing in the event.

    This shows how exclusive has an opposite meaning for me.

    But I can understand the choice to do it that way.

  • Collision filtering uses the words "exclusive" and "inclusive".

    Exclusive: ignore colliding with certain tags

    Inclusive: only collide with these tags

    I find these words confusing, and often have to look up their intended meaning.

    To me, "exclusive" implies the opposite of what it does here (only collide with these tags).

    Do you think there may be better fitting words? Or is it clear for you?

    Maybe "Exclusive" could be replaced with "exclude"?

  • fedca that solution looks great! Having just a simple efficient method like that

  • Are your origin/image-points using decimals?

    (It's difficult to know what's happening visually without seeing it)

  • You do not have permission to view this post

  • What do you mean by web app? Are you using NWJS? That's the only option I know that works with steam.

  • Stick with NWJS, it's the best exporting option we have at the moment.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I've found that NWJS has been the most reliable desktop exporter.

    I have games on Steam with it.

    Just have to use NVPatch-UI to make it work with laptop GPU.

    And occasionally a version of NWJS doesn't work properly, so just try an older version when exporting.

    • In a sprite with multiple animations, changes to image points and collision polygons sometimes are not saved. I think this happens more often after adding/importing new animations, but I couldn't reliably reproduce this bug.

    Yeah I still get issues with this too, I've just accepted it haha. I think my workaround is to import frames then close the image editor, then open it up again to set the points.

    Poor Diego, I've been reporting origin/image point bugs since 2017, it seems like it must be really hard to get this right.

  • thanks! I'll keep that in mind. (Removed from list.)

  • As long as it works, then great! Keep at it!

    However, if you've finished a few games, then you may eventually want it more featured like supporting custom controls.

    For example here is the approach I tend to do with my games. I have a global sheet, and here is the "up" input folder:

    Then throughout other eventsheets all I need is 1 condition to see if the up input is pressed.

  • I'm going to use this thread to track bugs I encounter, but haven't been able to replicate - which means I can't report them. But maybe it's still helpful to myself and others to know of them.

    • Sometimes after opening the Sprite Font image editor it opens with a bright/white background, even though it's set to dark.
    • In a sprite with multiple animations, changes to image points and collision polygons sometimes are not saved. I think this happens more often after adding/importing new animations, but I couldn't reliably reproduce this bug. (Work around?: to be safe, close editor after importing images, then open it again to set them.)