Questions

Docs · Questions

LOPsInstallation

How do I fix LOPs installation errors like 'LiteLLM installation failed'?

Problem

The LOPs installation process fails, often showing a “LiteLLM installation failed” error, getting stuck in a loop, or failing silently without clear feedback.

Core Solutions

  1. Use a Recommended TouchDesigner Version: For the most reliable installation, use an official 2023 TouchDesigner build. Once LOPs is successfully installed, you can open and use your project in a 2025 build.
  2. Use a Space-Free Installation Path: This is a critical step. The installation script can fail if the folder path contains spaces (e.g., C:\Users\My Name\Desktop\LOPS).
    • Fix: Create a simple, root-level folder like C:\LOPS or D:\TD_Projects\LOPS and select it as your installation directory.

How to Debug Your Installation

If the installation still fails, you can diagnose the issue using the built-in Python Manager:

  1. Open the OP Create Dialog in TouchDesigner.
  2. Find the dot_lops container and select the second option to open the Python Manager.
  3. In the Python Manager’s parameters, click the Print Venv Report pulse.
  4. Check the output in the Textport. The report must show that you are using Python 3.11.9. If it shows a different version, it is the likely cause of the failure.

Specific Dependency Errors

If the log shows errors with specific packages, you may need to install them manually. Use the Python Manager to run these commands:

  • For RAGIndex or Ollama errors:
    pip install llama-index-embeddings-ollama
  • For MCP Server errors:
    pip uninstall fastmcp -y
    pip install fastmcp==2.8.0
    pip uninstall mcp -y
    pip install mcp==1.9.4

Post-Installation Issues

  • API Keys: All API keys (OpenAI, OpenRouter, Groq, etc.) are entered in the ChatTD operator’s parameter pages.
  • “Model Not Found” Error: If you see an error for “Model not found or mapped by liteLLM,” this is a known bug in the model-fetching logic and not an installation error. A fix is planned for a future release.

External Resources