This is a very nice interface and tool for what it does and I appreciate releases like this.
If I may, I feel it has much more potential. For example, if it were able to create slices on a single sprite rather than making the user add image files individually, this would be a huge plus to begin with.
On top of that, if it allowed per-slice data such as origin points and custom-named points (to be used in code for things like sprite rotation or otherwise) it would be even more useful.
Taking it further you could add slice data fields (for things like naming groups of slices on the atlas along with an ID of some kind, for example: GrassSprite 01, or string IDs and sub-IDs: "Scene", "Lobby", "Table", basically just user-defined data per slice. This would be immensely useful.
I have created something similar but your GUI is better, you have features I don't, and your interface is already set up to add the things I mentioned. I would definitely pay for a professional version of what I have described.
If you feel there is already a tool out there that does this kind of thing, or a reason why these ideas are not practical in a game-dev workflow, please let me know, since I may be missing something!
Keep up the good work on all your wonderful tools and above all, Raylib! Thanks for reading.
Hi! Actually I'm already working in some of the proposed features!
I'm trying to support automatic sprite-slicing by alpha when loading a sprite containing an animation sequence but unfortunately I couldn't get it working yet.
The sprites custom tag/class has been in the roadmap for a long time and it's almost ready! Just testing the best way to expose it in the UI, at the moment I'm using a similar button to pivot-point-edit and a floating window...
Thanks for your reply! I saw your Youtube interview about Raylib today, it was very nice to see and hear your comments and get to know the producer of this special library.
Glad to hear a custom tag feature is on the roadmap!
As for creating slices, simply drawing boxes would be sufficient for me. Then each box/slice could have the custom tags and points. I would appreciate up to at least two or three points.
Another idea is "zones" which could simply be boxes or any polygons within the slice. This could be used for defining no-walking zones, trigger zones, or even pseudo-vertical zones for testing 2D upright collisions - for example, whether or not a flying arrow hit a tree trunk. You would need a base poly or ellipse, and a vertical line/height point, which should be enough to create a psuedo-3D collision area for a 2D upright object. I have these things in my own game engine but have not developed all the features in an interactive GUI, many of them are coded. I stopped working on it in case such an advanced editor existed, but I'm not sure there is one.
With such features you are technically taking sprites to a kind of "object" level, using a GUI to give them a body of really practical data (as well as user-defined data) that's ready to be loaded and utilized by an engine. The output could be in various formats if needed, but any format would work for me. Just need the data! :)
I would be useful to move the pivot point with the arrow keys, to make small adjustments, right now you have to be precise with the mouse, which isn't great if you want a specific pixel.
It would also be nice to have buttons that set the pivot at specific predefined positions like centered, mid-bottom, etc. Even better if you could select a bunch of sprites and click those buttons to set it for all (eg: to set it to center in batch).
While I can happily recommend (and even recommend sponsoring! go do it!) raylib, I sadly cannot recommend this software (rTexPacker).
the custom user interface is very small and inaccessible to use on mid-to-high dpi screens in windows. instead of 6 themes, I'd give the world for a "scale 200%" mode
the contrast on many of the buttons and ui elements is extremely low, including enabled elements
none of the fonts adheres to common legibility practices of modern UI
the "dark" theme is overall the best for legibility, but the contrast on greyed out buttons is comically the lowest
lots of interactions feel surprising or counterintuitive, and don't adhere to widespread UI standards
many actions are not discernible from the labels on the buttons, e.g. "trim sprites alpha"
there are no tooltips for most of the actual actions this tool performs
by default, the sprite view is filtered with LINEAR/LINEAR_MIPMAP (in a sprite packer? this should default to NEAREST)
zooming does not zoom to the mouse - it zooms... somewhere?
rTexPacker can't seem to import existing sprite sheets (filmstrip or otherwise) that contain multiple frames
individual UI elements "look" like windows in an MDI app, but the application does not work scaled to larger screens, all of the UI stays tiny and just moves apart impractically far. I expected every single one of them to be draggable, dockable, and resizable (in that order of priority)
It's not very expensive, but it was a mild disappointment - I'll not be switching to rTexPacker over TexturePacker.
Hi tiger.blue, I’m sorry your experience with rTexPacker was not as good as I’d like to. Thanks for all the feedback provided, it seems most of the issues you listed are related to UI/UX, I’ll try to review some of them for next release. Thanks.
Thanks for understanding, I had a really hard time trying to use rTexPacker. UI/UX is the main concern indeed. (and a simple way to split filmstrip sprite sheets... but one can always go to ImageMagick for that)
Can rTextPacker generate sprite font atlases where every character has the same width, similarly to what is displayed in sprite view? This is important for pixel fonts for ex. to avoid a score bouncing around in game when the numbers change.
Great tool, I wish we can have something such as "TexUnpacker", Would be nice if we could detect sprites within a sprite sheet, and export data to the formats supported by the app, something like "Atlas Image Data Generator" app do but the interface there is buggy and not user very user friendly.
Implementing such a system is not trivial, it requires some work, many considerations and probably some limitations. For the moment it's out of scope but if I got more resources (time, money) I could consider working on it.
Great tool - enjoying using it so far. One small request though, would it be possible to add the option to toggle on/off texture filtering? When dealing with pixel art the blurring caused by bilinear filtering makes it a little more tricky to work with. Thanks!
Is it possible to make the program, output multiple atlases if the number of sprites overflow the atlases? Then a map can be made to lookup which atlas the sprite belongs too. If source could be provided, I could add the feature myself, but this is closed source. It would be possible to make this feature even just using the binary, but would be easier if it already does this or source is available, even in a limited context. Either way buying this later today.
Maybe in a future but now my resources are very limited to keep improving this tool. I prefer to keep it closed source, it took me thousands of hours of development and I’m trying to monetize a bit all that work.
I am in now way saying you should open source the tool and not be able to monetize it. I simply wish for some way to access the source with purchase, even in a non redistributable limited license manner. I would be more than willing to sign any NDA or pay an extra fee or something, just because it would make my life easier, but if this is not possible, I understand completely.
I would also like to stress I am in no way ungrateful for all the work you do on raylib. It is a wonderful technology. I am using it now and appreciate everything you do. I have already purchased this software and completely understand any limitations you have to impose to insure your ability to make money. The fact you even offer the software for free as use as a web app is commendable from the outset, I have no issues paying you something for a small part of all the work you have done, and the existence of raylib brings me great joy in not having to re-implement many things when I create projects that I do not desire to use giant monolithic engines with. Thanks for everything you do Ray.
I was wondering if it is possible, when exporting the texture, to configure the number of channels per pixel? Specifically, if it is possible to export the texture in grayscale? This feature would be very helpful
Actually, I considered that option but I decided to keep that image-editing functionality separate from the packaging functionality. You can use rTexViewer to edit the pixel-format of your exported atlas.
There can be sprites that have a red border around them that are not on the atlas, is there a way to automatically delete all the viewable sprites (ones without the red border)?
You can check the code of rFXGen, rGuiStyler, rGuiIcons and rIconPacker, they are open source and all my tools use the same base template so the code structure is almost the same. rTexPacker just has specific code to package sprites but that's a few lines of code because it uses stb_rect_pack library.
← Return to tool
Comments
Log in with itch.io to leave a comment.
This is a very nice interface and tool for what it does and I appreciate releases like this.
If I may, I feel it has much more potential. For example, if it were able to create slices on a single sprite rather than making the user add image files individually, this would be a huge plus to begin with.
On top of that, if it allowed per-slice data such as origin points and custom-named points (to be used in code for things like sprite rotation or otherwise) it would be even more useful.
Taking it further you could add slice data fields (for things like naming groups of slices on the atlas along with an ID of some kind, for example: GrassSprite 01, or string IDs and sub-IDs: "Scene", "Lobby", "Table", basically just user-defined data per slice. This would be immensely useful.
I have created something similar but your GUI is better, you have features I don't, and your interface is already set up to add the things I mentioned. I would definitely pay for a professional version of what I have described.
If you feel there is already a tool out there that does this kind of thing, or a reason why these ideas are not practical in a game-dev workflow, please let me know, since I may be missing something!
Keep up the good work on all your wonderful tools and above all, Raylib! Thanks for reading.
Hi! Actually I'm already working in some of the proposed features!
I'm trying to support automatic sprite-slicing by alpha when loading a sprite containing an animation sequence but unfortunately I couldn't get it working yet.
The sprites custom tag/class has been in the roadmap for a long time and it's almost ready! Just testing the best way to expose it in the UI, at the moment I'm using a similar button to pivot-point-edit and a floating window...
Thanks for the ideas!
Thanks for your reply! I saw your Youtube interview about Raylib today, it was very nice to see and hear your comments and get to know the producer of this special library.
Glad to hear a custom tag feature is on the roadmap!
As for creating slices, simply drawing boxes would be sufficient for me. Then each box/slice could have the custom tags and points. I would appreciate up to at least two or three points.
Another idea is "zones" which could simply be boxes or any polygons within the slice. This could be used for defining no-walking zones, trigger zones, or even pseudo-vertical zones for testing 2D upright collisions - for example, whether or not a flying arrow hit a tree trunk. You would need a base poly or ellipse, and a vertical line/height point, which should be enough to create a psuedo-3D collision area for a 2D upright object. I have these things in my own game engine but have not developed all the features in an interactive GUI, many of them are coded. I stopped working on it in case such an advanced editor existed, but I'm not sure there is one.
With such features you are technically taking sprites to a kind of "object" level, using a GUI to give them a body of really practical data (as well as user-defined data) that's ready to be loaded and utilized by an engine. The output could be in various formats if needed, but any format would work for me. Just need the data! :)
Thanks for reading.
When I save a project (.rtp file), where does it gets saved?
I'm using the steam version on Linux (Fedora), and seemingly nothing happens.
Hi! I imagine you refer to the itch.io rTexPacker version, the Steam version is not available for Linux, only for Windows.
When you save a project a system dialog window should appear and ask for the path and filename to save your .rtp project, does it appear?
Please, could you report this issue to: https://github.com/raylibtech/rtools
I would be useful to move the pivot point with the arrow keys, to make small adjustments, right now you have to be precise with the mouse, which isn't great if you want a specific pixel.
It would also be nice to have buttons that set the pivot at specific predefined positions like centered, mid-bottom, etc. Even better if you could select a bunch of sprites and click those buttons to set it for all (eg: to set it to center in batch).
Thanks for your feedback! I take note for next release!
While I can happily recommend (and even recommend sponsoring! go do it!) raylib, I sadly cannot recommend this software (rTexPacker).
It's not very expensive, but it was a mild disappointment - I'll not be switching to rTexPacker over TexturePacker.
Hi tiger.blue, I’m sorry your experience with rTexPacker was not as good as I’d like to. Thanks for all the feedback provided, it seems most of the issues you listed are related to UI/UX, I’ll try to review some of them for next release. Thanks.
Thanks for understanding, I had a really hard time trying to use rTexPacker. UI/UX is the main concern indeed. (and a simple way to split filmstrip sprite sheets... but one can always go to ImageMagick for that)
Can rTextPacker generate sprite font atlases where every character has the same width, similarly to what is displayed in sprite view? This is important for pixel fonts for ex. to avoid a score bouncing around in game when the numbers change.
Thanks for the feedback. I take note of this feature for next release!
Great tool, I wish we can have something such as "TexUnpacker", Would be nice if we could detect sprites within a sprite sheet, and export data to the formats supported by the app, something like "Atlas Image Data Generator" app do but the interface there is buggy and not user very user friendly.
Implementing such a system is not trivial, it requires some work, many considerations and probably some limitations. For the moment it's out of scope but if I got more resources (time, money) I could consider working on it.
Great tool - enjoying using it so far. One small request though, would it be possible to add the option to toggle on/off texture filtering? When dealing with pixel art the blurring caused by bilinear filtering makes it a little more tricky to work with. Thanks!
Actually, there is a toggle button in the main toolbar just for that...
Oh perfect, I somehow missed that. Thanks!
Is there a quick way to set the origin of a frame (or all frames) to their centres?
I'm afraid there is no such option at this moment, pivot-point setup is manual for required sprites... but I take note for a future version!
Is it possible to make the program, output multiple atlases if the number of sprites overflow the atlases? Then a map can be made to lookup which atlas the sprite belongs too. If source could be provided, I could add the feature myself, but this is closed source. It would be possible to make this feature even just using the binary, but would be easier if it already does this or source is available, even in a limited context. Either way buying this later today.
Maybe in a future but now my resources are very limited to keep improving this tool. I prefer to keep it closed source, it took me thousands of hours of development and I’m trying to monetize a bit all that work.
I am in now way saying you should open source the tool and not be able to monetize it. I simply wish for some way to access the source with purchase, even in a non redistributable limited license manner. I would be more than willing to sign any NDA or pay an extra fee or something, just because it would make my life easier, but if this is not possible, I understand completely.
I would also like to stress I am in no way ungrateful for all the work you do on raylib. It is a wonderful technology. I am using it now and appreciate everything you do. I have already purchased this software and completely understand any limitations you have to impose to insure your ability to make money. The fact you even offer the software for free as use as a web app is commendable from the outset, I have no issues paying you something for a small part of all the work you have done, and the existence of raylib brings me great joy in not having to re-implement many things when I create projects that I do not desire to use giant monolithic engines with. Thanks for everything you do Ray.
I was wondering if it is possible, when exporting the texture, to configure the number of channels per pixel? Specifically, if it is possible to export the texture in grayscale? This feature would be very helpful
keep up the good work
Actually, I considered that option but I decided to keep that image-editing functionality separate from the packaging functionality. You can use rTexViewer to edit the pixel-format of your exported atlas.
There seems to be a bug.
I packed a .png-image with color RGBA(0, 0, 0, 50) and the result was RGBA(0, 0, 0, 10).
Is there something wrong with the alpha values?
Yes, it’s a known issue and has already been reviewed. An updated version will be published soon.
Do you plan on making this a library?
Also is there a way to remove all viewable sprites in the atlas? It'll be useful for fighting games that need a lot of sprites for animation.
What do you mean? There is a clean button on the sprites list to remove all sprites from the atlas.
There can be sprites that have a red border around them that are not on the atlas, is there a way to automatically delete all the viewable sprites (ones without the red border)?
Not for the moment but I take note about it, I can add it in a future but unfortunately not for next release.
Actually most of the functionality of this tool is directly available in raylib. You can use raylib.
Do you have a src-code for this program?
I'm afraid this software is closed source. Why do you need it?
I will answer for them. Because by reusing the code of this editor, you can create a level editor that will be more convenient than the ugly Tiled.
You can check the code of rFXGen, rGuiStyler, rGuiIcons and rIconPacker, they are open source and all my tools use the same base template so the code structure is almost the same. rTexPacker just has specific code to package sprites but that's a few lines of code because it uses stb_rect_pack library.
This is rather impolite to the creator of Tiled.
this os not for mac
Nope, unfortunately I never had a mac to learn how it works and create software for it...
ok sir
Any plans to make this available as a Linux binary?
I'm publishing a new version soon, I'll try to provide a Linux version by then.