Thank you as always TheRealDannyyy

You rock.

I was a little bit wary to change NW.js by fear of breaking anything, but I've tried the prebuilds in order to export with NW.js 0.44.0. Apparently everything is fine regarding the game itself, I don't see any problem. If a side effect is the game is a little bit more efficient then great! :)

Regarding the Icon problem : it is solved! It takes a little time to load. At first it is super pixelated but then a second later it gets clean. It's better than before though. This happened to anyone else?

Regarding the "trail" problem: it is still there.

I didn't think to look at the particular workaround you're refering to, somehow I thought it was for Letterbox Integer Scale... But the plugin is aimed at construct 2 and I don't find it on the C3 plugin page :/

(I realize we're in the C2 section of the forum but this topic seemed general enough)

How would you go to try an equivalent workaround on C3 ?

Thanks again for a much appreciated help.

Like Dop2000 says it's impossible to tell without getting more specific information. Plus you don't give the exact steps to reproduce the problem.

I've looked at your project quickly. There are several BIG things you need to do in order to get a cleaner project:

- learn to use the "Else" condition to avoid triggering events by mistake

- avoid nesting "On Start of Layout" triggers below other events. Put them at the top and then state your conditions from there. All the events triggering on start will be better sorted and then it's easier to track where something is going wrong.

- you're doing almost everything "every tick". This is going to be very CPU intensive and lead to errors. For example you're setting some texts and opacities every tick, it is just wrong to do it this way. Try using more functions and triggers. You're also setting "Fullscreen Scaling to High Quality" every tick. Useless.

- do NOT "wait for signal" every tick because this will stack up. If the signal comes ten ticks later, it will trigger ten times !

- similarly do NOT use the "Wait" action every tick. For example if every tick you say : "wait 1 second" then "create an object" il will indeed wait 1 second then it will create an object EVERY frame after that.

If something does not work, try disabling / enabling part of your code, it will show you where you must work. Here I couldn't launch the CarteDeJeu layout, the screen remained black and nothing happened (construct froze because no event was happening after a certain point). I disabled several groups and noticed when I disabled only the group "Menu Pause" it worked, so there is definitely one problem in there. I then disabled parts of the code in this group and I identified that the problem came from this block :

Disabled even more and apparently the problem is not the actions, but the conditions.

Somehow this is fine :

This is not :

I don't know why. Maybe construct loses the scope somehow.

I'll let you or someone else check for the rest.

First thing first you should try to adopt the best practices I've listed above.

I mean, it can feel steep to have to pay the whole year at once I agree, but it amounts to a subscription inferior to $10/month, so I doubt the classic "man with a fulltime job" can't afford it.

This is different for students and unemployed users, but that's another question.

And this system actually makes C3 more sustainable than before, not less. A constant revenue flux allows them to plan better and have a small team (that can probably be resized even in a catastrophic scenario) working on the soft instead of just Ashley doing it all by himself.