ActualHorse/CarmenSandiego
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

Camera system enhancements #53

New Issue
Closed
opened 2025-10-03 03:16:02 -04:00 by ActualHorse · 2 comments
ActualHorse commented 2025-10-03 03:16:02 -04:00
Owner
Copy Link
  • Add opening camera shot and logo.
  • Add transitional camera moves between stages, and that awesome crane shot before the end credits.
  • Make sure the camera positions sync across all clients, or at least all clients with camera privileges.
  • Experiment with camera positions to ensure everything that needs to be visible is visible, while accounting for headroom and title borders.
- [x] Add opening camera shot and logo. - [x] Add transitional camera moves between stages, and that awesome crane shot before the end credits. - [x] Make sure the camera positions sync across all clients, or at least all clients with camera privileges. - [x] Experiment with camera positions to ensure everything that needs to be visible is visible, while accounting for headroom and title borders.
ActualHorse added this to the v0.5 milestone 2025-10-03 03:16:02 -04:00
ActualHorse added the
Type
Enhancement
Priority
A
 labels 2025-10-03 03:16:02 -04:00
ActualHorse self-assigned this 2025-10-03 03:16:03 -04:00
ActualHorse pinned this 2025-10-03 03:24:53 -04:00
ActualHorse commented 2026-03-12 04:30:22 -04:00
Author
Owner
Copy Link

Turns out there's a pretty simple reason why camera movements don't sync, and it's because they were never programmed to. Figuring out how to sync camera attachments seems like a nightmare, and will almost certainly require significant refactoring, but eventually it will be necessary, so we may as well get to it soon.

Turns out there's a pretty simple reason why camera movements don't sync, and it's because they were never programmed to. Figuring out how to sync camera attachments seems like a nightmare, and will almost certainly require significant refactoring, but eventually it will be necessary, so we may as well get to it soon.
ActualHorse commented 2026-03-17 04:04:38 -04:00
Author
Owner
Copy Link

Wasn't as hard as I assumed. It's now done. There's still more work to be done, but those can now be in their own issues.

Wasn't as hard as I assumed. It's now done. There's still more work to be done, but those can now be in their own issues.
ActualHorse unpinned this 2026-03-17 04:08:22 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority
A
The priority is critical
Priority
B
The priority is high
Priority
C
The priority is medium
Priority
D
The priority is low
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Type
Breaking
Breaking change that won't be backward compatible
Type
Bug
Something is not working
Type
Documentation
Documentation changes
Type
Enhancement
Improve existing functionality
Type
Feature
New functionality
Type
Security
This is security issue
Type
Testing
Issue or pull request related to testing
No Label
Priority
A
Type
Enhancement
Milestone
No items
No Milestone v0.5
Projects
Clear projects
No project
Assignees
Clear assignees
ActualHorse
No Assignees ActualHorse
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ActualHorse/CarmenSandiego#53
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?