joelmayer importing/exporting array data to CSV is probably a bit awkward, as array data is always 3D but CSV is only 2D. I tried passing an empty 10x10x10 array file through an online json > csv converter and ended up with 30 values instead of 1000.

It should be possible to convert a "layer" of an array to CSV fairly painlessly, but I'm not aware of any tools that do it. If there's enough interest I would consider adding the ability to the array editor itself for import/export. As MS excel supports CSV it could be handy in some situations. However, CSV isn't really standardised, which is a bit of pain.

Admob sometimes just doesn't send Ads, not really sure why. It's worth taking it into account when creating your events. In any of the error events you can check the reasons using the MobileAdvert.errormessage system expression.

pilpgam Admob pushed out an updated on Friday ( not cool ) which added a new setup step. If the setup step isn't completed they purposefully crash the app ( also not cool ) I can't figure out why they needed the step, it seems pretty pointless. I've pushed an update out to the build server to use the older version of Admob, so it should now be working again. Hopefully we will be using the latest version again in r122.

There has been a bug reported today which turned out to be an issue with the "int" expression when a project is minified. Any expressions using it in r120 will fail.

If you are using minification then I recommend that you try disabling it and see if your game behaves correctly. As your exporting to android minification so it's probably safe to leave it off. It won't have much of an effect on your APK size; the native code and any media tend to be the largest parts of an APK.

If your not using minification or the int expression please file a bug report with a project that repeats the issue on github and we'll take a look for you.

I've just updated the manual entry for the mobile advert plugin with more details on GDPR compliance, which includes how to set a custom provider list.

There's been a few people struggling to get their configuration settings correct. With the addition of the GDPR compliance parts some additional setup and properties need to be completed for the plugin to work. There are no open issues with the Mobile Advert plugin at the moment so if you do believe something is wrong please file a bug report at our github tracker.

When you experience an error with the mobile advert plugin it worth checking the "ErrorMessage" expression, as it should contain the reason for error.

A few issues you may be experiencing:

- you must use a custom provider list with no more than 12 providers

- a privacy URL must be provided withing the plugin properties

- app ID and publisher ID must be filled in

- there is now a separate apple and android app ID property ( the old property value has been changed to android app ID )

Hey tunepunk looking at the GC you show in your screenshot it takes roughly a third of a normal frame(5.5ms) to complete, and as far as I can see in your profiler image there's nothing else occurring for the remaining 40ms of that frame. I expect it's managing to line up with some other large task the browser was doing that isn't shown on the flamegraph. Also worth remembering that when using preview chrome will share the process between your game and construct, so performance isn't completely representative.

As ash said GC has changed a fair bit in the last few years. Chrome prefers lots of small GC calls during expected idle time to avoid long blocking GC pauses. The side effect of that is that your memory graph will often appear as a sawtooth, even when there isn't a memory pressure. It's also worth noting that despite chrome labelling that as a "major GC" it was only 400KB ( max heap 34MB ), the graph you referenced is showing GC of about 80MB ( max heap 190MB ) so not only is construct using a lot less memory but the GC was 20 times smaller!

In terms of static allocation, it doesn't magically improve performance. We use it where possible but often it's just not feasible to use. In my experience, forcing the use of static allocation everywhere you can makes code a lot harder to work with, increase overall memory pressure and in some cases can have a negative performance impact.

I'm not trying to wash over the issues your having. Dropped frames definitely suck, and I have to say I've been having a slightly rough day in regards to chrome 69 bugs. I have spent most of the day working in canary instead, so I'm hoping to see some form of maintenance release over the next few days.

Perhaps could you upload the profile you took for us to look at? You can save it as a JSON from the timeline. It might answer more questions than a screenshot.

I'm not completely clear as to the structure of your game, but I'm guessing you don't need all this data to be loaded at once. If that's the case I would suggest breaking it into chunks and then only loading the sections you need. If your trying to produce a terraria style game and have effectively the whole world loaded at once your going to have memory problems left, right and center.

