[Remote rendering 3.2] Camera state persistence and sync-back
@LKasianAnsys 已经在做这个了。
开始于 2026年9月3日。
评估
这个 Issue 还没有评估数据。
描述
📝 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
- 主要语言
- Python
- 星标
- 1
- 派生
- 0
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 47
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ansys/Visual-Interactive-Simulation-Object-Renderer 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 50/100
-
Library updates 未关闭technical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 已指派 1 人 ·
-
maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 已指派 1 人 ·
-
Release 1.0.2 未关闭maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 已指派 1 人 ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 已指派 1 人 ·
查看 ansys/Visual-Interactive-Simulation-Object-Renderer 的全部 Issue
相似的 Issue
-
agent-ready documentation needs-triage
难度 1/5 1-3 小时 新手友好度 88/100
-
documentation
难度 1/5 1 小时以内 新手友好度 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
-
instance instance add
难度 1/5 1 小时以内 新手友好度 72/100
searxng/searx-instances#939 · 1 条评论 ·
-
area-deployment area-integrations triage:bot-seen
难度 2/5 半天 新手友好度 86/100