3 ms·
I didn't know what Construct was so I went to the homepage for clues. That intro spinning cube demo runs at a solid 4 fps with graphical glitches on a not exact
by kllrnohj 3y ago
I didn't know what Construct was so I went to the homepage for clues. That intro spinning cube demo runs at a solid 4 fps with graphical glitches on a not exactly slow phone (Pixel 7), give or take, and is a quite terrible introduction for a "Cutting-edge technology that runs right inside your browser like magic."
Then again the entire section on "game engine performance matters" only compares the performance of "JavaScript" (V8? Safari? Who knows!) vs. Game Maker Language and doesn't at any point compare anything about the performance of the actual game engine.
But it is cool that they're switching to WebGPU. Should make native app ports more viable to drastically improve performance and resource utilization
- syntheweave 3y agoThe intro runs fine on my nondescript phone of a few years ago. I would guess it's a browser issue.
- jcelerier 3y agoIt lags on my laptop with Firefox, is a black cube with Chrome, and has a lot of hiccups on my phone (one+ 8 pro)
- shlubbert 3y agoFWIW that intro cube is not implemented with their engine. It's just 4 video embeds animated with plain CSS 3D transforms, so performance should depend entirely on browser optimization on your device.
- kllrnohj 3y agoSeems Firefox hates it for some reason
- red_trumpet 3y agoWeird, Firefox on my 7a seems to handle it qute fine.