-
Notifications
You must be signed in to change notification settings - Fork 0
feat: [Remote rendering 3.2a] server-tracked camera: record, load-path write, and re-serialization #110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
LKasianAnsys
wants to merge
10
commits into
main
Choose a base branch
from
feat/3.2a-server-tracked-camera
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: [Remote rendering 3.2a] server-tracked camera: record, load-path write, and re-serialization #110
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
6f0e670
add camera record and pipeline projection to IRenderer and write it o…
LKasianAnsys 2083d23
Re-serialize the camera after sync_camera
LKasianAnsys 8247928
chore: adding changelog file 110.added.md [dependabot-skip]
pyansys-ci-bot 0248dd4
serialize camera in reset_camera
LKasianAnsys d5b9247
serialize only camera in serialize_camera_state and tidy up docstrings
LKasianAnsys a4b1c6b
xfail test_load_state_into_empty_scene
LKasianAnsys 9189f66
Merge branch 'main' into feat/3.2a-server-tracked-camera
LKasianAnsys c5627ba
Merge branch 'main' into feat/3.2a-server-tracked-camera
LKasianAnsys 3d570f0
clean up apply_state method content
LKasianAnsys 5778ff9
fix typo
LKasianAnsys File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| [Remote rendering 3.2a] server-tracked camera: record, load-path write, and re-serialization |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ansBAkula yes this is a nice callout, on
apply_state, and it's a good time for it because the rest of the stories in the state inversion work (phase 3) will build on this.The method did read awkwardly. In story 3.1, the per-part visual state was made server-authoritative, and it added
restore_part_states_from_runtimehere. Then this PR had added the camera sync and restore logic, but it was inline rather than in its own similar method, so it wasn't clear that the per-part and camera state were being treated on par. After this user story, there are three more that will also be adding their own state to the list (widget state, UI state, and variable state).I made a couple changes in this commit to make it more readable and to hopefully clarify, including putting the camera state restore/sync into its own method.
Once all part of the state are covered by the end of Phase 3, it will look like:
To try to help clarify I renamed the following:
_restore_part_states_from_runtime->_restore_part_states, We're inapply_stateapplying the persisted state, so the 'from_runtime' was confusing (even though it was technically true, it was applying the persisted state as converted to runtime). Dropped the suffix._apply_runtime_state_to_render->_push_runtime_state. This better describes what this method does. It runs through the renderer. On the wasm path it pushes the state to the client. (RCA would render a frame)Let me know if this makes sense to you. Open to feedback!