Testers Wanted: Color Binning Tool 0.2.30.1

SCREENSHOTS
Downloaded 5,040 times 1,693 Thanks 179 Favourited 239,687 Views
 Say Thanks!
  Featured Upload!   This is a featured upload! It showcases the best talent and creativity available on MTS and in the community.
Uploaded: 28th Apr 2006 at 8:14 PM
Updated: 27th Nov 2013 at 10:20 PM by Nysha
Color Binning Tool

The color binning tool is a custom plugin for SimPE 0.63+

Its purpose is to change custom hair packages so that custom hair recolors appear in the standard color bins.

It was designed to be easy to use: on each standard color tab, you can load a hair package file; after you load the four packages into their respective bins, you can save the result.

There is no need to edit any PropertySet, as the binning logic is already done for you.

More information and some tutorials can be found in the plugin's website: http://theos.chewbakkas.net/tools/c...nning-tool.html


Installation
- Extract the file theos.gbct.plugin.dll
- Copy it into SimPE's Plugins folder, which in a default installation is at C:\Program Files\SimPE\Plugins
- Run SimPE and verify that you have a menu item named "Color Binning Tool" under SimPE's Tools menu.


Basic Usage
After the plugin is installed, start SimPE.

On the Tools menu, click on the "Color Binning Tool" item, and the plugin's main window should appear. Initially, the "Black" color tab is selected by default.

Use the "Package" menu or the context menu to load a package file into the selected tab. Repeat this process for the other tabs (Brown, Blond and Red).

You can select which age groups you wish to keep or remove on each color tab. You must pay special attention to the fact that a properly binned hair should have only one elder (grey) recolor, so you must choose carefully one elder recolor out of the four available.

On most cases you can ignore the Grey and Custom tabs, so you may proceed to review the package options (available in the menu Package->Options), and finally save the resulting package files.


Credits
I would like to thank to everyone that contributed to this project, and in particular to Motoki, for giving the momentum that started this project; Pinhead, whose invaluable knowledge put the code right on track again; and of course all the folks at MATY that were willing to test the plugin on its early stages.