alastair's Forum Posts

  • XHXIAIEIN Tips like this are super valuable. I think people really need something like a Construct Cookbook or CheatSheet that shows the best practices for doing things the right way.

    Maybe this is something the community would be good at putting together rather than Scirra?

    Since the community are the ones trying to squeeze out the performance in real projects, whereas Scirra is just making the tool and is probably not use to the same challenges that we are use to facing.

  • > So more features, hmmm I don't know about that, depends who you ask.

    Depends on the feature

    There's hundreds of features the community wants to see and is waiting paitently for:

    github.com/Scirra/Construct-feature-requests/issues

  • The community wants to see more features added, not the removal of features! 🙏

  • ah ok, thanks for the reply

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • thanks for testing it out!

    Also can do without disabling groups as you can compare each Group's performance in the CPU tab while debugger is open:

  • system conditions/expressions don't do picking, so they're faster.

  • also a commonly forgotten feature is the ability to change the collision cell size with a system action (e.g. at start of layout).

    It defaults to the size of the screen, which is usually too big.

    So reducing it to roughly x2 the common object size is probably going to help boost performance as well.

  • Valve addresses this:

    partner.steamgames.com/doc/features/overlay

    Q. My game runs in a browser. Can the Overlay work in that?

    A. The Steam Overlay requires a game consistently render frames, not pausing rendering or rendering only part of the screen based on dirty rects. Unfortunately, web browsers do not support this model. A workaround for web based games is to host an embedded Chromium inside a native application, with a D3D window and input forwarding to the embedded Chromium. That can be setup to render in offscreen mode, which then renders the resulting chromium texture each frame in the native app. Partners often use CEF to do this, though this is not an easy task.

  • At the moment it seems to be that way. It doesn't work with the steam overlay.

    There is also the Pipelab addon though. Some people use Pipelab successfully with Steam. I think "Noobs Are Coming" might be using it.

  • Webview2 doesn't work well with Steam. I'd recommend not using it.

    The developers have arbitarily decided that we're not allowed to access NWJS in new versions.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Could some of the things that are better in scripting be used as inspiration to improve Event coding at all?

    As someone that uses Construct because of the Event Sheets and because I don't like scripting, I'd rather see the event system improved to the best it can be.

  • jomego Well said. It feels so arbitary as well. The features are working fine, but now we're just not allowed to use them anymore in new versions. It's like "daddy knows what's best for you".

  • Will this LTS also recieve all bug fixes that occur?

    Like the fixes to the animation editor that appened in r450.