Hey thanks for this great tool! One small problem though. For me, none of the encryption options are working. I've tried both through the GUI and CLI.
Interestingly, it appears to generate the exact same file with different passwords used for encryption. See the md5sum of an rres file created with two different passwords
Actually rres.h is engine-agnostic, it only depends on C standard library. rres-raylib.h is an specific rres implementation for raylib library; also intended to be a reference for other implementations for other libraries/engines. With rres.h it’s possible to load .rres resources, independently of raylib…
I’m afraid I don’t understand the request but feel free to open an issue on rres repo for further review.
I tried to use the online tool, but I noticed that no matter what I do I always get at least 4x larger overall file size. Could this be a bug? For example, I have 3 files all of them is about 3mb, the resulted rres however is 20mb.
I depends on the type of files and the compression selected but it could happen. rrespacker processes the input files to extract only required data, i.e that implied decompressing images to extract pixel data. If you choose the embedding as RAW option, size should be approximately the same as input files.
I'm sorry to hear that! I'll join your patreon and hope can contribute to a potential Mac purchase someday :) Thank you for all your work on Raylib. It's a real joy to use.
Thank you very much! Actually I’m already open-sourcing some of my tools to allow other users to review/test/compile them for other platforms. Technically they should compile for Windows, Linux, macOS, RPI, FreeBSD and other OSs with no problem but it requires some testing. Maybe in the future I will also open source this one. Glad you like raylib! Hope you enjoy it! :)
← Return to tool
Comments
Log in with itch.io to leave a comment.
Hey thanks for this great tool! One small problem though. For me, none of the encryption options are working. I've tried both through the GUI and CLI.
Interestingly, it appears to generate the exact same file with different passwords used for encryption. See the md5sum of an rres file created with two different passwords
See below:
rrespacker --output example.rres ~/video-prep/zero.png@zero.png,0,0,0,40,73 --password 1234567890123456
INFO: Input filepath to process: /home/xentropy/video-prep/zero.png@zero.png
RRES: Start building file: example.rres
RRES: Start Building Project (1 files)
RRES: [001/001] Processing file: /home/xentropy/video-prep/zero.png
RRES: Input File: zero.png
RRES: Output Resource: IMGE
RRES: > id: 0xe0007faa
RRES: > compType: QOI (40)
RRES: > cipherType: XChaCha20 (73)
RRES: > baseSize: 331796
RRES: > packedSize: 45477 (13%)
RRES: > nextOffset: 0
RRES: > CRC32: 0x0530f1e0
RRES: CDIR: Entry id: 0xe0007faa | Offset: 0x00000010 | Filename: zero.png (len: 12)
RRES: CDIR: Offset: 0000b1c5
RRES: Chunks count: 1
RRES: Package built successfully: example.rres
md5sum example.rres
036c9ef7020071b87855fd4ee74ec53c example.rres
rrespacker --output example.rres ~/video-prep/zero.png@zero.png,0,0,0,40,73 --password test23
INFO: Input filepath to process: /home/xentropy/video-prep/zero.png@zero.png
RRES: Start building file: example.rres
RRES: Start Building Project (1 files)
RRES: [001/001] Processing file: /home/xentropy/video-prep/zero.png
RRES: Input File: zero.png
RRES: Output Resource: IMGE
RRES: > id: 0xe0007faa
RRES: > compType: QOI (40)
RRES: > cipherType: XChaCha20 (73)
RRES: > baseSize: 331796
RRES: > packedSize: 45477 (13%)
RRES: > nextOffset: 0
RRES: > CRC32: 0x0530f1e0
RRES: CDIR: Entry id: 0xe0007faa | Offset: 0x00000010 | Filename: zero.png (len: 12)
RRES: CDIR: Offset: 0000b1c5
RRES: Chunks count: 1
RRES: Package built successfully: example.rres
md5sum example.rres
036c9ef7020071b87855fd4ee74ec53c example.rres
It’s good tool but library is complex to use.
The rres-raylib.h depend of ress.h .
And ress.h is make for raylib.h .
So why can you create a limited version of ress.h with focus to loading asset from .ress .
Actually rres.h is engine-agnostic, it only depends on C standard library. rres-raylib.h is an specific rres implementation for raylib library; also intended to be a reference for other implementations for other libraries/engines. With
rres.hit’s possible to load.rresresources, independently of raylib…I’m afraid I don’t understand the request but feel free to open an issue on rres repo for further review.
I tried to use the online tool, but I noticed that no matter what I do I always get at least 4x larger overall file size. Could this be a bug? For example, I have 3 files all of them is about 3mb, the resulted rres however is 20mb.
I depends on the type of files and the compression selected but it could happen.
rrespackerprocesses the input files to extract only required data, i.e that implied decompressing images to extract pixel data. If you choose the embedding as RAW option, size should be approximately the same as input files.Is a Mac build an option by any chance for the standalone download?
I’m afraid it’s not possible because I don’t have a mac to build and test the program properly. Unfortunately my resources are very limited… :(
I'm sorry to hear that! I'll join your patreon and hope can contribute to a potential Mac purchase someday :) Thank you for all your work on Raylib. It's a real joy to use.
Thank you very much! Actually I’m already open-sourcing some of my tools to allow other users to review/test/compile them for other platforms. Technically they should compile for Windows, Linux, macOS, RPI, FreeBSD and other OSs with no problem but it requires some testing. Maybe in the future I will also open source this one. Glad you like raylib! Hope you enjoy it! :)
Hi! An experimental macOS version has been added! It could require some additional work, please, let me know if it works for you.