alastair's Forum Posts

  • Over a decade ago in C2 there was a new thing called "collision cells", and in order to use them you had to have your "overlapping" condition be first in the top level event (not as a subevent).

    It can feel counterintuitive, because often we prefer to have other filtering conditions before doing something as expensive as a collision check. But apparently it was worth the trade off.

    I couldn't find anything about this in C3 manual, is this still the best practice?

    Here's the old blog post that explains the feature: construct.net/en/blogs/ashleys-blog-2/collision-cell-optimisation-914

  • Good question! I recently discovered how to do this for my game.

    It works well, I changed the Steam interface to Korean, then tested my game and it changed the language.

    Thanks for sharing that TackerTacker those are some wonderful suggestions, does sound a lot more fair!

  • Good point.

    It's easy to do this with Ublock Origin too (which most people use anyway).

  • Thejacs interesting that the newer versions of NWJS work at all for you, I think anything beyond version 71 gives a black screen for my game. So I'll have to stick with that.

  • ------

  • Personally I use nwjs 71, haven't tried the newest ones. It works fine for me on Deck, but I haven't actually got the game on Store yet.

    Did you read the guide for exporting game to Steam and Steam Deck?

    sleepingpanda.games/blog/how-to-export-your-construct-3-game-for-steam-and-steamdeck

    (Ps. it can be helpful to not quote the entire reply, because it takes up quite a lot of space, especially when their post is directly above your own)

  • Made me remember the project setting "preload sounds".

    So I unticked that, and it made the startup about 50% faster! Since I have around 770 sfx files.

    Maybe I should preload the sounds over time during the main menu.

    But I'm actually not noticing any perceivable lag with that preload setting turned off!

  • At the moment I have "nothing" selected for "loader style" as all else don't seem to work well for me. But it's not good because it means there's no loading feedback.

    For my game, clicking the .exe then having it finish loading takes about:

    • 3 seconds for goodish computer
    • 5 seconds for Steam Deck
    • 8 seconds for average to low computers

    Which means it's just showing a black window for a while. And may be confusing as to whether it's frozen or not.

    "Loader layout" does not seem to work with NWjs, unless I'm doing something wrong.

    If I selected "percentage" or "progress bar": it shows black window for only a third of the time, then for the remaining time it shows the percentage/bar. BUT they're frozen, it just stays at "0%" or an empty rectangle bar. So while this feedback is useful to know that something has loaded, it's also not ideal, because the user may think something is broken for it to stay stuck at 0%.

    Maybe I'll keep the setting on rectangle ("progress bar") as that's at least showing some form of change during loading, and might be the least intrusive and confusing option.

    The "progress bar and logo" option doesn't seem great either, since the progress bar doesn't move, and the logo is just using an icon files — which feels out of place.

    And "construct splash" is too intrusive/advertising feeling.

    I'd be content if I could just have a simple line of text that says "Loading". So that people know that something is happening.

    (I don't use the "package assets" option, as that slows the startup time.)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Thank you Tokinsom for confirming and sharing your experience!

    What do you have in "Settings -> Preview with"? I get a white flash only when I set "Browser tab" there.

    I use "popup window" that seemed like the best setting. I have the app installed as it's the best way to use C3 that I'm aware of.

    I think XHXIAIEIN may have initially pointed this issue out and now I'm more consciously aware of this strange flash.

  • Haha, yeah and when you're testing your game constantly, it's a lot of flashes!

  • They occur whenever opening a Chromium window. On both my computers.

    Am I the only one who doesn't understand what this thread is about?

    Brief White screen flashes.

  • Every time I preview my game, or open C3.

    Flashbang!

    Is there an easy way to fix this bug somehow?

    I'm guessing it's a Chrome issue.

  • The next 2 years of updates is going to be so good then!

    There's a lot of great suggestions already.

    Thanks Ashley and everyone for your submissions.