Are you using solids or jumpthrough ( from the title seems latter )?

I spent about 3 days dealing with this, in the end I decided to not use jumpthrough and use solids and when I need to drop down ( press Down arrow ) from the platform solid behavior is disabled for that platform, also any platforms above the player have their solid behavior disabled so he will not bump into them when jumping from another platform below that one.

It actually worked fine on my PC, but testing on a phone and another PC, player would just fall through often. Even when movin platforms at 60*dt which is pretty slow.

Also, Construct 2 export ( from Construct 2 seems to handle it much better )

Being slightly paranoid has its benefits I guess. I have not run into this bug, but whenever I want to do something like that ( open another project to copy/paste or delete stuff and take a screenshot ) I open an older version of that project.

You never know, software may screw up or I may screw up and do something I don't wanna do

Routine and stable for some, unstable and downright wasteful time wise for others.

That is why updates should be done when the end user wants to do them ( Construct 2 worked that way )

It has always been a sort of a golden rule with professionals. NEVER, EVER update anything mid project

Auto updates have always been a horrible idea, probably the worst idea in history of software development.

It has caused huge and numerous problems in the past and still keeps on giving, most notably in the past with Apple OS components and iTunes updates making PC programs unuseable ( because they relied on quicktime ), Windows 10 problems too numerous to mention here, and obviously with Construct 3. Win 7 and 8 and XP before never had these problems

Construct 2 has been working without problems for years, maybe a bug here and there , but nothing that would actually make me lose work. Construct 3 on the other hand seems to make itself unuseable with every update. For me anyway.

With every update you roll the dice.

If your machine is working today, it will still work 5 years from now too if you don't change anything.

You can find it somewhere if you do a search for PNGoo, but since it is basically a GUI for this https://pngquant.org/ and can be downloaded from different sites be careful from where you download it so you don't get some malware with it.

I got mine a long time ago, so don't remember where exactly

Edit: Just noticed there is a link to PNGoo and other GUIs on that page.

just compress your graphics on our own, if you want to?

I always do

You can also already apply lossy compression if you want - just recompress the exported spritesheet images after export using your own tools. So you can basically do it already manually.

I believe this is what the original post was referring to. I tried it. Using a 20 MB game as an example, using recompress images in Construct 3 I end up with about 18 MB, using PNGoo separately I get only about 8 MB

That is the difference the original post was talking about. That it would be more convenient to have that kind of compression in Construct 3

Anyway, I always recompress using PNGoo anyway. File size savings are too good not to use it.

One issue though is when building APK, you cannot recompress with a 3rd party tool as it generates a finished APK file so you end up with a needlessly huge file size. Or am I wrong here.

( I have not really playede with APK exports here, so if I am wrong please correct me )

For all practical purposes It is if no other humans can see the difference.

Nothing wrong with lossy compression. Flash used jpg and looked just fine

When hawks and eagles evolve hands and start playing games, then that will become an issue for sure.

Try PNGoo.

I use it and also get at least 50% reduction and no loss of quality as far as I can see even though it uses pngquant which is lossy compression