ETA on 4.2 update? Physics reduce the need for manual easing and timing a ton!

In a windowed game, dropping a single frame isn't really unusual - the OS might have just scheduled a background thread or otherwise done something to take CPU time away from the game thread so it misses the 16ms v-sync deadline. Not much to be done about that and affects pretty much everything on the system. So a single missing frame probably isn't anything notable.

Sorry, this is simply not true. I can have a Construct Classic project run for extended periods without drops as well as a Chowdren demo, or a modern game, running at 120fps mind you, so the window is just 8ms. An OS background thread on an 8 core PC is not gonna stall the whole system.

Also Vsync has been broken on chrome for 4 years now, you're gonna suffocate if you hold your breath for an update to fix that.

Colors:

Having complementary colors on top of each other like on the stripe causes vibration due to your eyes adjusting back and forth to the colors. Normally complementary colors work good when your eyes adjust to one and then the visual composition makes your eye travel slowly to the other one. When text is laid on a complementary, it causes eyestrain.

Contrast:

Eyes require value contrast (light/dark) to focus. A very light theme with no darks also strains the eyes due to lack of change in value. This also happens with thin fonts. From even a small distance a thin font appears lighter (a thin variation of a font is also called "light") and can become blurry due to how hard it is to focus on it. Cameras have trouble focusing on low contrast areas too and instead pick up the focus where light meets dark.

Layout:

Eyes are better suited to reading/looking horizontally and currently the line-height causes a lot of unnecessary vertical movement when reading. Having voids in visual design is good for splash pages and such, but for reading it's always better to gravitate towards legibility.

Anyhow, I imagine the migration wasn't an easy task so good job and congratulations on getting this far already Tom

Tested C2 runtime against Construct classic and classic was 3 times faster. So if C3 is 3 times faster than C2, it only means it's neck to neck with the archaic Classic from over a decade ago.

C2 is fast enough for simple games though and C3 is more capable. Thing is they're not necessarily suitable for professional game development regardless of how fast the runtime is since the performance is bound by whatever wrapper is used and comes with baggage from the browser, like Chrome still having VSYNC issues as well as trouble streaming with software like OBS.

This is why all the performance tests on the blog are on 30fps instead of a vsynced 60fps. A construct game simply will not hold vsync under slight load. Also you cannot run a game at 30fps unless you increase CPU load to slow it down.

It seems Chowdren is presenting a native solution that has already demonstrated superior speed on top of fixing vsync, input lag and game streaming issues, so looking forward to where it goes.

As things are now, I would only recommend using C2/C3 for making browser games.

Currently there's no progress on the chromium bug reports.

You can review them here: https://www.vsynctester.com/chromeisbroken.html

As it currently stands, here are the problems you will face when making a game for desktop/chrome using C2 or C3:

-Intermittent loss of vsync when under 30% CPU load

-constant loss of vsync when over 30% CPU load

-3 frame input lag

-vsyncing to the wrong monitor when multiple monitors connected

With these it's very hard to pass publisher QA.

It's better to get this early without monetization than to wait with nothing to work with until the monetization is also complete.

This way you can have your game ready when that feature is complete.

The discord server is far healthier than these forums because you can voice your concerns and talk about obvious and real issues related to the software without being ignored, glossed over, argued with or worse - banned for trying to help.

You personally acted in a way that seemed like trolling on the discord to the point where someone snapped and did resort to foul language. People are doing their best to be helpful and forthcoming with threads with up to a dozen people reporting on a widely known issue, simply to be met with "You are wrong, there is no problem", this results in frustration.

The tone of the channel is active, welcoming, friendly and accepting. Newcomers and pros get to help each others and share creations. People get to discuss things how they really are instead of a bent up, untrue sugar coated vision. This is extremely helpful so users can scope their creations accordingly and achieve their best potential instead of trying something that's not gonna work and falling flat.

The software is good and the channel lets people get the most out of it. I have only positive things to say of the people who frequent there.

Ashley The price of C2 has stayed the same for a LOOOOONG time right? It has more features now and has not been adjusted for inflation.

TBH it's good value even at increased price. Comparing to Fusion, it's in the same ballpark if you account for the paid exporter modules.

You could even say it's been on a sale since the beginning

You can use groups still. The particular issue comes if you put an "event sheet inlcude" inside a group like this:

Normal events inside groups should be unaffected.

There's a number of other cases that drag down perf without apparent reason too, but it could be more efficient if you shared specifics of your project in the Construct discord help section and people can take a looksie.

—

There's a bug in C2 that increases stutters by a ton if you have event includes inside a group. You could check if that's the case for you.

On NW.js and Chrome you can't get rid of the stutters completely due to bugs in Chromium. C3 can't overcome this bug either.

The bug report has been open for 4 years so far.

There is a way to reduce it if you use a way old version of NW.js though. Chromium 49 I think?