Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[Remote rendering 3.2] Camera state persistence and sync-back

Geschlossen
#20 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@LKasianAnsys arbeitet bereits daran.

Seit 03.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

technical
📝 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

Vorherrschende Sprache
Python
Sterne
1
Forks
0
Ø Merge
1 T. 21 Std.
Gemergte PRs (30 T.)
47

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ansys/Visual-Interactive-Simulation-Object-Renderer

Alle Issues in ansys/Visual-Interactive-Simulation-Object-Renderer

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.