[Remote rendering 3.2] Camera state persistence and sync-back
@LKasianAnsys ci sta già lavorando.
Dal 3/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
📝 Description of the feature
Intent: give the server a persistent record of the camera, so save_state/load_state work and remote mode has a shared contract to build on. Today nothing on the server holds camera between saves; FrontendBridge pulls it from the client on demand at save time.
The goal is to ensure the server tracks camera state, not to change interaction. In local (vtk-wasm) mode the camera lives in the browser: orbit/pan/zoom manipulate the wasm vtkCamera and the browser renders each frame with the server outside that loop. This remains, and for continuous interactions it will continue this way. This story doesn't route the camera through the server, and doesn't make the server drive the gesture. The only change is that the browser reports the settled camera to the server on EndInteractionEvent, and the server stores it.
Further details on the full camera interaction mechanism are deferred until user story 6.4, where the local (vtk-wasm) mode round trip mechanism is designed.
For the present user story, the following is intended scope (added for context/intent not for the purpose of a concrete prescription):
- Replace the passthrough camera handling. On main, the server asks the client for camera only when it needs it (save time) and never maintains its own pipeline vtkCamera; this story makes the server apply the client's reported camera on EndInteractionEvent, into the real pipeline vtkCamera, not a side record (as it currently is).
- The point is to keep the server pipeline current so local_view.update() is non-clobbering; a fresh server camera means any update() (dataset change, state loaded, etc) carries the camera the client already has and doesn't jump the view; a stale one drags it back.
Acceptance Criteria
- Tests pass
- Behaviour is the same as it is on main
- On a browser refresh, the camera state is preserved (this is a side effect of the server applying the camera to its own VTK pipeline on sync-back or at load_state time)
💵 Business Value
No response
🔗 Useful links and references
No response
- Lingua principale
- Python
- Stelle
- 1
- Fork
- 0
- Merge medio
- 1g 21h
- PR unite (30g)
- 47
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ansys/Visual-Interactive-Simulation-Object-Renderer
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 50/100
-
Library updates Apertatechnical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 1 assegnatario ·
-
[User Story]: Fix workflows Apertamaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 1 assegnatario ·
-
Release 1.0.2 Apertamaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 1 assegnatario ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 1 assegnatario ·
Tutte le issue di ansys/Visual-Interactive-Simulation-Object-Renderer
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
stephrobert/dsoxlab#238 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
sublimehq/package_control#1780 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
nwg-piotr/nwg-displays#145 ·