cadey
/
sm64pc
1
1
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

gamebridge: Twitch Control #2

Merged
cadey merged 29 commits from gamebridge into master 2020-05-11 22:40:05 +00:00
Conversation 0 Commits 29 Files Changed 24 +8 -4
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 1d0da2661f - Show all commits

12
doc/gamebridge.org
View File

@ -6,12 +6,16 @@ desires.
* High level ideas * High level ideas
the rust program has two threads, one is getting the inputs from $SOMEWHERE and the rust program has two threads, one is getting the inputs from $SOMEWHERE and
the other is doing the file I/O to the game \\ the other is doing the file I/O to the game
the game bridge thread has two file descriptors open, a fifo for feeding inputs the game bridge thread has two file descriptors open, a fifo for feeding inputs
to the game and a fifo opened by the game for signaling vblanks \\ to the game and a fifo opened by the game for signaling vblanks
the game will then write a readiness signal to the rust program and read the the game will then write a readiness signal to the rust program and read the
button data fifo \\ button data fifo
then things will progress normally \\
then things will progress normally
the getting the input thread of the rust program will have some logic for the getting the input thread of the rust program will have some logic for
telling how long ago it got liveness of the input source (explicitly vaguely telling how long ago it got liveness of the input source (explicitly vaguely
defined to allow a controller to sit there and do nothing as long as it still defined to allow a controller to sit there and do nothing as long as it still