Hey, Tumblr, I'm angry and frustrated and I'm making it your problem.
Break the Keep Reading only if you either A. have any experience with OBS-Websocket or other such integrations, or B. sincerely wish to partake in my suffering. Warning for excessive cursing, it gets rough.
Update on the whole KT-1632 overlay situation: After a handful of minor technical difficulties and rookie mistakes (hey cat, it would help if you actually turned on the damn websocket before trying to connect to it), I've established a base framework for connecting to OBS Websocket.
Once I had that in place, I started testing out what kind of messages I can get, and uh... I'm already running into a huge problem, here.
See, OBS Websocket 5.0 has the following messages that seem pertinent to my use case: CurrentProgramSceneChanged, SceneTransitionStarted, SceneTransitionEnded, and SceneTransitionVideoEnded. Keep in mind, the only documentation I can access right now, as far as I can tell, is just the 5.0.1 OBS-Websocket.
Here's a refresher on the use case: I want to be able to move elements of my Unity-based stream overlay depending on which scene is currently active in OBS. A wrinkle in this is that I use a custom stinger transition with a specific cut point, like this:
Now, all three events regarding the scene transition only have one piece of data to them: the name of the transition (which is basically always going to be "SniperScope"). The only event that actually tells me what scene is being switched to is the CurrentProgramSceneChanged event.
There is an immediate problem.
Funnily enough, this order of operations is actually backwards from the current documentation:
On the one hand, there could potentially be some sort of delay or other issue involved with WebsocketSharp / Unity that's responsible for this, however in my testing the exact amount of delay and order of operations is entirely consistent every single time I initiate a transition in OBS. The first message almost always arrives instantaneously; it's the other three messages that seem to come whenever they feel like it, and not at all close to what they need to be at.
On the other hand-- wait, what? What's this issue on the official obs-websocket github about--
So you're telling me that SceneTransitionStarted used to have the from and to scenes specified in the event data in version 4, and they removed it in version 5 for literally no other reason than an RPC overhaul? And they haven't added it back in OVER A YEAR?!
Now, the github actually does have an install link for obs-websocket version 4.9.1-compat that should (keyword should, you know how that goes) work with OBS 29 (more specifically, it should work with 28+, which means there isn't even a guarantee for it to work with OBS 29... fucking awesome).
However, uhhhhhh... I cannot find ANY FUCKING DOCUMENTATION FOR 4.9'S PROTOCOL WHATSO-FUCKING-EVER. There is LITERALLY ONLY 5.0 in the readmes and protocol.md docs.
This shit has me pulling my hair. I'm goin' the fuck to sleep. Anyone got any bright fuckin ideas, I'm all fuckin' ears for it in the morning.