Jump to content

Disconnects with Oculus 2


Recommended Posts

I've been playing in VR for about a month.  Everything was going well.  I got some great settings which were so incredibly immersive, words can't describe.  I'm sure fellow VR users can understand the difference.  Since Monday, When I load into the world, I am getting disconnects.  I've been troubleshooting with Oculus support, and I'm puzzled why it worked great on Sunday, but Monday I can't even do a carrier landing mission without multiple disconnects.

 

Curiously, In the past when I had disconnects, I could see DCS on my monitor in VR mode, but could not reconnect.  Yesterday, I COULD reconnect to the sim, but it would disconnect again after a short amount of time.  Today, I did the factory reset and all that crap they want you to do, and now I'm back to not being able to reconnect to the sim.

 

I tried my wife's Oculus, and the same issues.  Anybody else have a similar experience?  Google has not helped.  Any ideas?

Link to post
Share on other sites

You are not the only one. The Oculus forums and Reddit have numerous post about similar/same experiences.

Ever since my Q2 updated from v23 to v25 I have encountered regular 'link' disconnects (as well as other issues not listed here). It's been a frustrating experience to say the least. Unlike you, I haven't been able to reconnect to DCS if it disconnects while I've started the program while in VR>

 

I recommend using the 'Oculus Log Gather' to report issues encountered with the device. I'm going to assume that this will reach the relevant QA & Development teams for investigation and resolution far faster than our posts on here. 
 
You'll find the relevant program here (your installation path may vary if not the default install)
Located: "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusLogGatherer.exe"
 
Once run, set the Collection date period, and check the full logs and auto submit check-boxes, and finally complete the field explaining your issue.
 
I'm hoping that the more reports that are received in this manner is noticed and any priorities are changed to resolve any identified issues.

Edited by Dodge

Regards,

Paul "Dodge / LondonLad"

 

SYSTEM SPECS: AMD Ryzen 7 5800x @ 4.8 Ghz , 64GB 3600MHz RAM, ASUS ROG Strix X570-F Gaming, NVIDIA RTX 3070 (8GB GDDR6, IIYAMA 34" Curved GB3466WQSU, Thrustmaster Warthog (Joystick + Throttles), VKB Pedals (v4) + TM MFD (2), Oculus Quest 2

Group: DCAF

Link to post
Share on other sites

Thanks for the reply!

 

I've been in contact with Oculus support and have given them logs.  I bought a new Oculus USB-C cable, and still get disconnects.  Since I already tried on a different Oculus headset, I'm guessing it has to lie in the software on one side or the other.  Currently I'm overclocking through the BIOS, as well as MSI software just to be able to do basic training missions without disconnecting.

  • Like 1
Link to post
Share on other sites

I've been getting them on mission start as soon as the world is loaded.  Running the overclocks is the only thing that's helped so far, but that's how I get good frames with a crisp cockpit anyway.  I did lower the pixel density to 1.5 from 2.5 and turned civ traffic from Medium to off.  The troubling part is I was getting good performance from the initial settings as of Sunday all day.

 

For what it's worth, lowering those two settings helped lower my disconnects, though they still happen.

 

Edit:  Also, since resetting the BIOS auto overclock and using MSI software for extreme performance, I have been able to reconnect to the game after it drops back to the Oculus menu.  Quickly click on the Oculus link in the quick actions.  Not great in the middle of action, but livable during a cold start/flying to waypoint.


Edited by Danimal1306
Link to post
Share on other sites

Ok so i have an ongoing log with Oculus Support and will provide feedback as i hear back.  I also would like to clarify has anything changed with the way ED handle the flow from Mission editor, cockpit, to F10 map in either the Hotfix/end of Jan Feb patch.  

 

This started for me two weeks ago.  It happens both in SP and MP.  I can replicate it now 100% of the time on say mission editor where build a mission, click play and when you get to the choose slot screen and select one, you briefly see the aircraft loading in for a milisecond before it crashes back to the Oculus home within the headset.  It looks as if on the monitor the game is still running.  I do not understand however why despite showing the fly screen (as in stationary image and not yet pushed the fly button an i7 9700k core is maxed at 100%?).

 

95% if not more in MP if i say choose tac command or jtac to look at the F10 map, or even inflight checking the F10 map will dump the link.  To note there is a long standing F10 map issue with this that causes FPS loss anyway.   This for me has made DCS and Quest 2 completely unflyable, especially when associated with the FPS drop in game that sometimes can be corrected by al tabbing to another app and back in.

 

Checking in the Oculus logs i get his every time there is a disconnect.

 

Service_2021-02-19_17.32.16.txt] 19/02 20:07:28.851 {!ERROR!} [xrstreaming] WinUsb_ReadPipe(handle:0x000001D27A1A7610, ep:129, len:1024) failed: (433) A device which does not exist was specified.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] WinUsb_WritePipe(handle:0x0000000000000000, ep:255, len:4096) failed: (995) The I/O operation has been aborted because of either a thread exit or an application request.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] RemoteHeadphones: pipeCallback: sendAudio() failed to send audio buffer: -1002

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [RemoteHeadset] Error getting user settings from session. Result=-1002.

