CFC and CFC GUI have been updated to 0.60 and 0.60.35 respectively. CFC runtime files have been updated.
- Support for new filenames (and categories) used in TF3D v2.5+
- Support for new file formats (read only, "replace" write is always in old format) used in TF3D v2.5+
- Support for new compressed formats that correspond to the new formats mentioned above
- If you are using this with 2.5, please do read the 2.5 specific notes!
- At this time I STRONLY recommend patching Manila files manually instead of using the auto-patching! See the tech thread referenced below.
Update June 5, 2009
CFC and CFC GUI have been updated to 0.55 and 0.55.25 respectively. The CFC runtime files have not been updated.
- Better compression ratio (backwards compatible with old runtime)
- UltraHQ en/de-coding support (CFC)
- "Patch Manila on device" function has been improved to work-around the issue of Manila no longer starting that some people have (CFC-GUI)
Update April 20, 2009
CFC GUI v0.50 has been released! LOTS of new features! Also updated CFC runtime (for on the device) to 0.50.
Deployment of CFC 0.50 is needed for UltraHQ background images. "Use Device->Patch Manila on device" to deploy new version to device. Note that CFC Live Patch has been discontinued in favor of this function.
Also, a patch to xboxmod's TF3Dv2-VGA is needed. Can be deployed to device with "TF3Dv2->Deploy xboxmod TF3Dv2-VGA background fix" option. The file in question is also attached to this post ( 2a3d01cc_manila ).
For chefs: see the tech reference thread for updated runtime files or use the "Tools->Patch Manila" function.
Update Feb 26, 2009
CFC and CFC GUI have been updated to 0.46.15. Fixed an issue with PNGs without alpha channel.
Update Jan 15, 2009
CFC Live Patch 0.45.01 has been released. You can run this tool on your phone to make your current Manila installation compatible with CFC compression.
See this post.
CFC GUI is a Manila3D image tool, somewhat like Manila Editor, but better on some fronts.
Technical / reference thread
CFC command line version, full history / progress, complete technical documentation of all relevant file formats and how to en/decode them.
I do not need your donations to be able to buy my smokes, beers, pizza's, kebabs or phones - though they certainly help! However, nothing shows appreciation like a donation, and encourages people to continue developing and implementing feature requests. If you are a themer actively taking donations for your work, a donation would even be fair, instead of just nice.
Do not underestimate just how much time and research goes into many of the things posted on XDA. Donate something to someone (not necessarily me) or even XDA itself, don't be a cheapskate. (Yes I donate time, effort and funds myself to various projects, more than I get back!)
Things you should know
- RTFM. It will be a few posts down from here. Failure to RTFM will give you 7 years bad luck.
- The tool is called CFC and supports CFC compression, but you can also "not do" that. It's optional. Do note that not all ROMs and TF3D packages support CFC compression (yet).
- CFC GUI uses version notation of Z.XX.YY, where XX is the CFC-core version shared with the command line CFC program, and YY is the version of the GUI.
CFC is the tool I originally built to assist me with some things when I ported TF3D to QVGA. At first, I was severely annoyed with the size of TF3D, which lead me to implement extra lossless compression (as it turns out, Manila images compress very well). You will not be surprised to learn that CFC stands for "Chainfire's Compression" Unexpectedly, but not completely surprisingly, the compression actually made TF3D faster.
I was however not content with this, and thus wanted to scale images down to QVGA size. Not content with Manila Editor's image quality, I figured out how to do this with much better quality using an ATI tool: The Compressonator. This however required a lot of mucking with different texture formats and the conversions between those, which are all things that could be done with the CFC tool. A lot of things were figured out, and the complete reference can be found in the technical/reference counterpart of this thread.
Now, 3 months after all that, myself and D-MAN666 (one of the people originally behind Manila Editor) have finally figured out the complete QTC format, and I decided to create my own encoder/decoder. Both encoding and decoding quality easily beats Manila Editor, and rivals The Compressonator (but a lot less hassle!).
(< 0.60 : 12497 downloads)