paprik123456
Your going to have a problem making any P&C game on anything but a Desktop platform. Even many of the other suggested engines either don't do mobile or are massivly feature stripped for mobile.
As for images. Even for desktop NEVER EVER go above 2048x2048. Not enough graphics cards can handle images larger than that. If your image is larger. Slice them apart and place them next to each other.
However if you want the easiest, but knowingly limited feature route then I suggest using another engine. At some point I plan to strip and clean The Blue Code to an adventure game template and engine. But until that time C2 needs some elbow greese for P&C.
—
—
Early in development TBC was running sweet for for mobile games. however TBC demo was never meant to be mobile. Instead the game was going to go mobile after a full game PC release. Now I still did mobile controls, but didn't highly managed resources.
Now saying that. Because this was a one month project no one but me was concerned with the game running on mobile. So the game got hit by a handful of massive resource hogs. Some animators were sending character animations that were 3000x3000 per frame and there were 200 frames... double framed classical style. So in fact there were 2 frames per position. I spent easily a day cutting the frames down to 1/3, resizing the character to 200x500(still could go smaller, but I got complain from the product manager. It was his project).
The game also received a massive dump of sound effects. I really suggest for TBC putting on some good head phones. Turn up the volume and spend some time in each area listening to the sounds. They ended up using half the game total size. Really listen to the sounds of Lisa walking from grass to stone, from carpet to stone. Those muffling effects are reverb files, heck the construction files also used reverb files..
So TBC ran on mobile at a solid 30fps ish until the sounds were loaded.... then CocoonJS couldn't it anymore ... oh yeah. And Glitch also put on FPS drop, but it didn't matter at that point as all the sounds were being implement.
So except for memory issues. TBC didn't really have a problem with devices from late 2012 and including 2013 devices. My Acer A500 was a Tegra2 and the game ran pretty well on an iPad2. However my iPodTouch 4g didn't do so well
I however did avoid XML and instead used JSON and a custom in game scripting langauge.