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

Video playing no longer syncs at all. #65

New Issue
Closed
opened 2026-03-12 02:55:37 -04:00 by ActualHorse · 1 comment
ActualHorse commented 2026-03-12 02:55:37 -04:00
Owner
Copy Link

An insanely weird bug has emerged. Videos no longer sync when the first player to join a world tries to act as a host, despite that being the first person to become host in the first place. If a second player becomes host and attempts to play videos, they will then sync. It seems to be an issue of ownership; the video player seems to want to be owned by the most recent person to join a world, no matter what, and re-establishing ownership when the host card is picked up or a case is loaded seems to be broken. This needs to be investigated immediately.

An insanely weird bug has emerged. Videos no longer sync when the first player to join a world tries to act as a host, despite that being the first person to become host in the first place. If a second player becomes host and attempts to play videos, they will then sync. It seems to be an issue of ownership; the video player seems to want to be owned by the most recent person to join a world, no matter what, and re-establishing ownership when the host card is picked up or a case is loaded seems to be broken. This needs to be investigated immediately.
ActualHorse added this to the v0.5 milestone 2026-03-12 02:55:37 -04:00
ActualHorse added the
Type
Bug
Priority
A
 labels 2026-03-12 02:55:37 -04:00
ActualHorse self-assigned this 2026-03-12 02:55:37 -04:00
ActualHorse commented 2026-03-12 04:16:05 -04:00
Author
Owner
Copy Link

Okay, this seems to have been fixed. Some seemingly superfluous code was commented out of the video player, but it turns out that code was very necessary for syncing values properly between clients. It's been added back in, but long-term it seems like a better idea to reduce the number of serialisation requests to prevent this from being necessary. I'll file a separate issue for that.

Okay, this seems to have been fixed. Some seemingly superfluous code was commented out of the video player, but it turns out that code was very necessary for syncing values properly between clients. It's been added back in, but long-term it seems like a better idea to reduce the number of serialisation requests to prevent this from being necessary. I'll file a separate issue for that.
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
Bug
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#65
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?