I wanted to know if theres a work around to the automated garbage collection at 60 seconds and if not could that be requested? Like a means to specify when to call it?
It seems big hitches called by the first gargbage collection of any gaming session are more or less unavoidable on Mobile. Even In the GooglePlay version of Tappy Chicken you can quite easily test for its interuption in gameplay. Open the app, wait 50-55 seconds before starting a game to ensure garbage collection happens during play and you will see that it causes a notable freeze during gameplay. In the instance of Tappy Chicken it was typically halted for 0.5-1 second, in faster paced games such as my UE4 project it can more or less guarantee a game over for the player.
I’ve tried my best to optimise my project in order to minimise the impact of the GC by reusing actors and such (The hitches are not noticable on PC although they’re detectable by “stat hitches”), but its occurence in such a simple project as Tappy Chicken shows theres little room for mobility when it comes to mobile (Tappy Chicken hitches were not detectable on my laptop even with “stat hitches”). I’ve incorporated “Collect Garbage” command nodes before every match and even at intervals right before the 60th second and everything still halts at that initial 60th second (afterwards every other GC runs smoothy until you reset the game).
Some sort of response on this is hugely appreciated, it makes for a terrible first impression for the game to force a loss on the player.
Just for ref I’m using:
UE4.8
Samsung Galaxy Note 3
Thanks