When you install it again, cut a piece of an old credit card and bend it around the cable to use as a zipper.
THATS BLOODY GENIUS!
As you have already guessed, not my idea…
Thank you, thank you, thank you.
I wish my new cable would arrive. Did they send it to you guys regular mail or courier?
Mine was by courier. Have you received a shipment notification? These cables are in high demand. Could be they need to re-stock?
Nope, no shipment notification. I’ll keep my eye out. Ugh, actually waiting for a package is like watching water boil.
The wonderous world of ‘puters…
Just when you think you have everything dialed in perfectly.
I wanted some easy distraction and went jerryhunting in my DCS Spitfire.
A minute in the mission the G2 blacked out. WTF?
Restart and SteamVR had installed another beta update. Ok, that must’ve been it.
Black out again…
Hm? Something the matter with the SteamVR beta perhaps? Opted out of the beta and tried again. Black out.
Starting to get annoyed.
Uninstalled SteamVR and installed it again.
Black out.
Started to think.
The only thing I had changed with the setup, since changing the G2 cable (which worked great, BTW) was removing the new cable to put on the Alex Tech sleeve… Surely, that couldn’t be the issue? Well, I had pulled out the connector in the headset and the DP and USB connector at the other end.
So…I reset all the connectors and rearranged the cable attachment to the headset straps.
No more blackouts…!
Could that really have been the problem?
The sleeve made the cable a bit stiffer so maybe it pulled at the connector…?
I’m at a loss here… I need @fearlessfrog. He can always explain the strange stuff to me.
That is my guess as well. I have been having some stutters while using it and it always goes away when I pull the cable up to reduce tension on the connector. It seems very sensitive to pullibg forces
Phew! Had me on the the edge of my ejection seat there. Glad it’s working.
LOL, me too! I took a good hard look and my G2 and figured out I had the cord taped in the back which should actually be a velcro band SLIDING point! I took off my left headphone and double electrical taped the cord up front. I already had it taped there once … just needed reinforcement.
My G2 has an appointment with a roll of motherloving duct tape.
LMAO!
I am patiently waiting on my Rev 2 cable. I sure will make some gizmo to keep tension off. In the army they call it a tension loop. I will attempt that.
I really want a G2 for Xmas but man, she doesn’t sound like an easy gal
95% of problems you hear about with the G2 are because of the old cable. When you buy a new one, you get the fixed cable. I never had the faulty cable and I bought a G2 a month ago.
So it’s not as bad as it looks anymore
I kind of made that myself… But the tension loop can also cause tension, if the cable itself is stiff enough and the loop too small.
I secured the cable to the top head band and the neck band, but there was too much cable between the connector and the first attachment which forced the cable into a curve. I think that may have put a strain on the connector. When I straightened it out a little, all was well again. Also, as you can see, I put the cable sleeve on all the way up to the connector. There’s really no reason to do that as that’s not where the cable gets stuck or tangles. I will remove some of the sleeve close to the connector.
I had zero problems on my intel system. The problems it had with AMD systems was due to the cable, that now has been fixed with a new cable.
I think my recent blackouts was a simple user error…
As mentioned, its the cable and that is now fixed. I’m on the Odyssey and its not as nice as the G2. Its only been frustrating for me because my mail takes 2 weeks. (APO). I still love the G2
Nah… This isn’t a cable issue.
Blackout again. This time with a ”Steam VR has encountered a critical error”.
No blackouts in WMR portal, only when using steam.
Makes me think about @fearlessfrog’s problems in this thread.
It is…
Hmmm… I tried reinstalling Steam VR and deleting all associated files and then reinstalled it again, per @fearlessfrog’s recommendation in that thread. Seemed to work for almost an entire mission, but…no.