Ashley's Forum Posts

  • You can always make your own performance measurements.

    "Set HSL" sounds like a third-party effect (Construct only has "Adjust HSL"); in both cases the effect runs entirely on the GPU, and they're very good at it, so it will probably be hard to measure a difference either way. The only real difference is any shader using HSL will have to perform HSL-to-RGB conversion at some point, which takes quite a lot of calculations, but the architecture of GPUs generally means they spend so much time waiting for memory access that there's a lot of time to spend doing calculations, so it probably still doesn't make much difference. I guess it might save a bit of power.

  • If it automatically navigated you away, you couldn't intentionally switch from a beta release to a stable release. So it only prompts you to give you the opportunity to stay on the stable release.

    In short:

    editor.construct.net = latest stable

    editor.construct.net/beta = latest beta

    editor.construct.net/rXYZ = specific version

  • Yes, that's what I said it probably is. You're loading the latest stable release, with prompts about beta updates enabled. So every time you load the stable release it tells you there's a newer beta release. It's working correctly according to your settings.

  • Well, if you've opted in to beta updates, then the latest stable release will prompt you about newer beta releases. If you don't want that, opt out of beta update notifications.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Usually this means you bookmarked or installed a specific version which is now out of date. Make sure you bookmark or install editor.construct.net since that auto-updates; anything with a version in the URL is fixed to that version only.

  • I think you missed the new tutorial search.

  • You didn't mention which device you were using when you had the problem. What device were you testing on?

  • It's not controlled by Construct at all, the connection is managed by the browser. All Construct can do is tell it which servers are available - other than that Construct itself has nothing to do with the connection. If their service doesn't work with major browsers like Chrome then I don't know what they're up to...

  • TURN is a different technology and not part of Construct - it's a separate Internet standard that happens to integrate with WebRTC. There is no "internal TURN" in Construct, other than the fact we host our own TURN server for Remote Preview. By default multiplayer does not use any TURN service. For the Remote Preview TURN server we run coturn on a cloud Linux server, so you could try that. If you have issues with third-party services like xirsys it would be best to take it up with them.

  • C3 RUNTIME: 26 fps and 1.8% CPU

    If you look in the profiler tabs you can get much more detailed information about both the CPU and GPU usage.

    However given the low CPU usage and low FPS, I would guess you have an older device that's in the few % of systems that get kicked down to software rendering. The C3 runtime only uses WebGL so presumably with the C2 runtime you're getting canvas2d rendering only (which is possibly hardware accelerated, since it has lesser requirements). Try installing any software updates or updating the graphics driver. Most modern devices should be fine. Assuming you're using Chrome you can get more detailed information by visiting chrome://gpu in the address bar.

    Also the framerate shouldn't affect the speed anything happens if you correctly use delta-time.

  • Construct could not parse string literals in the way you expected, because it would make it impossible to set some strings. For example if it parsed the string as an expression, you couldn't set a string to the word "newline", because it would interpret it as an expression and insert a newline character; you couldn't set a string to "1+1" because it would evaluate it and set it to 2; and so on...

  • Not at the moment, because any non-flat 3D features allows for depth intersection, which requires a depth buffer, which doesn't normally work with an alpha channel... so it ends up opening a whole can of worms.

  • The object is rendered at the end of the tick, but it's drawn at the position it was at the time of the paste action.

  • It seems to be running fine here. Construct provides tools for you to check performance and investigate why things are slow if you run the debugger and look at the profile tabs. That's the first place to go.

  • Is this not possible with C3's drawing canvas due to the paste object action only happening at the end of each rendering frame and outside of the normal order of events and actions?

    FYI that doesn't happen, it draws where the objects are at the time of the paste action. I think you're referring to an old bug where that happened, but the bug was fixed.