Running Engine Analysis
Open a Game or Position
Load a game from your database, open a PGN file, or set up a position on the analysis board.
Configure Analysis Settings
Adjust engine parameters:
- Threads: Number of CPU cores to use (more = faster analysis)
- Hash: Memory allocated for the engine (larger = better)
- MultiPV: Number of best lines to show simultaneously (1-5)
- Depth: How deep the engine searches (higher = slower but more accurate)
Understanding Evaluations
Evaluation Bar
The evaluation bar on the side of the board shows:- White advantage: Bar favors White (positive scores)
- Black advantage: Bar favors Black (negative scores)
- Equal: Centered position (around 0.00)
Centipawn Values
- Score Ranges
- Material Equivalents
| Score | Interpretation |
|---|---|
| 0.00 | Equal position |
| +0.50 | Slight White advantage |
| +1.50 | Clear White advantage |
| +3.00 | Winning advantage for White |
| +6.00+ | Decisive advantage |
| -0.50 | Slight Black advantage |
| -1.50 | Clear Black advantage |
| -3.00 | Winning advantage for Black |
| -6.00+ | Decisive advantage |
Mate Scores
When the engine finds a forced checkmate:- M5: Checkmate in 5 moves
- M1: Checkmate in 1 move (immediate mate)
- -M3: Black has checkmate in 3 moves
The number indicates moves (full moves, not half-moves/plies). “M5” means 5 moves for the side to move.
Viewing Multiple Lines (MultiPV)
MultiPV shows alternative best moves:Higher MultiPV values (4-5) can significantly slow down analysis, especially on weaker hardware.
Analysis Features
Evaluation Listener
The evaluation listener automatically:- Updates the eval bar as you navigate moves
- Shows the engine’s top move with an arrow on the board
- Displays the principal variation in the analysis panel
- Highlights blunders, mistakes, and inaccuracies
Move Annotations
Analysis can automatically annotate moves:- !! Brilliant move
- ! Good move
- !? Interesting move
- ?! Dubious move
- ? Mistake (evaluation drop of ~1.00)
- ?? Blunder (evaluation drop of ~2.00+)
Variation Tree
Explore different move options:- Main line: The actual game played
- Variations: Alternative moves you or the engine suggest
- Sub-variations: Variations within variations
- Click any move to jump to that position
- Right-click to promote a variation to the main line
- Delete variations you don’t need
Engine Management
Adding Engines
Obsidian Chess Studio supports any UCI-compatible engine:Add Engine
Click Add Engine and locate the engine executable:
- Windows:
stockfish.exeor other.exefile - macOS/Linux: Stockfish binary or other UCI engine
Configure Engine
Set engine-specific options:
- Default threads and hash
- Engine-specific parameters (if supported)
Switching Engines
You can switch between engines during analysis:- Each engine may have different playing styles
- Useful for comparing evaluations
- Some engines specialize in certain positions (tactical vs. positional)
Deep Analysis Techniques
Cloud Analysis
For critical positions, you can:- Copy the FEN (position notation)
- Paste into Lichess Analysis Board or chess cloud engines
- Get multi-engine consensus or deeper analysis
Analyzing Critical Moments
Identify Key Positions
Identify Key Positions
Look for:
- Large evaluation swings (mistakes/blunders)
- Complex tactical positions
- Critical endgame positions
Time Control Analysis
Time Control Analysis
Review positions where you were in time trouble:
- Did you make mistakes under time pressure?
- Were there simpler winning moves?
- Could you have simplified earlier?
Opening Preparation
Opening Preparation
Analyze your opening games:
- Find where you deviated from theory
- Identify weak moves in your repertoire
- Build better preparation lines
Annotation Workflow
Manual Annotations
Add your own analysis:Combining Engine and Manual Analysis
Best practice:- Run engine analysis first
- Review engine lines and understand why moves are good/bad
- Add your own explanations in comments
- Draw arrows for key tactical ideas
- Create variations for instructive alternatives
- Save the fully annotated game
Performance Optimization
Adjust Threads
Use fewer threads on older computers to avoid lag. Modern CPUs with 8+ cores can use 4-6 threads.
Limit Depth
For casual analysis, depth 18-22 is sufficient. Deeper analysis (25+) is slower but more accurate.
Reduce MultiPV
MultiPV 1-2 is faster. Use higher values only when exploring multiple options.
Increase Hash
More hash memory (512MB-2GB) improves analysis speed and accuracy on powerful machines.
Troubleshooting
Engine Not Starting
- Verify the engine path is correct in Settings
- Ensure the engine file has execute permissions (macOS/Linux)
- Check engine logs for error messages
- Try a different UCI engine
Slow Analysis
- Reduce threads if CPU is maxed out
- Lower MultiPV to 1 or 2
- Close other applications using CPU/memory
- Consider upgrading to a faster engine (newer Stockfish versions)
Inconsistent Evaluations
- Different engines may evaluate differently
- Increase depth for more stable evaluations
- Some positions are genuinely unclear to engines
- Compare with cloud engines for complex positions
Best Practices
Start with Engine Overview
Run the engine through the entire game quickly to identify critical moments.
Deep Dive on Key Positions
Spend more time analyzing positions where the evaluation changed significantly.
Understand, Don't Memorize
Don’t just copy engine moves. Understand the plans and ideas behind them.
Compare Your Thinking
Before checking the engine, analyze the position yourself. Then see how your analysis compares.
