Hey Slavy! Thanks for the feedback :) I used some example projects by R0J0hound as a starting point, he was the one who implemented all the math/physics wizardry, I merely refactored his code and added some features on top of it (I just updated the project’s description with this info). Everything is in events, there are no custom behaviours or JS code in the original project, nor in my version.
Can you share some info about your hardware (CPU & GPU) and what browser you used? I’m pretty sure there’s room for improvement in the performance department, I’m less sure if I’m capable of massively improving it though :D
Oh super cool! Is this your main project at the moment?
I am using Google Chrome on the latest version, on my M1Max 64GB MacOS 26.3 - I was a bit surprised as the GPU was at 0% and CPU sits at about 80-95%. So it may be on my end, unusual.
I don’t really have a main project at the moment :) this one I haven’t touched for a couple weeks now, but I’m hoping to pick it up as soon as I have enough free time and inspiration to do so (both are a bit low at the moment).
Thanks for the specs, that’s a very beefy machine so it doesn’t look great that CPU usage is apparently that high. Although I think as long as the game’s running smooth, it’s not too concerning. I don’t have an Apple Silicon Mac to test/reproduce the situation, but the fact the GPU is at 0% (in some cases Construct’s gpuutilisation system expression can also report “NaN” instead of 0%) is a bit weird.
Another issue I know about that I haven’t fixed is framerate dependency. I just pushed a new build (19) which has the new “fixed FPS” project setting (and FPS is locked to 60), which should be a feasible workaround for that.
I also added some info in the top left about the renderer (webgl/webgpu, etc); I’d love to know what it says on your Mac. On my iPad with Safari it says webl2 | Apple GPU, GPU usage is “NaN” the whole time and CPU usage rarely goes above 25%.
Hey, so even at that high usage before it did run smooth. However I tested the new version, and it’s much better.
So I know on Safari, Scirra have disabled WebGPU at the moment, but eventually iPadOS having WebGPU for Construct will be fantastic. But I tested on Chrome again today for the Mac as that can use WebGPU with AppleDevices, it’s running at 60fps, CPU 15-20% and GPU around 5% - as well as the renderer being AppleMetal with WebGPU, running much more expected!
I forgot they added a locked framerate, that is very helpful too. I have a few devices, if you ever need extra benchmarks happy to help.
← Return to game
Comments
Log in with itch.io to leave a comment.
Super interesting!? Is this a custom behaviour you made? Also, it’s working smoothly, but on my end CPU usage is about 90% at the moment when testing.
Very interesting to see!
Hey Slavy! Thanks for the feedback :) I used some example projects by R0J0hound as a starting point, he was the one who implemented all the math/physics wizardry, I merely refactored his code and added some features on top of it (I just updated the project’s description with this info). Everything is in events, there are no custom behaviours or JS code in the original project, nor in my version.
Can you share some info about your hardware (CPU & GPU) and what browser you used? I’m pretty sure there’s room for improvement in the performance department, I’m less sure if I’m capable of massively improving it though :D
Oh super cool! Is this your main project at the moment?
I am using Google Chrome on the latest version, on my M1Max 64GB MacOS 26.3 - I was a bit surprised as the GPU was at 0% and CPU sits at about 80-95%. So it may be on my end, unusual.
I don’t really have a main project at the moment :) this one I haven’t touched for a couple weeks now, but I’m hoping to pick it up as soon as I have enough free time and inspiration to do so (both are a bit low at the moment).
Thanks for the specs, that’s a very beefy machine so it doesn’t look great that CPU usage is apparently that high. Although I think as long as the game’s running smooth, it’s not too concerning. I don’t have an Apple Silicon Mac to test/reproduce the situation, but the fact the GPU is at 0% (in some cases Construct’s
gpuutilisationsystem expression can also report “NaN” instead of 0%) is a bit weird.Another issue I know about that I haven’t fixed is framerate dependency. I just pushed a new build (19) which has the new “fixed FPS” project setting (and FPS is locked to 60), which should be a feasible workaround for that.
I also added some info in the top left about the renderer (webgl/webgpu, etc); I’d love to know what it says on your Mac. On my iPad with Safari it says webl2 | Apple GPU, GPU usage is “NaN” the whole time and CPU usage rarely goes above 25%.
Hey, so even at that high usage before it did run smooth. However I tested the new version, and it’s much better.
So I know on Safari, Scirra have disabled WebGPU at the moment, but eventually iPadOS having WebGPU for Construct will be fantastic. But I tested on Chrome again today for the Mac as that can use WebGPU with AppleDevices, it’s running at 60fps, CPU 15-20% and GPU around 5% - as well as the renderer being AppleMetal with WebGPU, running much more expected!
I forgot they added a locked framerate, that is very helpful too. I have a few devices, if you ever need extra benchmarks happy to help.
That’s excellent to hear!
Also, thanks for the offer, very nice of you :)