Changeset - 8815bc2e6f91
[Not reviewed]
default
0 1 0
Jason Maltzen - 12 months ago 2023-12-07 04:50:00
jason@hiddenachievement.com
Update README for Tale 11.
1 file changed with 5 insertions and 1 deletions:
0 comments (0 inline, 0 general)
README.md
Show inline comments
 
# Desert Paint Codex
 

	
 
(Formerly _Desert Paint Lab_)
 

	
 
This is a tool for players to record their [Pigment Laboratory](https://atitd.wiki/tale10/Pigment_Laboratory)
 
ingredient reactions in [A Tale in the Desert](http://www.atitd.com/).
 

	
 
### Latest Releases
 

	
 
You can find the latest releases at https://desert-paint-lab.malkyne.org/
 

	
 
### Features
 

	
 
* Scans your screen for the Pigment Lab reaction values, without any math, measuring, or manual number entry.
 
* Warns you when a reaction clipped outside of readable range.
 
* Supports multiple character profiles.
 
* Can export to [PracticalPaint](http://www.atitd.org/wiki/tale7/File:PracticalPaint.Zip) data format.
 
* Includes simulator for experimenting with recipes without spending ingredients.
 
* Includes a recipe generator
 

	
 
## Tale 11
 

	
 
* Updated for UI changes that were preventing detection of colors clipping above the maximum red/green/blue.
 

	
 
## Tale 10
 

	
 
* Desert Paint Lab is now Desert Paint Codex, and has a whole new UI, for Tale 10.
 
* Untested reactions are now kept in a list to the left, so you can immediately see what still needs testing.
 
* The application has not yet been updated for ATITD's new UI.  This will be coming soon.
 
* The application is updated for ATITD's new UI.
 

	
 

	
 
## Tale 9
 

	
 
* New papyrus texture in interfaces
 
* Earth Light was replaced by Falcon's Bait mushrooms. Practical Paint still uses the name EarthLight internally, so the data files still use that name here as well.
 
* macOS is now a 64-bit app. Windows remains 32-bit due to incompatibilities with the UI library.
 
* macOS build does not support Catalina (is not notarized)
 

	
 
### Known issues
 

	
 
* A batcher installed on a Pigment Lab will prevent finding the right part of the screen with the resulting color.
 

	
 

	
 
## Directions
 

	
 
### Download Desert Paint Lab
 

	
 
You can always find the available downloads, on [the download page](https://desert-paint-lab.malkyne.org/).
 

	
 
Desert Paint Codex now uses Net Core, instead of Mono.  The package should come with everything you need to make it work.
 

	
 

	
 
### 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 Pigment Lab.  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.
 

	
 
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:
0 comments (0 inline, 0 general)