Logs & Troubleshooting
When working with procedural systems in Infinity Creator, errors can occur due to invalid inputs, misconfigured nodes, or performance limitations. The Logs Panel provides real-time diagnostics to help identify and resolve these issues efficiently.
1. Understanding the Logs Panel
The Logs Panel captures and displays issues related to node execution, data flow, and performance.
How to Open the Logs Panel
- Open the Views in the Header Menu.
- Select Logs to enable the panel.
- The panel appears below the Node Graph (hidden by default).
- Resize or dock it for better visibility.
Tip: Always check the logs when unexpected behavior occurs in a procedural system.
Debugging Performance Issues
Issue: "Warning: Node execution taking too long"
If a systems execution has hung or not completed in a reasonable amount of time, the user should terminate the Infinity Creator.
Example:
- A large terrain generator may take too long if the resolution is too high.
2. Best Practices for Debugging Errors
- Check Logs First – The first step in debugging should always be reviewing the logs.
- Validate Data Flow – Ensure that all inputs and outputs are correctly linked.
- Minimize Complexity – Start with a small subset of nodes before expanding the graph.
- Test Changes Iteratively – Modify one parameter at a time and check results.
Tip: When encountering multiple errors, resolve them one by one starting from the top of the log list.
3. Resolving Common Errors Quickly
| Problem | Possible Cause | Solution |
|---|---|---|
| No procedural output | Disconnected node | Ensure all required inputs are connected |
| Node fails to execute | Invalid parameters | Adjust values in Inspector Panel |
| Object appears broken | Incorrect scaling | Check transform values and adjust scale |
| System is slow | High computational load | Reduce system complexity |
Example:
- A blank output in the Visualizer might mean a Mesh Deform node has no input Mesh.