GBear Posted December 8, 2015 Share Posted December 8, 2015 i'm optimizing to increase FPS.. and i'm testing CONST.SPRITE_BATCH_SIZE //pixi notice like this..this.size = CONST.SPRITE_BATCH_SIZE; // 2000 is a nice balance between mobile / desktop but 2000 is not good on mobile in my case pc is not problems by SPRITE_BATCH_SIZE..becuase always good.. but mobile is not.. i'm testing with samsung note3 and note 10.1 but there are problems with SPRITE_BATCH_SIZE lower value is more good than 2000 use; please tell me to optimize some ideas thx.. Quote Link to comment Share on other sites More sharing options...
mattstyles Posted December 9, 2015 Share Posted December 9, 2015 I guess the only sure-fire way is to run some sort of test during app initialisation and pick a value that suits the FPS you're targetting. That's easier said than done though. Can't you make guesses? As in, dynamically set the value to whatever you have judged to be a good value after sniffing the user agent? (UA sniffing is bad bad, you should really test by feature rather than UA but it might be the simplest solution in your case as feature detecting, or performance detecting, is similarly error prone) Quote Link to comment Share on other sites More sharing options...
xerver Posted December 9, 2015 Share Posted December 9, 2015 How big are your batches normally? Try reducing to the largest size that your batches get, I assume the whole point of this is to avoid the subarray call later? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.