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

Auxilliary video screens don't update maps correctly #29

New Issue
Closed
opened 2025-08-01 17:06:07 -04:00 by ActualHorse · 3 comments
ActualHorse commented 2025-08-01 17:06:07 -04:00
Owner
Copy Link

Auxilliary maps always show the last updated frame when loaded in, which is often one of the correct answer flashes, which reveals the answer to the player. This needs fixing, or else those screens can't be used.

Auxilliary maps always show the last updated frame when loaded in, which is often one of the correct answer flashes, which reveals the answer to the player. This needs fixing, or else those screens can't be used.
ActualHorse added this to the v0.5 milestone 2025-08-01 17:06:07 -04:00
ActualHorse added the
Type
Bug
Priority
A
 labels 2025-08-01 17:06:07 -04:00
ActualHorse self-assigned this 2025-08-01 17:06:07 -04:00
ActualHorse commented 2025-08-01 23:27:32 -04:00
Author
Owner
Copy Link

Attempting to fix this only broke more. Not sure what the issue is, but it's a bit strange. Try to revert the changes back to the original and figure out why only the main material changes despite it supposedly being a global material.

Attempting to fix this only broke more. Not sure what the issue is, but it's a bit strange. Try to revert the changes back to the original and figure out why only the main material changes despite it supposedly being a global material.
ActualHorse pinned this 2025-08-03 01:04:47 -04:00
ActualHorse commented 2025-08-03 04:43:16 -04:00
Author
Owner
Copy Link

Update: It's not just the auxiliary screens. The main screen is doing it too. It seems to be some kind of weird sync issue. Just need to figure out why it isn't syncing the cancellation of the flashing answer correctly.

Update: It's not just the auxiliary screens. The main screen is doing it too. It seems to be some kind of weird sync issue. Just need to figure out why it isn't syncing the cancellation of the flashing answer correctly.
ActualHorse commented 2025-08-03 20:36:34 -04:00
Author
Owner
Copy Link

Finally fixed.

Finally fixed.
ActualHorse unpinned this 2025-08-03 20:36:47 -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
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#29
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?