A fast, easy to use, free, and community supported 2D game engine
horseshoe7
Member
I don't think Loew is a spammer. He's promoting a tool for cocos2D. If you have a good tool for cocos2D, promote it! but please don't get all upset because someone made something to help the community. Yes it's a bit expensive in this era of $0.99 Apps, but it's a useful tool.
Point is, he's helping the community and people get upset that he wants to make a bit of money for his hard work?
@knbmedia:
- command line: can you change the color of the size message if it's not the half of the HD size (like a warning) because when you have a lot of sprites, you can't look at each HD/SD size to verify it...
I'll check if this works.
I could set it as warning message for the XCode integration
- GUI: maybe you can just make a warning when publishing ? so it will not slow down layout.
I added a status message in the lower left corner of the window which shows the created size after exporting.
@horseshoe7 I think it's all because of the shady looking avatar.... :D
@jordo & horseshoe7
I am really deeply frustrated: The one complains about my avatar, other guys tellme that TP reminds them of Tiolet Paper....
It's really hard to run a business! ;-)
So here's the deal: Create a cool avatar for me - I'll choose and the one I like most gets a free TexturePackerPro license ;-)
TexturePacker 2.1.1 beta 1 adds a new feature for all users of 3rd party sprites which use a color instead of transparency. (Like Reiners Teilesets)
Read more about this new feature in my blog post here:
Using TexturePacker with 3rd party tile sets
Additionally to this I wanted to point out that you can get TexturePacker for free if you are running a development blog... ( with at least 5 blog posts which are not "hello world" ;-) )
Hi, I've installed the recent 2.1.1 ( non-beta ) and there is a strange thing - no command line support. There is no TexturePacker in /usr/local/bin, and I simply cannot invoke it from shell :) Any solution ? I could copy it by myself, but I really cannot say which ( from where ) executable I should copy ( from GUI version in /Applications ? but it is made with the Qt framework, so executable should link to the Qt libraries, and it does not work... )... Recently I've used some of the 1.1.x version, and I remember that works.
Or maybe a free version doesn't have a command line support ?
The command line version is available in all versions.
Strange. I removed my link and ran a new install and everything is fine.
Did you install it in some other place than the Applications folder?
Please do not copy the executable - this won't work. Instead create a link like this:
/bin/ln -s /Applications/TexturePacker.app/Contents/MacOS/TexturePacker /usr/local/bin/TexturePacker
@cocos2dbeginner cool ;-)
Hi Andreas,
I just got the TP update and was wondering... what is the heuristic mask for?
I mean if I wanted the background of a sprite removed I would remove it before working it with TP.
At first I thought it was to save space in the spriteSheet if some sprites had the same background (and being able to recover them in cocos2d) but it doesn't seem so.
So, why then?
Hi,
heuristic mask is a convenience function for people using old fashioned 3rd party tile sets like this one here: http://reinerstileset.4players.de/
It has no use for people who work with an artist since he can export png files with transparency.
You could also remove the background color with photoshop but since the tiles are single sprites you would have to work on all of them.
TexturePacker now allows you to simply import the sprites and activate the heuristic mask.
By the way: The new 2.1.1 contains several UI improvements including support for smaller screen sizes and a bunch of bug fixes.
One new feature which could be of good use is an alpha threshold when trimming sprites.
I also added tooltips for all settings. Simply hover over the label or the control to get a short description what the option is good for.
Cheers
Andreas
Well, in the label for "Threshold" I see the description for "Trim" so no use for that one :)
The headline is "trim" but if you read the last paragraph it explains the threshold...
This update comes with an important bug fix: Scaling down the sprites implicitly activated premultiplication of alpha values. This lead to dark outlines on anti aliased sprites and some strange pixel artifacts when dithering.
I have downloaded the last version of TexturePacker and I can change the Alias name of the sprites.
I want "EnemyRed" instead of "enemyRed.png", for example.
Can you include this feature soon?
double click in the alias name to rename.
Mark Sawicki
Member
+1 for alias name changing..
Also, how about a simple checkbox/flag to automatically create an alias name without the file extension of the frame.. so if the option is set, enemyRed.png is aliased to enemyRed automatically.
-Mark
edit: or maybe even better, simpler, is to have a setting in preferences with a simple regular expression type input to define the alias name creation. i.e.
[filename].[ext]
[filename]
or something like that..
Ok - I'll add that ;-)
thank you!!
Hi, I don't know if this a problem with TexturePacker itself ( maybe cocos2d ? ), but I have some problem with *.pvr.ccz texture format. ( With .png textures, everything is ok )
I've thought that recent version ( 2.1.2 at this time ) will fix that, because my problem is quite similar:
This update comes with an important bug fix: Scaling down the sprites implicitly activated premultiplication of alpha values. This lead to dark outlines on anti aliased sprites and some strange pixel artifacts when dithering.
But unfortunately, it doesn't...
I still have some black, sharp outlines around some sprites ( always around rendered text labels - if that could be important ) This problem appears with both RGBA8888 and RGBA4444 texture formats, with dithering on and off, it is not a problem for .png textures.
Maybe someone else had a similar problem ? Andreas, did you hear about something like this ? Or maybe there is a problem with my command-line syntax ;) ?
I could share you my problematic sprites for testing...
TexturePacker: 2.1.2
cocos2d: 0.99.5
You need to set
[CCTexture2D PVRImagesHavePremultipliedAlpha:YES];
before loading the textures.
@lano78 I did currently not plan add it to AppStore.
Some of my reasons are this:
If you find a bug or have special needs I can fix it within several hours and supply you with an update. I think that I'll loose this flexibility - and this is bad for all users.
TexturePacker has its essential mode - in which it runs for free with basic features enabled. This would also not work in AppStore since there is no InAppPurchase yet.
There are also several developers who want to archive the version of TexturePacker they used to create their game which would also not be possible to do.
Additionally you can now use the license key on other platforms- TexturePacker runs on Linux and Windows too. Or maybe your artists work on Windows...
It depends on the pixel format you choose.
If you use RGBA8888 the amount of memory is the same. (Except that loading a PNG uses 2x the buffer while loading)
RGBA4444, RGBA5551 and RGB565 are at 50% of memory usage
I used RGBA8888 and pvr (not compressed), Autosize selected, padding set to 1,
I have 16 sprites on the sheet (all png's), 8 SD 32x32px and 8 HD 64x64px. It uses 10mb more ram and I have no other apps running on the device.
I'm just curious, the textures loads much faster but what could cause the extra ram??
how do you measure the memory usage?
I have added some code to CCDirector to display device Ram. I'm not running Instruments to get the data, I just noticed it dropped by a steady 10mb and it stays that way.
edit;
I ran the game with instruments it's back at 12.25mb, the only memoryleaks at the moment is in AudioToolbox at 12kb and 480b in one of my CCArray's. So at the moment it's not much at all.
I'm going to switch back to my old spritesheet I made with Zwoptex (png) and see what happens.
edit;
My old spritesheet only use 10.45mb.
You must log in to post.
