PhysicsEditor is a tool to create the (collision) shapes of physics bodies from images. It also allows editing of the physics world. LevelHelper is an editing tool to design your game visually. Both create a single large texture from individual images. SpriteHelper is essentially the same tool as TexturePacker.

What's the best approach to doing this swap?*Do I have to create all my assets via script as described in the docs? Or even create two entire sets of atlases, sprites, and animations?*Or, is it possible to create my Sprites, Animations, etc and somehow 'swap' out the underlying exAtlas updating the sizes accordingly? Cocos2d (the platform I'm porting this game from) has this sort of automated process, but I'm aware they've had years to build that kind of feature.The forward can change to up and the gravity can change to Z as you already mentioned. DesignerParticle Designer -Texture Atlas Tools Texture Packer, and How to.At runtime, I want to use either the low res textures or the high res textures depending on the device I'm running on. You can adjust the layout of the sprite sheet in the right panel see Texture Settings.Slide 1 3D Programming Cocos 2D-x and Unity 3D Nguyn c Ton -51103691 Bi. The sprite view updates each time you add new sprites to the folder, rename or change sprites.

I don't have almost any experience regarding image compressions methods, hence I do not know how to proceed. Keep in touch, this topic won't be closed easily, we both need more example to prove it.I have a doubt regarding the texture size.We have a pair of big images which cannot be compressed, and which would occupy something around 2048x2048 pxs in a texture map.Hence, as they cannot be compressed (any methods we tried made it look really bad.), we would have 16MBs only in a texture maps for those images.Is there any other way, using ex2d or not, to load those textures into a sprite?I mean, each individual. XZ, YZ platform is really not that important once the team have the same knowledge and have an agreement in encoding the game.Hope you can understand and I'll seek the reason deeply to find out if XZ, YZ is really necessary in the future. I use it made prototypes and they only have up, right vector, but still can create games without trouble. Plus In my previous works, I developed a 2D engine that only have x, y coordination.

You init the batchnode with the texture atlas you have prepared (thanks to SpriteHelper or TexturePacker), you add the batchnode to the scene, and then create children of this batchnode which are the actual sprites you see on screen.The batchnode is added to the scenegraph with its own 'global' z-index and the batchnode children are added to the batchnode's node and receive a z-index which is relative to their parent and used only to sort them amongst each other. Well all limitations that come with not being able to switch render state between primitives as you render them in one go). One would need to change the drawing order of sprites according to the distance from the camera in order to have characters walking in front of some objects and behind them according to their position on screen.The problem, as I am seeing with Cocos2D too and the re-ordering in their scene graph, is that such re-ordering is easy for children of the same batch node/texture atlas, but there are considerable more problems if you mix and match different atlases and multiple childrens of the same batchnode and keep z-ordering correct according to the formula you are using.How to deal with this in Ex2D? Is it possible to fetch all animations from the same texture atlas but to have each sprite be independent (separate draw call per sprite even though they use the same atlas)?How would you approach this kind of scenario with your toolkit?Click to expand.Thanks for the answer, I guess I made some confusion when explaining myself earlier on.My question was not about how to batch items and how to reduce draw calls, I do understand how a texture atlas helps in this case (both to reduce draw calls and to avoid redundant state changes).Cocos2D uses a scenegraph and renders all objects at a default z (say z=0) using an internal z-index for each node to decide the final drawing order.To take advantage of batching on Cocos2D you use a special node called batchnode and accept some limitations (such as using the same blending equation for all batchnode's children. Pngs and decompressing them at runtime?Sometimes this trade-off between performance and storage may be worth.I would like toask you for some tips about using Ex2D (I am evaluating Unity and some 2D Toolkits for it) to realize what we could call an ol' school 2D beat'em up with sprites that can move horizontally, jump along the Y axis, and walk up and down with the Y axis movement here affecting the z-index so to speak. Png texture map generated on the computer before compiling anything has less than 2MBs, and when I build my project using RGBA32, it turns to 16MBs.Thanks very much, and sorry for the ignorance on this topicEDIT: found a nice thread on this topic: Hence, is there any way of storing textures as. Can I use any alternative method of compression which does not degrade image quality? I mean, the 2048x2048.

Texturepacker Vs Spritehelper