Changeset - 691a41e154ab
[Not reviewed]
Merge default
0 1 0
Jason Maltzen (jmaltzen) - 9 years ago 2015-12-23 21:26:17
jason.maltzen@unsanctioned.net
Merge README updates
1 file changed with 29 insertions and 2 deletions:
README.md
29
2
0 comments (0 inline, 0 general)
README.md
Show inline comments
...
 
@@ -38,16 +38,43 @@ The first time you run Desert Paint Lab,
 
Add two ingredients to your paint bench.  Select those same ingredients in Desert Paint Lab.  Then, with the Pigment Lab dialog unobstructred, select the **Capture** button.  Once you are satisfied with the result, click the **Record** button.  The data will automatically be added to your profile.
 

 
### Clipped?  Huh?
 

 
Occasionally, you will see a warning dialog that informs you that a "Reaction clipped."  That means that one or more of the color components moved outside of the testable range.  This makes it impossible to calculate the reaction from these two ingredients.
 

 
You can solve this by doing a three-way test.  To do this, select a third ingredient that has known reaction values with the two ingredients you are attempting to pair, and which will adjust the color component that was clipping, so that it is no longer doing so.  Combine that with your two ingredients.  In Desert Paint Lab, you'll want to select a known pairing in the first two boxes, and the other ingredient in the third.  Desert Paint Lab can then do all the math to figure out the mystery reaction.
 
You can solve this by doing a three-way test.
 

 
1. In your clipped reaction, let's call your **1st** ingredient **A** and your **2nd** ingredient **B**.
 
1. Select a **non-catalyst** ingredient **C** for which you have already tested **C + A** and **C + B**.  It is OK if there was a reaction in those earlier tests.  Desert Paint Lab can work out the math.
 
1. In Desert Paint Lab, select ingredients as follows:
 
    1. **C**
 
    2. **A**
 
    3. **B**
 
1. Add the ingredients in your Pigment Lab _in exactly that order_.
 
1. Capture.
 
1. Record.
 

 
For clipped reactions, your **C** ingredient should be one that corrects for the clipped color.  Here are some suggested **C** ingredients for clipping correction:
 

 

 
Clip Color  | Clip Direction | Correction | Suggested "C" Ingredient
 
------------|----------------|------------|---------------------------
 
Red         | Low            | +Red       | Carrot (224) or Red Sand (144)
 
Red         | High           | -Red       | Silver Powder (16) or Toad Skin (48)
 
Green       | Low            | +Green     | Earth Light (240) or Copper (192)
 
Green       | High           | -Green     | Red Sand (16) or Silver Powder (16)
 
Blue        | Low            | +Blue      | Earth Light (224) or Copper (192)
 
Blue        | High           | -Blue      | Red Sand (24) or Clay (32) or Carrot (32) or Silver Powder (32)
 

 

 
In many cases, it may be easiest to go back and do these three-way tests after you have finished all of your other testing.
 

 
### Catalysts
 

 
For catalyst to catalyst reaction tests, follow the three-way instructions, as above.
 

 
### Finishing Up
 

 
When you're done testing your reactions, you can either use the built-in Pigment Lab simulator (`Window > Run Simulator`) to experiment with recipes, without dipping into your precious ingredient stocks.  Alternatively, you can export your reactions in PracticalPaint format.
 

 
## Known Issues
 

...
 
@@ -66,7 +93,7 @@ A: You can find it by opening up "About 
 

 
Q: Why not a native Mac app bundle? Why make me use the command line?
 
A: That's in the works, along with a Windows installer that bundles up the GTK# dependencies so you don't have to install that separately.
 

 
## For Developers
 

 
This application was developed using [MonoDevelop](http://www.monodevelop.com/), using the [Stetic GTK UI designer](http://www.monodevelop.com/documentation/stetic-gui-designer/).
 
This application was developed using [MonoDevelop](http://www.monodevelop.com/), using the [Stetic GTK UI designer](http://www.monodevelop.com/documentation/stetic-gui-designer/).
...
 
\ No newline at end of file
0 comments (0 inline, 0 general)