So I have been learning the Castlevania: Symphony of the Night speedrun on Christine's XBox Series X and I was gonna stream it this weekend. On Playstation streaming direct from the console was incredibly easy so I expected it would be simple on XBox also.
It is not. So: I tell it to start streaming. It does everything on screen to show it has started streaming. When I bring up the stream on Twitch, it's… a silent loop of… a "corporate Memphis" animation of an astronaut and an angel and a cat clock.¹ It is supposed to be Castlevania Symphony of the Night. Certain system menus, if I bring them up while this is happening, force the stream to automatically "pause" and once it pauses it does not (can not) unpause, the streaming UI is just locked up. I can click "Unpause stream" and it bleeps and animates like I selected the menu item but the menu option continues to show "Unpause stream" afterward and the stream remains "paused". Of course, I'm not sure what difference this makes since it streams the same cat clock animation regardless of whether it's "paused" or "unpaused". In any of these situations, my headphone sound is not included.
This is really hard to chase down because how do you even search for that? "Stream is a cat clock." What I eventually find is a five year old Reddit thread where it turns out you simply can't stream Symphony of the Night. More specifically the XBox does not let you stream ANYTHING unless the developer has set a special "ok to stream" flag, and none of the XBox 360 backward compatibility titles have the flag set at all. So that's really disappointing, but beyond that, why not show some kind of error message in that case? Why… just stream something totally other?
Not sure if I'm going to be able to make my stream tomorrow work or not. :/
¹ A friend tells me he recognizes this as one of the animations from Microsoft's "Mixer" service?!
EDIT: Story continues
So searching for a fix I find an interesting suggestion: Mirror your game screen to a PC using the XBox app, then stream that using OBS. What I have learned is that the XBox app(s) are very broken. A chronicle of software depravity follows.
So, I log in on the "Xbox Console Companion" app on my Windows 10 PC. It easily lets me connect to the Series X, and shows it is playing "Castlevania: SOTN". (This is the name of Symphony of the Night on the XBox. "SOTN". If you search for "Symphony of the Night" on the XBox store you won't find anything.) Beneath the name of the game is a red circle. I want to dwell on this because it was very weird. It wasn't clearly a button or anything. It wasn't animated. It was just a red circle. If I clicked the red circle, it sort of… throbbed. I could click it as many times I wanted and all it would do is jiggle a little.
Uncertain what this means, I try the "Test Streaming" button. This gives me an error dialog explaining that either my XBox or my Console Companion app needs to be upgraded. After a moment of fiddling and a search on Google, I realize what this means is that the XBox Console Companion app is entirely discontinued at this point, and I need to switch to a new app, with a separate Microsoft Store entry, named "XBox". Okay.
I download the new app and log in. The interface is not as good as the Console Companion and much much more focused on aggressively selling you things (selling you PC games actually, an interesting decision for the "XBox" app) but whatever. I tell it to link to the XBox, like the Companion did instantly. When I select the XBox, the only thing it will do is bring up a box saying "Let's test remote play". That sounds like what I want. Clicking "Next" causes a few different boxes to flicker on and off screen, and then… it dumps me at an error box saying only "Try again in a bit. Something went wrong.". This error turns out to be very hard to search for, especially given Microsoft's poor naming choices (every XBox console name seems designed to frustrate Google, app is named "XBox"— "XBox Console Companion" is not a good name but at least it's searchable). But the most common explanation is: This error usually means you have Bluetooth turned off. This is a very interesting comment since my Windows box does not have Bluetooth, and if it did it probably wouldn't be able to reach the XBox which is in another room.
I think I might still be able to pull this out; a friend says he got this error before and got it working by repeatedly turning things on and off again. He also may have wound up using the Android app at some point in the process, which opens the interesting possibility that in order to get our Microsoft console to stream to my Microsoft operating system I will need to use a third product, manufactured by Sony actually, to negotiate between the two.
In the meantime, I am extremely startled by the poor ~user experience~ here. I'm used to Microsoft products working poorly, but what I'd been hearing for years was the XBox was their one line that worked very well. Yet the experience I'm getting here is more akin to a Windows 95 level of glitchiness. Let us count up Microsoft's interface sins:
- Streaming is failing, yet instead of any user-facing message of such it not only fails silently but decides to stream something else entirely
- Consumer/set-top device shipping in 2023 can reproducibly get into an interface state where clicking a prominent button simply does nothing at all
- Dialog box says app may need to be upgraded, where the correct solution is to delete the app and download a different one from the same vendor (I traversed this quickly but a less computer savvy user might not have)
- Dialog box saying "Try again in a bit" for a permanent error [see edit below].
Guh
EDIT: I have it working now. So get this.
The reason remote play was not working was that remote play was turned off on the XBox.
Now, given, that's a pretty understandable reason for remote play to not work. But I probably would have figured that out quicker if it had given me an error message other than "Try again in a bit".
Also, once I turned on remote play, remote play still did not work. It just gave me a different failure mode where instead of displaying an error message and saying "Try again in a bit", it instead showed me a box saying "Turn on your console and sign in with this account". This box was impossible to escape. Signing in on the console had no effect. The way I eventually got past this box was to change the name of the XBox, then turn it off and leave it off for 60 seconds. After that it worked. I'm not completely certain if changing the name actually did anything.
That sucked.
FINAL EDIT: My suffering had not ended.
I posted the above edit Friday night. Satisfied, I went to bed, thinking I would simply be able to boot up ten minutes before the stream the next day. No.
When I set up the stream exactly as yesterday, the remote play window on the Windows 10 machine was very, very dim, as if a dark curtain were over the game. My stream started half an hour late as I struggled to understand what was happening here. Searching Google, I found many forum, reddit etc posts from people begging for help with this same problem, and unhelpful "restart the XBox" style advice from Microsoft representatives. Eventually, restarting the XBox did seem to fix the problem, and I was able to start my stream, albeit nearly half an hour late.
When my stream completed, I basically swore never again. I wanted to continue my SOTN speedrun attempts, but my rube-goldberg streaming situation was just not worth it. I decided that in future, I would simply use the XBox's built in video recording feature to record my play sessions. Streaming is kinda high-pressure anyway. This would let me run as a casual thing on a random afternoon.
When I came back on the next random afternoon, that Monday, I once again hit a wall.
There were two problems.
-
Unlike the PS4/PS5, which can record a half hour of play without even being told to do so ahead of time, the XBox is limited to videos of four minutes in duration. That is not enough for a speedrun. Looking around, it turns out you can extend this to one hour— not enough for some SOTN categories, but enough for the ones I'm running— with a USB3.0 external hard drive. Fine. I plug in a USB stick. It is not accepted because the USB stick is FAT32 formatted and it can only record to an NTFS drive. Fine. I plug in my backup hard drive with an NTFS partition. It is still not accepted because despite being created by an actual operating system company, apparently the XBox Series is not able to comprehend drives with multiple partitions. I sigh, order a new USB stick off Scamazon¹ so I can format it NTFS, and go back to my loathed "Remote Play"/OBS solution.
-
As with the start of my stream, once again I am in dark curtain land. Infuriated, I spend my precious spare time I was going to spend playing a fun video game debugging this and re-reading the many internet chronicles of other people hitting this bug, until by complete coincidence I figure out a solution: It turns out that the reason the dark curtain appears sometimes but not other times is that the dark curtain appears anytime that you initiate a remote play session while a game is already open. If the XBox has the system "Home" menu open when remote play connects everything is fine, if Symphony of the Night is open the dark curtain remains until you disconnect Remote Play, bring up the "Home" menu, and reconnect. I may have just found the solution to a problem that has tormented countless others over the last five years and I have no way to communicate it to any of them.
I start recording on OBS and hurry to get in one last run in the time I have left. I am killed in the inverted castle by a bat.
¹ Take that, Jeff Bezos.
