If you use a loop to do that then you can just use loopIndex

Set X = LoopIndex

If you don't use a loop to do that then you can use instead push back at X and then set at

X = Array.Width - 1

This will give you always the last X index

Is this only when previewing, or is it taking 2 minutes to load when exported and opening it?

When we export it, meaning that the players will experience that 2,2 minutes or more as on Pc not sure why it takes much much more than that I'm still looking why there is a big difference between the two

C3 takes too long to load when you have many animation frames.

We have 50K+ animations frames and to load the game takes 2.2 minutes.

This is the only part that C3 has no support for games that need a huge amount of animation frames like in our case.

This could be solved if you add support for:

1-Zip files so we can use it to load zips from (C3 files folder or from our server) to make game Updates with new levels

2-Also, by adding support to write to the disk on (Android & iOS) with the Cordova plugin we could save the Zip files directly into the device disk so we can make new Levels updates easier and without worrying about the MB size

https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file/index.html

This will solve two problems:

1-Slow loading

2-We can make updates to add new levels easier which is currently not supported if you need to download the updates from the server.

At the moment we have to remove more than half of the levels so it doesn't take long to load the App which is not really cool when you spend 1+ year making the game.

Is there any possibility that you could add support for this?

Thanks

The context is missing which is very important for any judgment:

For example, if they asked you to share your capx because you needed help with some issue in your code then:

Definitely Not

Never share your capx even if they get angry, the truth they shouldn't get angry and instead they should encourage you to get used to not sharing your Capx for obvious reasons.

It happened to me many times in the past that some users shared with me their capx because they needed help and I had to tell them off very serious that you should never share your main project capx and instead do a quick demo example reproducing your issue. You have to remind them of the consequences of doing that which could be catastrophic.

tapestry

Would you be able to share links to those other cases of developers encountering the problem?

Looking at my Chrom history this is the last ones I visited:

A lot of them seems to believe is the Canvas issue but For me, I think it's Canvas + some Memory issue because I turned it off and still crashes, though it fixes the problem with invisible objects.

https://developer.apple.com/forums/thread/689071

https://developer.apple.com/forums/thread/684843?answerId=684348022#684348022

https://developer.apple.com/forums/thread/690924

https://developer.apple.com/forums/thread/690924

https://bugs.webkit.org/show_bug.cgi?id=231157#c1

========================================

I do agree with "tapestry" and I always said the same thing, on important Bugs like this that are serious will be better to be reported by Scirra for two reasons:

1-Your company will look way much better, that cares for all the issues that affect your engine even if the bug wasn't your fault. At the end of the day, you will have customers worrying and complaining in the forum anyway which can give a bad image to your product.

2- Even if "we" the customers open a bug report we will end up on technical questions from the bug developers that we cannot answer and therefore we need to ask Ashley for answers anyway, going back and forwards between them till is resolved.

A good example of this is:

I have been trying to resolve a bug for 4 months that AJAX fails to load one big JSON file in my Game and I recently opened a bug with Chrome because no one could tell me the source of the problem.

So when I opened the bug, chrome developers told me that there is a bug that AJAX is calling twice, then I had to open another bug at C3 GitHub and ask Ashley to check if Ajax is calling twice etc.... which he checked it and said is not. So the point here is that there are questions we cannot answer anyway as these are questions that only Ashley and his team can answer therefore is more suited for the Game engine developers to report them as they can sort it out much much quicker because they can replay any question that they may have, this way you will save the customers going back and forwards, therefore, wasting more time than it should and also most of the time the Bug developers will ask questions that we normal customers we cannot answer so we have to sit down and watch if gets resolved as it's limited the help we can give them. C3 Team will be far more helpful to them.

One really good point I have to mention in favour of Ashley:

Is that I give him the link to the Chrome AJAX bug report and he is replying and following up with comments in the Chrome bug report by himself to help the Chrome devs, which I appreciate that he takes the time from his busy life to try to resolve this bug which looks like is not from C3 anyway.

So if you open a bug report with the other companies and link back then Ashley does get involved for what I saw.

Transparency doesn't work well with depth buffers which are required for 3D rendering. This is a known limitation and is probably going to stay.

Hoh that is a heart braking to hear, almost all the excitement for the New 3D features are gone for me because of that transparency issue as it looks too bad and unprofessional if you release Games in your name with that issue. I really hope you can find a fix because otherways will be no point in using it unless you use boxes etc ((:

I was really looking forward in using the new 3D in the future.

Quote: "This is a known limitation"

I have never seen any other HTML Game that runs 3D with that issue perhaps they do some tricks or something but probably you tested everything already.

tarek2 Try switching on/off these two settings for safari on your device, verify if it makes any difference for you:

• GPU Process: Canvas Rendering
• GPU Process: WebGL

The iPhone with iOS 15 had the Canvas Rendering ON by default so switching it OFF and turning ON the WebGL seems to stop the Problem with the objects becoming invisible, however, for a run of 20 minutes it crashes 3 times with white screen and two of them there was no refresh button or any other button to carry on so I had to uninstall the PWA and install it again.

In another of the tests for just 2 minutes

It crashed and restarted 5 times and in the last crash I had to reinstall the App again as there wasn't a refresh button or any other button

It looks like it solves the object invisibility problem but still crashes at random

I also tried turning off both (Canvas Rendering & WebGL) but is the same issue, it solves the object invisibility problem but still crashes at random

I googled the issues and it seems that many people reported already the bug to Apple as most HTML games are affected though it has been around 3 months now since iOS 15 and they didn't make any progress, too bad.