Spinning Dorito's Forum Posts

  • 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.

  • You do not have permission to view this post

  • 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

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You do not have permission to view this post

  • 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?

    About a year ago I remember having an issue with my downloads folder on Win10. It had about 5000 images and opening the folder would be slow and subsequently scrolling the folder would have an occasional freeze too.

    Now that problem is gone. I can open a folder with 50.000 images instantly and scroll it without any kind of hiccups. The icons are lazy loading on the visible area while scrolling the folder. What if some of the icon loading has been changed and now the API C2 uses is actually meant for lazy and not eager loading of the icons?

    Also there's this: https://answers.microsoft.com/en-us/win ... a12?auth=1

    dop2000 can you see if you experience odd behavior with the icon cache? The performance degradation over time may be related to this.

    This may be worth a shot too: http://www.thewindowsclub.com/increase- ... in-windows

    — has been helpful so far by providing workarounds, maintaining the thread and collecting data from people to find out what this is about.

    I believe there's some level of misunderstanding which is causing some to get riled up. Nuance is hard for some to read, so please don't assume there's "blame" or "trolling" or any kind of ill will when someone's actions show they're doing their best to HELP.

    People already pointed at win10 updates being a probable root cause way early on the thread, so I don't get why there's so persistent bickering about it. A change in Windows is the probable cause, get over it, it's still a problem that exists. It sucks for scirra as much as it sucks for us users.

    So to keep the wagon moving:

    While workarounds have decreased the issue somewhat for me, it's not completely gone.

    Ashley reported 1 second to open the dialog, which means he can reproduce the problem.

    To make it easier to debug, I have reduced an earlier example to a state that has the minimal amount of excess, while still showing the problem.

    This capx only has a 1000 objects and some families, nothing else, while also consistently showing 1 second to open when clicking "add event"

    https://www.dropbox.com/s/cm0dildivgcf6 ... .capx?dl=0

    I've spent years dedicated to a project that is now suffering due to this, and I'm not the only one. (count on first post shows 14 users)

    Beautiful. So it has been faster before, so Windows did something that makes what you use unusable.

    The earth moves, so do you.

    There are options to make it work fast again. A change to how the icons are loaded may be needed. A different way of showing them, or alternatively having them populate the dialog on the fly like so:

    1. action popup opens with a text or other light way of showing objects that haven't loaded their icons yet.

    2. icons load la-la, you can can still use the search and select an object you wanna use. Most of the time your typing what you need will take a second.

    Like while implementing stuff fast, you know what object you need to select and what action to add, so you really don't need to see all of the objects at once anyway.

    Alternatives: The thing that "add action" button does, can it be preloaded so that it doesn't need to do "the thing that is slow" every time you add an action?

    --edit

    What if from a certain point onwards, the icon cache on windows 10 is not big enough to accomodate all of the icons in your project, thus they need to be reloaded each time you click "add action"

    Now a windows update might've decreased the size of the cache or done something that increases the footprint of the C2 icons.