I've been working on minecraft clone written in webGL and JS for about 6 months ( haven't actually had much time to work on it, coding as a living puts you off coding in your evenings as well ). So I'm fairly familiar with the techniques needed for procedural generation of terrain and streaming level loading.

In my case the world is split up into 16 x 16 x 256 block chunks. Chunks don't exist until they have been visited. When a chunk is visited for the first time I generate a 3D array holding a number representing the block type using 2d simplex noise. This is then passed to a separate system where a mesh is generated for the chunk ( so I only have to render 1 object per chunk ). When I leave the chunk the mesh is thrown away and I pack up the block data into a flat array. That flat array is 66kb and if needed could be compressed quite heavily.

While it would be complex most of this could be done in construct for a 2D game. Instead of meshes you could use tilemap instances. With the addition of a small bit of JS you could hold a much smaller representation of your chunk data in a Uint8TypedArray or similar. Additionally you could store your world in a simple binary format that would be a lot smaller than JSON.

I presume your trying to download this file using the Array plugins "download" action? I expect the method is struggling with the array size, but it's not clear why. If you submit a bug to our issue tracker with a barebones version of the project your using to generate the array we can take a closer look.

You can include JSON files ( in our array format ) into your project by importing them into the "files" folder. To load the file in your game you can use the AJAX plugin to get the file as a string, then use that to create your array. We don't support a pure binary form of array files at the moment, only JSON. Binary formats tend to be a lot smaller, and often faster to load, but need specialist tools to view or edit them. Whereas textual ones like JSON are can be read in any text editor ( notepad or textedit for instance ).

The inbuilt array editor in C3 can create arrays up to 1000 x 1000 x 1000. But in practise I wouldn't advise trying to create an array that large, I think the highest I've got it to load is about 60 million cells before chrome runs out of memory, but your mileage may vary.

I was curious how much memory such a large array would use, so I've done a bit of testing. Within the runtime it's hard to predict quite how much memory an array is going to consume, and even with the same data it's going to vary depending on a lot of factors.

You can get a rough estimate by counting the number of objects that make up the array. For starters all arrays in construct are 3D even if your only using a simple 1D array. This 3D array is made from lots of smaller 1D arrays, structured as an array of arrays of arrays.

Number of sub arrays = (width x height) + width + 1

Number of items = width x height x depth

Size of a string (bytes) = 2 x length

Size of a number (bytes) = 8

Size of an array (bytes) = 32

So for an array of numbers ( I used 0 as my number ) with the dimensions [5000, 5000, 1] you would need 900MB. In practise I saw about a 960MB memory increase when I created an object that size ( actually a smaller margin of error than I was expecting ). Unfortunately I can't be any more precise, because the memory profiler in chrome cannot deal with an object this large ( it crashed the tab every time I ran it ). Converting that to JSON gets you a string that is 100 million characters long ( 200MB ). When you use the download method in the array plugin that JSON string is then URI encoded, which increases it's length by 2.5 times. That should be 250 million characters ( 500MB ) but in practise chrome crashed again at this point. If your curious supposedly the maximum length for a string in chrome is about 1 billion characters.

Okay final tally. Say I had that data as a file, used AJAX to get it over the network, passed it into my array then tried to download it. How much memory would that use?

200MB + 960MB + 200MB + 500MB = 1.86GB

700MB of that would be garbage collected after the download had completed, but its still quite a lot!

Hey rickario, we made some changes to how we load folders from the cloud in the last stable. It used to be that we would load the whole tree of folders and files at once, which could take awhile if you've got a lot of files and folders. Now we load a folder at a time, which is generally a lot faster.

Do you find it any faster than the old version?

— what platform are you using? You might have a sign in popup hiding away somewhere, it will show as loading until the sign in is completed. The cloud component talks directly with your provider, so any slowdowns are either the provider being slow or your internet connections I'm afraid.

We have some fairly liberal limits at the moment, mostly to prevent abuse. It's likely to be tightened up a bit in future but it's not our intention to limit users. Just to ensure that the server has enough capacity for everyone to use it.

A minor tweak to what — said; the compressed limit is currently still 500MB, but the expanded version is 1GB. In case it isn't clear these are per build limits, not some kind of usage quota.