I added a small feature comparison chart between TexturePacker and Zwoptex:
Comparison between TexturePacker and Zwoptex
@zwopple: Can you please check that I didn't forget any major point in your tool?
A fast, easy to use, free, and community supported 2D game engine
I added a small feature comparison chart between TexturePacker and Zwoptex:
Comparison between TexturePacker and Zwoptex
@zwopple: Can you please check that I didn't forget any major point in your tool?
Updated to Zwoptex 1.1.3
Alias creation is one thing I would realllly like to see in Zwoptex, would make animations so much easier to create in code...
Alias creation is coming :) It's a bit harder to do with a GUI since you can add/remove them on the fly :)
That is a great news! What about something more simple like documentation?
Regards,
c
If you're going to put in dithering, please put in a few different dither methods.
There's a nice comparison chart which shows a whole slew of different dithering methods and what they look like: http://bisqwit.iki.fi/jutut/colorquant/index16.html
Bear in mind he's reducing to 16 colors.
Furthermore, ImageMagick code is free to use in commercial applications.
Kohonen neural network quantization (with and without dithering) would be a nice option, as well.
TexturePacker will be updated with several dithering algorithms on the furure.
I am currently working on Graphical User Interface and port to Windows/Linux.
You will be able to create your sheets from the user interface and use automated updates from XCode :-)
One more thing about ImageMagick: It sound a good idea at start but it is not the best solution.
Reason is that you have to adapt the dithering algorithms for game development purposes.
I use a modified version of FloydSteinberg in TexturePacker which avoids bleeding of the sprites.
I currently also do some research on directional dithering to optimize sprites which scroll in one direction. This is something you can't find on the web. I found a good solution for this but its not yet ready to be published.
Most common algorithms try to optimize image quality for still images and are not prepared for transparency or animation.
It is done - TexturePackerPro 2.0.0 RC3 is out!
New Features:
Feature Comparison Chart is updated!
Like TexturePackerPro!!! 14 EUR rules!
I mean....I used zwoptex..and then...boom $24...crazy. customer lost 4ever.
Downloaded the demo last night to try out the gui but it say's it's not supported on my mac.
Any chance of a 32bit version for my crusty old core duo machine? :-)
Sorry for this inconvenience.
I updated it to rc4 which comes with 32bit support.
Thank you, giving it a try now :o)
Like TexturePackerPro!!! 14 EUR rules!
I mean....I used zwoptex..and then...boom $24...crazy. customer lost 4ever.
hmm...TexturePacker is still $22 USD (after conversion) zwoptex is $14.95
hm... robert lowered his prices today.
so can i ;-)
TexturePackerPro $17.95
TexturePacker $9.95
Upgrade from TP -> TPPro $7.95
(These are approx. prices - may vary with tax, curreny...)
TexurePacker is the more expensive tool ($3) but it comes with a big load of cool features zwoptex does not have.
I'll add PVR support in the next hours... ;-)
Customers who bought TexturePacker / TexturePackerPro within the last week can get back the difference if they contact me.
Cheers
Andreas
Here you go: Next big feature for TexturePacker: PVR and zlib compressed PVR file support!
Read http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:sprites#speedup_sprite_sheet_loading_with_pvz for more information about the new format and what power it brings to game development!
TexturePacker: Development snapshot of the Windows version is now available!
Wow, do you ever sleep, Andreas ? *gg*
Nope ;-)
Germans never sleep! Well not really sure about that. :( Zwoptex 1.5 will help this chart look a little bit more fair :)
Let's wait an see ;-)
Will it be available this year?
You've got quite a lot to do until you can keep up with TPPro ;-)
Update ;-)
TexturePacker now supports the current version of .pvr.ccz format.
@riq: I wanted to make this the "update" thread....
But if somebody requested a feature or found a bug which was discussed in another thread I think they should also know that their is a solution for the problem, don't you think?
@riq: Just to get things right:
If somebody discusses a feature (e.g. like our ccz format) and I've implemented it - instead of tell them that the new feature is now available I tell em to read this thread because this is the announcement thread?
E.g. this thread here:
http://www.cocos2d-iphone.org/forum/topic/10899
In the end I should tell them: Read this thread to know when it's done?
I understand your concerns about spamming but only announce updates if they fixe the problem addressed in the thread. If a thread has nothing to do with a problem that TP solves I don't mention it...
If somebody asks about a way to create sprite sheets what should I answer? "I know a tool but I must not say its name"? Or somebody has memory problems because he uses RGBA8888 am I not allowed to tell him to use RGBA4444 and an apropriate tool to create it?
I think, Riq is telling you that your promotion is just a bit too aggressive... And I agree. You made a great tool and there is really no need to poke someone's eye with it. I personally think that, comparing two products the way you did it with zwoptex, is just something you should keep on your site and not making it public on this friendly forum.
After setting the chart up I immidiately contacted Robert to check if it was ok for him. Here is what he wrote back to me:
Hey Andreas,
Looks pretty good there is a typo "zwo major tools". I'm impressed with Texture Packer
and you've done a really good job...
...-Robert
So this was set up by me to be a fair comparison between the tools. Robert can also add his features. I think a "neutral" ground for the comparison is best - I don't want to set things up on my own page and be blamed for forgetting a feature Zwoptex has.
You must log in to post.