Me: I want to play VR.
Mixed Reality Portal: Check your display cable!
Me: *sighs, gets up and takes the cable out and puts it back in* There. *sits back down*
Mixed Reality Portal: Check your display cable!
Me:
Yeah Microsoft, what the FUCK did you DO!? ..Oh, that’s right, yesterday Windows Update got quite busy. First time it was a small update. Since I had nothing to do, I decided to allow a restart. Decided to check again.. big mistake– big update this time.
Turned out it was this ‘October Update’… in mid-December.
Today I tried to get into VR (as you saw from what I said above). Usually, taking out and putting the cable back in fixes the problem, but not this time. This time it was getting me this strange ‘Error: 1-4’.
Clearly, the October Update has just borked my WMR equipment. Tried to look it up, no one else having this issue. So I thought that it’s possible my graphics card drivers need to be updated. Got the latest, that was released just today. How very interesting, almost like this is a fix for my issue. Yet it wasn’t listed anywhere in the changelog.
Made a mistake with clean install. Instead of it uninstalling the old drivers and installing the new in its place, I only uninstalled the old.. ugh. I’ve been used to Nvidia for way too long.
Tried to restart, noticed Windows also wanted to do so, and I had noticed this last night, but since it was nearly 5:30 in the morning, I didn’t want to wait for it to get done. But this time I allowed it, maybe hoping this would had saved me the hell I’m going through.
–
Came back, installing the drivers. MR Portal comes up, still showing an issue to the cable. But I noticed the error code was gone. Suddenly, it realizes the cable is in and shows ‘Ready’. Thank GOD that’s fixed!
After restarting, I’m no longer seeing the ‘check your display cable’ message when launching MR Portal. I want to take this with a grain of salt of the thought they finally fixed that highly annoying issue.
Also, my brain is reminding me this ‘October Update’ was supposed to fix a lot of issues with WMR. I just hope one of them is optimization with low end builds. I also wonder what took it so long to get to me.
The same can be said for the next Gamefly game coming to my house, but I digress.
—
EDIT (the 14th): Guess what? Yep, the issue’s back after I turned on my computer the day after. Same message, same error code. Here I thought I had it after updating the GPU drivers. Turns out that wasn’t it.
Made a post on the WMR Reddit forum (for a reason I will explain in just a few moments, I’m not linking it). Let’s just say I was extremely not happy, and was on the verge of tossing this $200 paperweight out the window and get an Oculus. My anger made me 110% put the blame on the October Update.
Before I made the thread however, noticed someone having a slightly similar issue, who got help and was told the HDMI cable could be possibly going bad on them. But at the end, they got a new headset. Sadly, this isn’t an option for me.
–
One interesting thing about this, are the troubleshooting steps. One was looking in
Device Manager and looking for ‘Monitors’ and ‘Mixed Reality devices’. The person said they didn’t see the headset in Monitors… but on mine, I saw it.
So, Windows is definitely seeing my headset. If this means there’s nothing wrong with it nor the cables, than that rules those out.
I also noticed they claimed, they reinstalled the WMR software without having to reinstall Windows. And I remembered briefly reading something about that. Seeing this is something I have yet tried, I attempted to look it up and found this. Unplugged the cables from the back of the tower, and repeated the process as Windows seemed to not recognize it. Hit Uninstall, and it claimed there were a few files it couldn’t remove. The post also said to unpair my controllers, so I did.
Plugged in the cables, and the post claimed something would come up and start the setup/installation process… but nothing happened– no window popped up. Randomly tried the MR Portal, and wishing the post said “click on this to start it”, because that was what was needed.
As it’s starting up the setting up, whammo. Issue is back, same error. Posted in the thread I made that I tried reinstalling the software and didn’t help.
…And now, for the reason I refuse to post the link (over embarrassment).
Tried restarting my computer (feeling this isn’t going to help)…. but this time, it did! It went past the error, and ran me through re-paring the controllers. Holy fuck, this is promising. But all I could feel is the issue is just going to happen again after a restart.
After setting up the boundary, everything was ready. It was looking really promising, but I tried my best to keep my surprise at bay and quickly did a restart.
Came back, and.. oh wow. Did I actually kill two issues with one reinstall?! It definitely seems so! 😀
Redid the boundary as I didn’t like how messy I made it the first time. This time it’s much better. After doing the initial VR tutorial and getting to the Cliff House, I noticed it looked slightly different. New demos to play (such as a Superhot demo), yet there’s still no ‘Launch SteamVR’ button. Though I could actually set this up (much like the Desktop app).
Got in VRChat and didn’t have many issues.
–
Shut off my computer for the night, and brought it back this afternoon (the 15th). I was fearing that the issue would return… I was greeted with it saying ‘Ready’. Holy fuck, I got it!! It’s FIXED!! It’s a miracle! Who knew, a simple reinstall would fix months of an annoying issue.
And that, is why I’m not going to link the thread. Saying a reinstall didn’t help, when it actually did. Yeah, embarrassment.
…”It’s FIXED”, Benie cried out. Yet he didn’t realize the next time he turned his computer on, the issue would happen again.