alastair's Forum Posts

  • agreed, it's big payment to have surprised on you.

  • Good idea, thanks!

    I tested with the new rally game which felt slow, and also Demonoire which was going at roughly 24 FPS!

    But with the older Njws71, Demonoire runs at roughly 60 fps!

    I have attempted a bug report github.com/Scirra/Construct-bugs/issues/6747

  • dop2000 that's unfortunate! But it's helpful to hear another confirmation.

    The only solution I'm aware of so far is to stick with the old nwjs version 71.

    Did you try testing with that one too?

  • Good idea, thanks! I tried checking win64 with proton experimental on the Deck, but doesn't seem to work for me.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • latest NWJS version 73 is still performing terribly on Deck/Linux.

    I get 20 FPS on it.

    Compared to 60 FPS with 71.

    Interestingly, in 73, despite running so awfully, when using the Deck's own FPS overlay, it reports that it's "60", and the GPU/CPU are both low values too.

    Which seems to indicate that in this version of NWJS, something is artificially slowing or limiting the FPS cap?

  • Thanks, it's cool to see a list like that

  • github.com/Scirra/Construct-3-bugs/issues

    I think they fixed this issue.

    But yeah unfortunately there's a lot of broken stuff happening in recent releases.

    What I'm learning from this is to not do work in the latest beta or I'll be stuck with it for a week or so 😂

  • dop2000 thank you! And the memory error just came randomly while working on the game, not sure why it happened, never seen it before. I might have switch to a different window and back, can't remember.

  • I haven't had this before, and i have 32gb of ram. Not sure if it's related to your guys issues.

  • Does anyone know any good practices that will help keep performance good?

    Or little things to avoid, that might be deceptively simple yet have a big cost?

    Sometimes things can seem fine in a project, but then as the project becomes bigger over time, all the little inefficiencies start to add up!

    For example, I saw someone having performance issues on Discord, and all they were doing is using the action "Move to Object" every tick!

  • anyone know if its better for editor performance to have less tabs open (layouts, event sheets, etc.), or it doesn't make much difference?

  • Thanks for the comment!

    I did another fresh pair of builds, to compare nwjs 71 and 72.

    The problem still exists.

    Both have the same amount of files.

    I wasn't able to figure out how to do the log thing on the Deck easily.

    Interestingly, Deck's inbuilt FPS counter always shows 60, regardless of the game's performance (in both builds).

  • If making a build for Steam Deck (linux64)

    I found that my game only gets up to 20 FPS when using NJWS latest version 72.

    But I get average of 60 FPS when using the previous NWJS version 71.

  • Another large drain on editor performance, is when you have text in a search field.

    So keep the search fields clear when you're not using it any more.

    (It makes a lot of lag, even on my powerful computer.)

  • Just curious how others prefer to work.

    Do you like to have lots of small event sheets that are then included in other sheets?

    Or do your prefer to work with big event sheets?

    poll here if you like: strawpoll.com/polls/e2navGXAzgB