[Remote rendering 4.1] Add headless RemoteRenderer and RCA streaming backend

Open

#26 opened on Aug 25, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Active
Tech stack: python
Domain: backend, computer-graphics

Research direction

Trace the RemoteRenderer, RemoteApp, VtkNodePipeline, and VisorRemoteScene entry points described in the issue, starting with the existing local renderer and runtime-state hooks. Break the work into the off-screen renderer, streaming wiring, and coalescing/camera behavior; done means a connecting client receives an initial frame and the tests pass.

Written by the indexing model from the issue text.

Description

technical

📝 Description of the feature

Stand up the server-side rendering path on the backend:

a RemoteRenderer that implements IRenderer against an off-screen vtkRenderWindow (SetOffScreenRendering(1)), writing per-part mutations through the shared VtkNodePipeline and owning camera state directly on the server-side camera (unlike the local path, where the camera lives in the browser).
RemoteApp wires the render window into trame-rca so frames can stream to the client, and complete VisorRemoteScene against the runtime-state hooks from user story 1.2. This includes render coalescing (back to back mutations produce one frame).
This is the largest story in the phase and is expected to break down into several sub-PRs, e.g.
- The off-screen renderer
- the streaming wiring
- coalescing + camera push

Local mode is untouched in this user story; all of this new code is behind the mode flag.

Acceptance Criteria

A connecting client receives an initial frame.
Tests pass

💵 Business Value

No response

🔗 Useful links and references

No response

Dominant language: Python
Stars: 1
Forks: 0
Avg merge: 1d 21h
Merged PRs (30d): 47

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.