Troubleshooting

Troubleshooting

Common issues and solutions for the Ramses-Fusion plugin.

Connection Issues

"Ramses Client Offline"

• Cause: The plugin cannot communicate with the Ramses Daemon.
• Solution:
  1. Ensure the Ramses Client application is running.
  2. Check that you are logged in within the Ramses Client.
  3. Verify the Port in the Plugin Settings matches the port in the Ramses Client (default is 18185).

Pipeline Errors

"Project Mismatch"

• Cause: You opened a file that belongs to "Project A", but the Ramses Client is currently set to "Project B".

• Solution:
  • Change the active project in the Ramses Client application.
  • Click the context header (the project/shot display at the top of the panel) to refresh.

"Scene Identity Missing"

• Cause: The current composition was saved manually outside of the Ramses-Fusion plugin and lacks metadata.
• Solution:
  • Click Setup Scene or use the Switch Shot wizard to re-register the file in the pipeline.

Render Issues

"Missing Anchor Node"

• Cause: The _PREVIEW or _FINAL Saver nodes were deleted or renamed.
• Solution:
  • Click Setup Scene. This will recreate the missing anchors at the current position in your flow.

"Disconnected Anchor"

• Cause: The _PREVIEW or _FINAL nodes are in the flow but have no input connection.
• Solution:
  • Connect the output of your final tool (e.g., a MediaOut or a Merge node) to the input of the anchor Saver.

"Render is incomplete: found N of M frames"

• Cause: Fusion reported the render as finished, but fewer files landed on disk than the frame range calls for. Usually a full disk, a dropped network share, or a render that errored on a frame partway through.
• Consequence: The publish is aborted deliberately. Nothing was backed up and the database status is unchanged — this is the safety net working, not a plugin fault.
• Solution:
  • Check free space and that the output share is reachable.
  • Open the Fusion console and look for the frame that failed.
  • Re-run the publish. If the count is off by exactly the frames you expect, check that the comp's render range matches the shot's range in Ramses (Sync Project Settings fixes this).

The publish stopped on a validation error

• Cause: The comp does not match the database — resolution, frame rate, range, or a missing/disconnected render anchor.
• Solution: If the dialog offers Fix It (or a ticked checkbox), take it — the plugin repairs the frame range, format, or missing anchors itself and then re-checks. If it stops you a second time, the repair did not take and the remaining finding needs fixing by hand.

UI Issues

The panel is too small or buttons are cut off

• Cause: Fusion's UIManager sometimes fails to calculate the initial height correctly.
• Solution:
  • Toggle one of the section headers (e.g., click [ - ] PROJECT & SCENE) twice. This triggers a layout recalculation and window resize.
  • The section headers exist only in the vertical layout. If you are in the slim horizontal bar, click ⇄ to switch back first.

A plugin update doesn't seem to have taken effect

• Cause: Fusion keeps one Python interpreter alive for the whole session, and modules under lib/ are not reloaded when you reopen the panel.
• Solution: Restart Fusion completely. Closing and reopening the panel is not enough.

"AttributeError: 'NoneType' object has no attribute..."

• Cause: Usually happens if the composition is closed while the plugin is performing an action.
• Solution:
  • Close and reopen the plugin panel.