@@ -32,41 +32,68 @@ without the need for installing Mono. On
### Set Up a Profile
The first time you run Desert Paint Lab, it will prompt you to make a profile. You may either create a new profile, or import an existing PracticalPaint reactions.txt file.
### Start Testing!
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 | 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
### Slowness
If you are running on a multi-screen system, or a very high-resolution screen, you may find that Desert Paint Lab is rather slow in determining paint reactions. That's because you have a lot of screen real-estate to scan, to look for the Pigment Lab dialog. You can speed up the scanning process by ensuring that your Pigment Lab Dialog is as far to the upper-left of the screen as possible.
### Retina / High-Density Screens
High DPI screens may be displaying the game at something other than a 1:1 game-pixel to screen-pixel ratio. These screens didn't exist, back when Desert Paint Lab was created. The current version now prompts you for your screen resolution when it starts to work around this. If you see a crash when trying to capture a reaction, it's likely because the resolution is incorrect. For example, Snoerr's MacBook Pro has a retina screen with a resolution of 2880x1800. Mono (and therefore DesertPaintLab) detects it as having a resolution of 1440x900. He enters his resolution as 2880x1800 and sets the Game pixel width in screen pixels to 2.
## Mac user FAQ
Q: How do I find my native screen resolution?
A: You can find it by opening up "About this Mac" from the Apple menu and clicking on the "Displays" tab. That should show the screen size and resolution to enter.
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/).