> A .capx is worth 1000 posts. If you have a performance problem, reproduce it in a minimal .capx and share that. Then I can profile it and get some actual data on what is going on, rather than just aimlessly speculating. You should also not use any third party plugins in such .capx files (as per bug reports). If the performance problem is caused by a third-party plugin, it's not our problem at all.
>
Ashley
As I said upthread, I was hoping to get feedback on what potential issues could be causing it so I could fully test/tweak as much as possible before reporting it as a bug .
Since I'm loading a TMX at runtime, which C2 doesn't support, I'm using a 3rd-party plugin to bring in the files - though there's no reason it should impact the performance in this case since it's not active after loading the file, and hasn't previously affected performance. The performance issues can be traced directly to how much of a tilemap is on-screen combined with how many tilemaps are on-screen at the same time with nothing else going on other than loading the TMX and setting the tiles on the appropriate tilemap objects. Performance is also affected by what portions of a tilemap are on-screen, and when portions of the tilemaps are visible that don't have a lot of repeating areas of a single tile, there's a hit to the framerate. Using tilemaps versus not using tilemaps is the only variable in the scenario I've described in above posts, with tilemaps affecting performance vs. no tilemaps not affecting performance.
And still, a capx is worth a thousand words..
Sharing a capx isn't the same as filing a bug-report..
Can you recreate this framerate drop in another capx?
Maybe you could import the tilemap from tmx and then export asjson, so in a new layout you can load the tilemap from asjson to see if the problem persists..