Jump to content

Recommended Posts

Posted (edited)

At first I thought that the oculus link cable was the problem, so I threw $85 down for a new Oculus Link cable. Not the issue. 

DCS will stay running while the Quest boots me back to the home screen. I then have to pause the game and restart oculus link from the Oculus home screen . Sometimes I will be able to start back where I was, other times I will just be looking at a black screen in the headset while tracking resumes on the PC monitor and I have to just exit the DCS program from there. This ONLY happens on the F14 and I am out of ideas. I can not find any errors in the logs. HELP 

 

 

 

dcs.log

Edited by [̲̅D][̲̅A][̲̅T][̲̅A]
Posted

Running v25 of the Oculus software? If so, there seems to be a number of users (various forums) with users experiencing 'link' disconnection once v25 updates the Q2. This certainly happened to me on a regular basis (v23 was fine). My Q2 just updated to v26 and I 'feel' in the short couple of sessions that it seems slightly better (and the visual do as well for some reason). What I when the link disconnects is use the Oculus Log Gather to submit the logs and provide a description (see image below - select the options that suit you). I'm hoping the more reports received, the faster the Oculus developer identify issues and resolve them:

Oculus Log Gatherer

 

Description

The OculusLogGatherer.exe tool is included with the Oculus app installation, and can be used when you have issues with the Oculus runtime.

 

From <https://developer.oculus.com/distribute/log-troubleshooting/?locale=en_GB>

 

Location (Your path may vary)

  • "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusLogGatherer.exe"

image.png

 

Addition Reading Links

Regards,
Paul "Dodge / LondonLad / ChemoBrain" 


SYSTEM SPECS: AMD Ryzen 7 5800x , 64GB 3600MHz RAM, ASUS ROG Strix X570-F Gaming, NVIDIA RTX 4080 SUPER 16GB GDDR6, IIYAMA 34" Curved GB3466WQSU Monitor, VPC WarBRD-D Base, VPC MongoosT-50CM2 Grip, VPC MongoosT-50CM3 Throttle,  VPC Control Panel #2, VPC ACE Interceptor Pedals, TM MFD w/CUBESIM (x2), PointCTRL, HP Reverb G2 VR  Headset | Back up: NVIDIA RTX 3070 8GB GDDR6, Thrustmaster HOTAS Throttle, VKB Pedals (v4), Oculus Quest 2 VR Headset, & TrackIR

Group: DCAF (Now Left, but a great group to be apart of - UK Based)

Posted

Thank you Paul for the reply. I am indeed using v25, and after my tooling around trying to fix the issue. I've successfully made the whole oculus link program unuseable. Updating to v26 and trying again. Thank you again for your reply and  letting me know that it's a Oculus problem and not a me problem. 

Posted

Update again, reinstalling the F14 did not work. 
Tried other aircraft, other aircraft causes oculus to stop running. DCS is the problem. Played Blade and Sorcery for an hour without issue. 

F14 just causes the crash to happen faster. 

 

That's where I am at with this problem so far. 

 

Faulting application name: OculusDash.exe, version: 0.0.0.0, time stamp: 0x4b6e1b38
Faulting module name: OculusDash.exe, version: 0.0.0.0, time stamp: 0x4b6e1b38
Exception code: 0xc0000005
Fault offset: 0x0000000000427156
Faulting process id: 0x514
Faulting application start time: 0x01d71106caf04c36
Faulting application path: D:\Oculus\Support\oculus-dash\dash\bin\OculusDash.exe
Faulting module path: D:\Oculus\Support\oculus-dash\dash\bin\OculusDash.exe
Report Id: 2a73be1e-a942-4298-a666-0488ae421dbd
Faulting package full name: 
Faulting package-relative application ID: 

 

Fault bucket 1353361737694256787, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OculusDash.exe
P2: 0.0.0.0
P3: 4b6e1b38
P4: OculusDash.exe
P5: 0.0.0.0
P6: 4b6e1b38
P7: c0000005
P8: 0000000000427156
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF91.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB33B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB34C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB359.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB36A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OculusDash.exe_481bee853faf373699d44364c4943e7054b0bf6f_4b71f3e5_5e4b2b54-3719-414a-8e08-516959a308d6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2a73be1e-a942-4298-a666-0488ae421dbd
Report Status: 268435456
Hashed bucket: 849e9991b1ae686db2c81b547bdf1e93
Cab Guid: 0

 

Posted

Update: Downloaded and installed the standalone version of DCS. Still crashes oculus link back to home screen. 

Also unplugged the USB hub that I had installed thinking that there was a USB power issue that was causing the problem. Did not fix anything. 

Also in more investigating, crashes happen with every module, not just the F14. The F14 just crashes the program faster. 

  • 2 weeks later...
Posted

Having exactly the same issue, used to work fine but after latest update VR is pretty much unusable.  Although Brother who is on a quest AND link cable is running fine, so i don’t know if it’s a quest 2 thing or what.

 

Seen several posts of people complaining bout the same issue.  Hope£ully they will fix it soon for us all. 

 

 

[sIGPIC][/sIGPIC]

 

Fighter pilots make movies, Attack pilots make history, Helicopter pilots make heros.

 

:pilotfly: Corsair 570x Crystal Case, Intel 8700K O/clocked to 4.8ghz, 32GB Vengeance RGB Pro DDR4 3200 MHZ Ram, 2 x 1TB M2 drives, 2 x 4TB Hard Drives, Nvidia EVGA GTX 1080ti FTW, Maximus x Hero MB, H150i Cooler, 6 x Corsair LL120 RGB Fans And a bloody awful Pilot :doh:

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...