{!ERROR!} [RemoteHeadset] Error getting audioControlfrom session. Result=-1002.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [RemoteHeadset] Error getting hands from session. Result=-1002.

{!ERROR!} [RemoteHeadset] Error getting hand skeleton data chunk from session. Result=-1002.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [RemoteHeadset] Error getting tracking from session. Result=-1002.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [RemoteHeadset] Error getting body from session. Result=-1002.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

9 {!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [xrstreaming] inbound data processing loop exited: I/O error (13)

{!ERROR!} [Kernel:Error] OVR Error:

[Service_2021-02-19_17.32.16.txt] 19/02 20:07:29.199 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""

{!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""

{!ERROR!} [xrstreaming] Failed to construct channel for winusb,2833,ff,89

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile.

{!ERROR!} [xrstreaming] Failed to construct channel for winusb,2833,ff,89

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [Kernel:Error] [Aggregated 24 times] OVR Error:

{!ERROR!} [xrstreaming] [Aggregated 20 times] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic

{!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile.

{!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled

{!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled

{!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled

{!ERROR!} [LifeCycle] Leave VR with unregistered pid: 2864 (Unknown)

{!ERROR!} [xrstreaming] WinUsb_ReadPipe(handle:0x0000000000000000, ep:255, len:1024) failed: (995) The I/O operation has been aborted because of either a thread exit or an application request.

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] inbound data processing loop exited: transport closed (12)

[Service_2021-02-19_17.32.16.txt] 19/02 20:08:33.601 {!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""

{!ERROR!} [Kernel:Error] OVR Error:

{!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile.

[Service_2021-02-19_17.32.16.txt] 19/02 20:08:35.443 {!ERROR!} [IpcRouter] Command /bug_reporter/get_bug_info caused an error: OVR54112166

 

Would appreciate a Dev's thoughts on the issue and feedback!

---------------------------------------------------------------

 

DCS | F14B | AV-8B | F18C | F16C | A10C | JF17 | Viggen | L-39 | MIG 15 | SU27 | SU33 | F15 | MI8 | Huey | KA50 | Gazelle | P47 | Spitfire | CA | Persian Gulf | Nevada | Normandy | Channel | Syria

 

Liquid Cooled i7 9700K @ 5Ghz & OC RTX2080 Ti Ultra | 64GB DDR4 3200 MHz | 500GB SSD m2 | Oculus Rift S | TM Warthog | Virpil T50/Warbrd Base | Cougar MFD | Saitek Side Panel | Steel Series Arctis 7 Heaphones

Link to post
Share on other sites

I have similar entries, and am ensuring that after each 'link' disconnect that I am reporting the issue via the Oculus Log Gatherer which seems to automatically send the/a report to the Oculus 'reporting' system.


Edited by Dodge

Regards,

Paul "Dodge / LondonLad"

 

SYSTEM SPECS: AMD Ryzen 7 5800x @ 4.8 Ghz , 64GB 3600MHz RAM, ASUS ROG Strix X570-F Gaming, NVIDIA RTX 3070 (8GB GDDR6, IIYAMA 34" Curved GB3466WQSU, Thrustmaster Warthog (Joystick + Throttles), VKB Pedals (v4) + TM MFD (2), Oculus Quest 2

Group: DCAF

Link to post
Share on other sites

Since Oculus support has asked to run the log compiling program and send it, we shouldn't assume it's automatic.   If it's automatic, why would they request for me to gather the logs and send them in an email?

 

Do the Oculus logs help the DCS team? Should we give them here to help find the problem?

Link to post
Share on other sites

Oh, don't get me wrong. I fully support whatever the Oculus Support team are requesting from you. I've just added what I've been doing during each problematic encounter I've had to endure, and with that, I feel I don't need to contact Oculus Support (I'm hoping reports sent from that program is doing something similar to you contacting the support team).

To your second point. And I'm assuming here, but I don't think the Oculus logs are of use to the  DCS team (at least not directly). I suspect, if they can/do, would just pass this onto Oculus or point us to contact Oculus Support. However, there no harm is providing that to DCS (as you have done here), as I'm none the wiser and who knows, there might be something there that if seen by a developer, might be useful for either something within DCS to adjust, or allow DCS to raise suggestions with Oculus themselves (if there is any form of mutual contact).

Regards,

Paul "Dodge / LondonLad"

 

SYSTEM SPECS: AMD Ryzen 7 5800x @ 4.8 Ghz , 64GB 3600MHz RAM, ASUS ROG Strix X570-F Gaming, NVIDIA RTX 3070 (8GB GDDR6, IIYAMA 34" Curved GB3466WQSU, Thrustmaster Warthog (Joystick + Throttles), VKB Pedals (v4) + TM MFD (2), Oculus Quest 2

Group: DCAF

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...