Instanced Static mesh component bugged behaviour on Android

Trying to increase dynamically number of instances on my Nexus7 2013 device I noticed that sometime half of the instances disappear hitting certain number of instances.(On Pc it works as expected).

In my test I used 4.6.1 version of the engine and an actor with a simple cube model with 24 vertices (due to unsmoothed faces) increasing instances dynamically(no more than 1 per frame).
It fails on 128 instances and 196 instances of the cube. When I hit these numbers it looks like half of the instances don’t render then I can simply add or remove an instance to make them render again.

As if it may help to reproduce the issue I used a simple unlit untextured material to make them simply glow.

Hi Deadlineproof,

Could you post some screenshots showing the setup of how you are spawning the instanced meshes?

I will provide you a picture as soon as I can however the setup is a very simple blueprint fiction triggered by touch button it calls add instance function on the component.this function also print the instance index by instance get count so I expect this exact number of cubes to render.

I attempted to repoduce this again and so far I haven’t been able to. I could be setting up the function different than you though. When you have time feel free to upload the screenshots we talked about or even a test project that shows the issue.

Hi Deadlineproof,

We haven’t heard back from you in a few days, so we are marking this post as resolved for tracking purposes. If you’re still experiencing this issue, please feel free to post back here with additional information and it will reopen the post.

Cheers,

TJ

I was sure to have posted some files days ago, seems like something happened to that post. Google Drive: Sign-in .this is a file with some assets to reproduce the issue just call the function in the provided blueprint. My OS is lollipop ota for nexus 7 razor.
Sorry for making you wait I really didn’t realize the post was gone after I sent it.

I don’t have a Nexus 7 to test with but I’m testing this on a Nexus 6 and all of the instances will render for me. However, I noticed a ‘flickering’ every 50 to 100 instances that were spawned in. Is this the behavior that you’re talking about or are they not rendering at all?

I also noticed some minor flickering on another device however on Nexus 7 on the specified numbers it happens that half of the instances disappear .They just show back if I add or remove an instance.

The closest I can get to this behavior is by playing in the Mobile Preview mode. The meshes don’t appear over time, they appear in groups of 50 or so and disappear, then another group will pop in. With 300 instances it will do this 4 or 5 times with about 3 seconds. Is this similar to the behavior that you’re seeing on the device?

I won’t have access to test on the Nexus 7 because it has been discontinued by the manufacturer.

on my device they appear normally one at time, up to 128 instances then I get the first group disappearing(half of the instances or however 50 or so of them as you said).then all works normally up to 196 instances on the 196th instance It starts again with the a large group disappearing. I haven’t the app installed at this moment so I cannot check how many times it happens .It happens around 4 or 5 times before the tablet goes under 30fps (around 600 instances if I remember correctly)
However on 128th and 196th it always present this issue in a reliable way.So I guessed it is some kind of pattern.Possibly the same issue may arise on other adreno 320 devices.

Hi Deadlineproof,

Can you try duplicating this behavior with a project packaged from the latest release 4.7.2? Also, do you have any other devices to test this on besides the Nexus 7?

Hi, TJ I will try to reproduce it on 4.7.2. My other android devices are quite outdated (mali400, sgx 540),not so eu4 ready, however I can try on them too.

Have you had any luck reproducing this issue on another device?

Hi Deadlineproof,

We haven’t heard back from you in a few days, so we are marking this post as resolved for tracking purposes. If you’re still experiencing this issue on other devices, please post back here to let us know.

Cheers,

TJ