Troubleshooting¶
Comprehensive guide to diagnosing and resolving BlenderForge issues.
Table of Contents¶
- Quick Diagnostic Checklist
- Connection Issues
- AI Client Issues
- Installation Issues
- Asset Integration Issues
- AI Features Issues
- Performance Issues
- Error Messages Reference
- Debug Mode
- Log Files
- Platform-Specific Issues
- Getting Help
Quick Diagnostic Checklist¶
Run through this checklist before diving into specific issues:
1. Verify Installation¶
# Check BlenderForge is installed
blenderforge --version
# If not found, try:
python -m blenderforge --version
pip show blenderforge
2. Check Blender Setup¶
- Blender is running
- BlenderForge addon is enabled (
Edit→Preferences→Add-ons) - BlenderForge panel is visible (Press
N, find tab) - Server status shows "Connected"
3. Verify AI Client¶
- Config file exists and has valid JSON
- AI client has been restarted after config change
- BlenderForge appears in available tools
4. Test Connection¶
Ask your AI: "What objects are in my Blender scene?"
Connection Issues¶
"Could not connect to Blender"¶
Symptoms: - AI assistant reports connection failure - Tools return timeout errors - "Connection refused" messages
Solutions:
Solution 1: Verify Blender is Running¶
Solution 2: Check Addon is Enabled¶
- Go to
Edit→Preferences→Add-ons - Search for "BlenderForge"
- Ensure the checkbox is checked
- If missing, reinstall the addon
Solution 3: Start the Server¶
- Press
Nto open the sidebar in Blender - Go to BlenderForge tab
- Click "Connect to MCP server"
- Status should show "Connected"
Solution 4: Check Port Configuration¶
- Default port is 9876
- Verify the same port is set in:
- Blender's BlenderForge panel
- Your MCP configuration (if using
BLENDER_PORTenv var)
# Check if something else is using the port
# macOS/Linux
lsof -i :9876
# Windows
netstat -ano | findstr 9876
Solution 5: Check Firewall¶
- BlenderForge only uses localhost connections
- Some firewalls block localhost (
127.0.0.1) - Allow connections to
127.0.0.1:9876
"Connection refused"¶
Symptoms: - Error message contains "connection refused" - Tools fail immediately without timeout
Solutions:
Solution 1: Restart the Connection¶
- In Blender's BlenderForge panel, click "Disconnect"
- Wait 2-3 seconds
- Click "Connect to MCP server"
Solution 2: Kill Stale Processes¶
# macOS/Linux - Find and kill process on port 9876
lsof -i :9876
kill <PID>
# Windows
netstat -ano | findstr 9876
taskkill /PID <PID> /F
Solution 3: Change Port¶
If port 9876 is persistently problematic: 1. In Blender panel, change port to 9877 2. Update your MCP config:
{
"mcpServers": {
"blenderforge": {
"command": "blenderforge",
"env": { "BLENDER_PORT": "9877" }
}
}
}
"Timeout waiting for Blender"¶
Symptoms: - Tools start but never complete - Error after 30-60 seconds
Solutions:
Solution 1: Simplify Operations¶
Solution 2: Check Blender Responsiveness¶
- Click in Blender's viewport
- If Blender is frozen, wait for it to recover or restart
Solution 3: Increase Timeout¶
Or in MCP config:
{
"mcpServers": {
"blenderforge": {
"command": "blenderforge",
"env": { "BLENDER_TIMEOUT": "120000" }
}
}
}
Solution 4: Check System Resources¶
- High RAM usage can slow Blender
- Close unnecessary applications
- Check for runaway processes
AI Client Issues¶
"Tools not appearing in AI assistant"¶
Symptoms: - AI doesn't recognize BlenderForge commands - No Blender tools in tools list - AI says "I don't have access to BlenderForge"
Solutions:
Solution 1: Restart AI Client¶
MCP servers load at startup. You must: 1. Close the AI client completely 2. Wait a few seconds 3. Reopen the AI client
Solution 2: Verify Config File Location¶
| Client | Config Location |
|---|---|
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json |
| Claude Desktop (Linux) | ~/.config/Claude/claude_desktop_config.json |
| Claude Code | ~/.claude.json |
| VS Code | settings.json → github.copilot.chat.mcp.servers |
| Cursor | Settings → MCP tab |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Zed | ~/.config/zed/settings.json |
| Continue.dev | ~/.continue/config.yaml |
Solution 3: Validate JSON Syntax¶
Common JSON errors: - Missing commas between properties - Trailing commas (not allowed in JSON) - Unquoted strings - Wrong bracket types
Use a JSON validator: https://jsonlint.com/
Solution 4: Check Command Path¶
# Verify blenderforge is in PATH
which blenderforge # macOS/Linux
where blenderforge # Windows
# If not found, use full path in config:
{
"mcpServers": {
"blenderforge": {
"command": "/usr/local/bin/blenderforge"
}
}
}
# Or use Python module:
{
"mcpServers": {
"blenderforge": {
"command": "python",
"args": ["-m", "blenderforge"]
}
}
}
Solution 5: Check AI Client Logs¶
Most clients have developer logs showing MCP errors:
- Claude Desktop:
~/Library/Logs/Claude/(macOS) - VS Code: Help → Toggle Developer Tools → Console
- Cursor: Help → Toggle Developer Tools → Console
"Tool calls fail silently"¶
Symptoms: - AI says it will use a tool but nothing happens - No visible error message - Blender doesn't respond
Solutions:
Solution 1: Check Blender Console¶
- Windows:
Window→Toggle System Console - macOS/Linux: Launch Blender from terminal:
Solution 2: Enable Debug Logging¶
Solution 3: Test Direct Connection¶
Ask AI to run a simple test:
"MCP server failed to start"¶
Symptoms: - AI client shows server startup error - BlenderForge never connects
Solutions:
Solution 1: Check Python Environment¶
# Verify Python version
python --version # Should be 3.10+
# Check if blenderforge is importable
python -c "import blenderforge; print('OK')"
Solution 2: Reinstall BlenderForge¶
Solution 3: Check Dependencies¶
Installation Issues¶
"pip: command not found"¶
Solutions:
# Try pip3
pip3 install blenderforge
# Or use Python module
python -m pip install blenderforge
python3 -m pip install blenderforge
"Permission denied during installation"¶
Solutions:
# Install for user only
pip install --user blenderforge
# Or use virtual environment
python -m venv venv
source venv/bin/activate # macOS/Linux
venv\Scripts\activate # Windows
pip install blenderforge
"blenderforge: command not found" after installation¶
Cause: pip installed to a directory not in PATH
Solutions:
# Find installation location
pip show blenderforge
# Add to PATH (example for user install)
# macOS/Linux - add to ~/.bashrc or ~/.zshrc:
export PATH="$HOME/.local/bin:$PATH"
# Or run as module:
python -m blenderforge
Python version incompatibility¶
Symptoms: - SyntaxError during import - ModuleNotFoundError
Solution:
# Check Python version
python --version
# BlenderForge requires Python 3.10+
# Install newer Python if needed
Asset Integration Issues¶
"PolyHaven not working"¶
Symptoms: - Can't search or download PolyHaven assets - "PolyHaven not enabled" errors
Solutions:
- Enable PolyHaven Integration:
- Open BlenderForge panel in Blender
-
Check Use PolyHaven checkbox
-
Check Internet Connection:
- PolyHaven requires network access
-
Test: Visit polyhaven.com in browser
-
Check API Availability:
- PolyHaven API:
https://api.polyhaven.com -
If API is down, wait and try later
-
Update BlenderForge:
"Sketchfab not working"¶
Symptoms: - Authentication failures - "Invalid API key" errors
Solutions:
- Verify API Key:
- Log into sketchfab.com
- Go to Settings → API
- Copy the API token
-
Re-enter in BlenderForge panel
-
Check API Key Format:
- Should be a long alphanumeric string
-
No spaces or special characters
-
Check Model Permissions:
- Not all models are downloadable
- Use
downloadable: truefilter - Check license requirements
"Hyper3D/Hunyuan3D generation fails"¶
Symptoms: - Generation starts but never completes - Authentication errors - Credit exhausted messages
Solutions:
- Verify Credentials:
- Double-check API key/secret
-
Ensure account is active
-
Check Credit Balance:
- Hyper3D uses credits
- Free trial may have limits
-
Check account dashboard
-
Check Generation Status:
- AI generation takes 15-60+ seconds
- Use status polling commands
-
Don't cancel too early
-
Check Rate Limits:
- Some services have request limits
- Wait between generation requests
AI Features Issues¶
"AI Material Generator not working"¶
Symptoms: - Material generation fails - No material created in Blender
Solutions:
- Check Object Selection:
- Material generator may require an object to be selected
-
Or specify target object name
-
Check Blender Console:
- Look for Python errors during material creation
-
Common: missing node connections
-
Verify Scene Setup:
- Ensure you're in a 3D scene (not compositor, etc.)
- Check Blender is in Object mode
"Natural Language Modeling fails"¶
Symptoms: - Object not created as expected - Wrong position/size/color
Solutions:
-
Use Clearer Descriptions:
-
Check Units:
- Blender uses meters by default
-
Specify units explicitly when needed
-
One Operation at a Time:
"Scene Analyzer returns empty results"¶
Symptoms: - No analysis returned - Generic or unhelpful feedback
Solutions:
- Ensure Scene Has Objects:
- Analyzer needs content to analyze
-
Add some objects first
-
Check Scene Complexity:
- Very simple scenes may not trigger detailed analysis
- More complex scenes get better feedback
"Auto-Rig not finding mesh"¶
Symptoms: - "Mesh not found" error - Armature not created
Solutions:
- Verify Mesh Name:
- Use exact mesh object name
-
Check Object name vs Data name in Blender
-
Check Mesh Type:
- Must be a mesh object (not curve, text, etc.)
-
Humanoid rig needs humanoid-like mesh
-
Mesh Requirements:
- Mesh should be at origin or specify location
- Should have appropriate topology for rigging
Performance Issues¶
"Blender becomes slow/unresponsive"¶
Symptoms: - Blender UI freezes - High memory usage - Operations take too long
Solutions:
- Reduce Operation Complexity:
- Download smaller textures (2K instead of 8K)
- Import simpler models
-
Process fewer objects at once
-
Manage Memory:
- Close unnecessary panels
- Purge orphan data:
File→Clean Up→Purge All -
Restart Blender periodically
-
Optimize Scene:
- Use simpler materials for preview
- Lower subdivision levels
- Hide complex objects when not needed
"MCP server uses high CPU"¶
Symptoms: - High CPU from blenderforge process - System slowdown
Solutions:
- Avoid Polling Loops:
- Don't continuously check AI generation status
-
Wait between status checks
-
Restart MCP Server:
- Restart your AI client
-
This restarts the MCP server process
-
Check for Stuck Operations:
- Kill and restart if an operation is hanging
"Large scenes cause timeouts"¶
Solutions:
-
Increase Timeout:
-
Work in Sections:
- Process parts of the scene separately
-
Use collections to organize
-
Simplify Queries:
- Get info about specific objects, not entire scene
- Use filters to reduce data
Error Messages Reference¶
Python/Module Errors¶
"ModuleNotFoundError: No module named 'mcp'"¶
"ImportError: cannot import name 'FastMCP'"¶
"ModuleNotFoundError: No module named 'blenderforge'"¶
Connection Errors¶
"JSONDecodeError" in logs¶
Cause: Malformed messages between server and Blender
Solution: 1. Restart both Blender and AI client 2. Check Blender console for errors 3. Update to latest BlenderForge version
"Permission denied" when starting server¶
Cause: Port in use or permission issue
Solution:
"Address already in use"¶
Blender Errors¶
"Context is incorrect"¶
Cause: Operation called in wrong Blender context
Solution: Ensure proper mode (Object/Edit) and selection
"Operator poll failed"¶
Cause: Blender operator prerequisites not met
Solution: Check object selection, mode, and scene state
Debug Mode¶
Enable Debug Logging¶
# Environment variable
export BLENDERFORGE_DEBUG=true
blenderforge
# Or in MCP config
{
"mcpServers": {
"blenderforge": {
"command": "blenderforge",
"env": { "BLENDERFORGE_DEBUG": "true" }
}
}
}
Capture Debug Output¶
# Save logs to file
blenderforge 2>&1 | tee blenderforge_debug.log
# Or redirect stderr
blenderforge 2>blenderforge_error.log
View Real-time Logs¶
Log Files¶
Log File Locations¶
| Component | Location |
|---|---|
| BlenderForge (with debug) | stderr output |
| Blender Console | System console window |
| Claude Desktop (macOS) | ~/Library/Logs/Claude/ |
| VS Code | Developer Tools → Console |
Blender Console Access¶
Windows:
macOS:
Linux:
Collecting Logs for Bug Reports¶
# 1. Enable debug mode
export BLENDERFORGE_DEBUG=true
# 2. Capture output
blenderforge 2>&1 | tee debug.log
# 3. Reproduce the issue
# 4. Include debug.log in bug report
Platform-Specific Issues¶
macOS¶
"Operation not permitted"¶
- Check System Preferences → Security & Privacy
- Allow terminal/Python access
"blenderforge: command not found" with Homebrew Python¶
# Add Homebrew bin to PATH
export PATH="/opt/homebrew/bin:$PATH"
# Or
export PATH="/usr/local/bin:$PATH"
Blender from App Store Issues¶
- App Store version may have sandboxing restrictions
- Download from blender.org instead
Windows¶
"Python not found"¶
- Reinstall Python with "Add to PATH" checked
- Or add manually:
"Access denied" errors¶
- Run Command Prompt as Administrator
- Check antivirus isn't blocking
Path Issues¶
Linux¶
Snap/Flatpak Blender Restrictions¶
- Snap and Flatpak have sandboxed file access
- May not be able to access all directories
- Consider official tarball from blender.org
Permission Issues¶
# Check addon directory permissions
ls -la ~/.config/blender/4.0/scripts/addons/
# Fix if needed
chmod 755 ~/.config/blender/4.0/scripts/addons/
"externally-managed-environment" Error¶
# Use virtual environment
python -m venv venv
source venv/bin/activate
pip install blenderforge
# Or use pipx
pipx install blenderforge
Getting Help¶
Before Asking for Help¶
- Check this troubleshooting guide
- Search existing issues: GitHub Issues
- Enable debug logging and collect logs
- Try to reproduce with minimal setup
Creating a Bug Report¶
Include the following information:
**Environment:**
- OS: [e.g., Windows 11, macOS 14.0, Ubuntu 22.04]
- Python version: [output of `python --version`]
- Blender version: [e.g., 4.0.2]
- BlenderForge version: [output of `blenderforge --version`]
- AI client: [e.g., Claude Desktop, VS Code + Copilot]
**Description:**
[What you were trying to do]
**Expected behavior:**
[What you expected to happen]
**Actual behavior:**
[What actually happened]
**Steps to reproduce:**
1. [First step]
2. [Second step]
3. ...
**Error messages:**
[Copy any error messages]
**Debug logs:**
[Attach or paste debug log output]
Contact Channels¶
- GitHub Issues: Report bugs
- GitHub Discussions: Ask questions