Put these two files in the engineering resources. For details, please visit the following website Ģ. Pay attention to the format of "Unity - Texture2D sprite sheet" (there are some lower versions of TP that do not have this format). Pack small drawings into the atlas we need. The next part of this article is about unity 2018.2.5f1 (64 bit) and TexturePacker 5.2.0, the latest version Another familiar method is packaged with TexturePacker tool. There is another article about the first method for you. One is to use the external plug-in TexturePacker to package pictures and use them One is to use the system's own packaging tool sprite packer There are two ways to package and use the atlas in UGUI: When using UGUI, we also need to package small graphs into atlas to reduce Drawcall (like coco2d-x, package into atlas for one-time loading in exchange for image reading efficiency). We often hear that it is to package the atlas in NGUI. ③, loading or unloading multiple images at one time, improving the operation efficiency ②, pictures of different modules can be classified ①, reduce performance consumption and improve processing efficiency Obviously, this is very performance consuming. In GPU, if we want to draw an image, we need to submit the image (texture) to display memory, and then draw it (in this process, a DrawCall will be generated), that is to say, if we want to draw 100 pictures, we need to generate 100 drawcalls. If you do have a much larger goal in mind, building the custom tools yourself might be worth it.As we all know, CPU is used to process the logical operation of the game, while GPU is used to process the image in the game. Keep in mind that unless you actually plan on making hundreds of different assets for your game then these simple approaches are often the best. In small games, this approach has the lowest overhead. In other words, the reference points are not specific to the artwork, but rather hard coded into the game logic. You can even use different colored pixels to represent different things.Īnother common approach is to simply draw all your art the same way and position the weapons “by convention”. You might be surprised how well this works, because you can simply draw the pixels at the right spot in your favorite paint program. For example, you could have a “special” frame in the animation that just has some black pixels on it representing the different reference points. In my experience it’s pretty common to solve these kinds of problems by using some hand rolled custom logic. The first one that popped into my head was Aseprite which by the looks of it doesn’t do anything like that. Honestly, I’ve never actually seen this functionality in similar software. (I do plan to revisit sprite animations at some point in the future, but no set date). Unfortunately, I think it would be quite a bit of work to get this working and I have quite a few things on the to-do list already. It would be nice if you could set custom point in the animation file as you described. I understand where you’re coming from and I think it’s quite a good idea. How are you handling reference-points in your 2D animations? Maybe I am currently thinking in the wrong direction.
TEXTUREPACKER IMPORTER HOW TO
Also to me setting these reference points in a sprite seems such a basic functionality that I guess there has to be a best-practice way on how to do this. However this means manually adjusting these points whenever the sprites change and overriding the Importer/Processor seems no easy task to me. So my best guess is to add the attributes I need to the “.aa” file and extend the currently used “Astrid Animator Importer/Processor”. I do not see anything that fits my needs in the “.aa” format or the texture-atlas. I am wondering how this could be done most efficiently. In fact I need to be able to setup multiple custom points (or even areas) per frame. I am aware of pivot-points in TexturePacker, but as far as I understood, this is used for other purposes and is limited to one point per frame. For example when picking up objects, displaying a weapon or showing effects. Now for some animations I need to specify reference points in the frame to render other sprites to. This setup is pretty much as it is done with the zombie-animations in the demo and works great (after I have learned that sprite-rotating is not supported by MonoGame.Extended currently). Alongside that I have a “.aa” file describing my animations which I manually created. I am using TexturePacker to generate my sprite-sheet and texture-atlas file (using the JSON output format).
0 kommentar(er)
