#Texturepacker example install#
#Texturepacker example code#
#Texturepacker example crack#

вЂ“this creates a formatted options table from the Texture Packer data Hopefully that helps you out (and works). But again all of the data is based on the dimensions of the images in the 1x image, so all of the larger files need to be scaled correctly.

#Texturepacker example code#

I use a separate lua module to reference all of my images and I use the code below to figure out the correct data from the Texture Packer file. I did this months ago and completely forgot about it until I just looked! lol. I went back to my code and realized I wrote a bunch of code to figure this stuff out. IвЂ™ve ran few queries here and there but couldnвЂ™t find a working solution. I think that by modifying the exporter to multiply all of the values by 0.5 I will be able to get the SD coordinates. I will try to generate the sheet and lua file for HD files and then convert it to SD file on my own.

IвЂ™ve got around 30 imagesheets which I generate using ant script, so ItвЂ™s quite automated. IвЂ™m looking into different ways of solving the problem.

#Texturepacker example crack#

Unfortunately, this beta has expired and all of the new betas will generate different layouts.ДЄlthough Andreas responds to issues pretty quick, this one seems to be either tough nut to crack or he is focused on something else. Up until week ago, you could use one of the betas, where there was an option to solve it by using base sorting by name, without trimming and NOT using auto-sd but scale. Unfortunately, because Texture Packer is redoing itвЂ™s algorithms for each of them, they may look different. Uid: 94868 topic_id: 30336 reply_id: 122140Д¬orona does load all resolutions using the вЂbaseвЂ™ one. No idea and havenвЂ™t looked into it.ДЄnd not sure about your second problem of the items being scaled up. I think I read somewhere that Texture Packer might be addressing the issue or has some additional code (or maybe that is what you were referring to?) Or maybe it is in the beta. Also make sure your border padding and shape padding are changed also. Otherwise, when it produces the 1x sprite sheet, it will have 1/2 a pixel and it will either round up or down and then your spacing will be off between the two sprite sheets. So if your maximum resolution images are you imagesвЂ™ dimensions should be divisible by 2. So if the two sprite sheets are not scaled correctly, your images will be off. So when it uses the images from the sprite sheet, it is basing the height,width,x and y position off of the data in the 1x file. I am not exactly sure what you mean by the script, but I believe Corona will always use the data from the initial lua file In other words if you have a 1x and a 2x file (with the 1x file not actually having the 1x suffix), Corona will base all of the coordinates off of the data in the 1x lua file that TexturePacker produced. Local imageObject = display.newImageRect(tSheet,tFrame,tWidth,tHeight) Local tSheet,tFrame,tWidth,tHeight = findImage(imageName) вЂ“to make use of image dynamic scaling, you have to use display.newImageRect Return optionSheets.sheet,j,imageTable.width,imageTable.height вЂ“returns the sheet the image was found in, frame index,width and height вЂ“this searches the big options table for a sprite with NAME Local oldSpriteSheetData = oldStyleData.getSpriteSheetData() Local oldStyleData = require('scripts.catsheet') The higher res graphics are bigger than they should be (meaning, the hd images are being scaled up).Д¬ode for loading the spritesheet now looks like -get all sprite data It seems that itвЂ™s not using the script, because animations are out of place. I finally managed to load the high res texturesвЂ¦ But itвЂ™s not working rightвЂ¦Дў problems arose: 1. Images.Whoa, one would think Ansca would have updated their articles to account for this.

#Texturepacker example install#

$ npm install free-tex-packer-core Basic usage let texturePacker = require('free-tex-packer-core')