fixed Latest Oculus v63 PTC build crashing DCS when used on Oculus Link

[eagle17]

Well add me to the list... i just bought a new pc and with the new pc also bout an quest 3.. I am not opted into ptc, I have been running the 63 ver of the oculus desktop software since day 1  last weekend    and not problems until tonight. ... I booted up my machine to see that the oculus link driver updated and now get the crash... not sure how to downlowd the "link software" but this is pretty disheartening...  I hope that ED can find a solution soon as I also agree that steamlink is something that will work for me... I was pretty happy with the ease of use and don't want to add complexity of VD or other solutions...    at least now I know its an ED issue and they are working on it... 

Thanks slughead for posting the link to bignewy post about native oculus vr ...   

Edited March 29, 2024 by eagle17

[Dogmanbird]

i guess the bug has given an indication of how many use just a meta headset alone

[slughead]

12 minutes ago, dugite57 said:

It's easy to invest a lot in ED over many years. I've got two accoints so as I can fly two up in VR. It's Easter Holidays and I'm unable to play. Leaves a very bad taste and I am, to put it mildly, very dissappointed. It's not ok to not release a hot fix just because of with some inflexible corporate patch regimen.

Fair point. Have you not tried running via SteamVR in the meantime?

[Mike_CK]

33 minutes ago, slughead said:

Seriously? Wow. Devoted simmer. 

Well, according to steam, the value of all of the modules, maps, etc you can purchase is like $3500. So yeah, figure about 15 modules, all of the maps and probably over a dozen campaigns…it adds up. That’s not including the VR/HOTAS/pedals crap. 

[slughead]

11 minutes ago, eagle17 said:

Well add me to the list... i just bought a new pc and with the new pc also bout an quest 3.. I am not opted into ptc, I have been running the 63 ver of the oculus desktop software since day 1  last weekend    and not problems until tonight. ... I booted up my machine to see that the oculus link driver updated and now get the crash... not sure how to downlowd the "link software" but this is pretty disheartening...  I hope that ED can find a solution soon as I also agree that steamlink is something that will work for me... I was pretty happy with the ease of use and don't want to add complexity of VD or other solutions...    at least now I know its an ED issue and they are working on it... 

Thanks slughead for posting the link to bignewy post about native oculus vr ...   

 

Quest 3 headset?

Just now, Mike_CK said:

Well, according to steam, the value of all of the modules, maps, etc you can purchase is like $3500. So yeah, figure about 15 modules, all of the maps and probably over a dozen campaigns…it adds up. That’s not including the VR/HOTAS/pedals crap. 

You must have a huge amount of planes in your hanger. Fair do's.

[Mike_CK]

1 minute ago, slughead said:

Quest 3 headset?

You must have a huge amount of planes in your hanger. Fair do's.

Not as many as some; about 15 (not including the FC-3 pack). I don’t really ever fly 4 of them (mirage F1, Mig 19, Mig 15, f-86) but the others I do…in “bursts” depending on mood. But trust me, there are a lot of people who have invested more than me. So I figure that we should get a lot more room to yell and complian over stuff like this compared to a regular $50 game 

[slughead]

6 minutes ago, Dogmanbird said:

i guess the bug has given an indication of how many use just a meta headset alone

I doubt they were unaware that Meta headsets make up 50% of the VR headset sales globally. What matters is the ratio of Meta VR users to other users of 2D, pimax, HP etc. I expect we are massively outnumbered by 2D users. That's not to say we are not important to ED though.

1 minute ago, Mike_CK said:

Not as many as some; about 15 (not including the FC-3 pack). I don’t really ever fly 4 of them (mirage F1, Mig 19, Mig 15, f-86) but the others I do…in “bursts” depending on mood. But trust me, there are a lot of people who have invested more than me. So I figure that we should get a lot more room to yell and complian over stuff like this compared to a regular $50 game 

If you had selected the F-16 or F-18, you'd have no time for the other ladies. 

[MAXsenna]

Seriously? Wow. Devoted simmer. 

I'm passed 2000, and that's not counting the two T-shirts from HB for 130.

Sent from my SM-A536B using Tapatalk

[Benno]

Been having regular crashes since the last update. I basically cannot have a session without a random crash occuring. Not module dependant. Happens in any aircraft.
Also having LONG load times of textures when joining servers. Aircraft sitting on ocean map texture. Sometimes for up to a minute. Aircraft cockpit textures taking similar on occasion.

Running MT
10700k
32gb Ram
4090
HP Reverb G2

Attached Log.
 

dcs.log-20240329-031547.zip

[freehand]

I in my reverb at the moment.

You should always have spare or 2 with DCS 

Edited March 29, 2024 by freehand

[Mike_CK]

3 hours ago, slughead said:

I doubt they were unaware that Meta headsets make up 50% of the VR headset sales globally. What matters is the ratio of Meta VR users to other users of 2D, pimax, HP etc. I expect we are massively outnumbered by 2D users. That's not to say we are not important to ED though.

If you had selected the F-16 or F-18, you'd have no time for the other ladies. 

I own both and - along with the F-14 and Mirage 2000k fly them a lot. But sometimes I want to fly a Mi-24 hind. Other times I’m in a WW2 mood. When the F-4 comes out. I’ll be into that. Can’t fly only 2 planes for 6 years!

[Qcumber]

10 hours ago, DCoffey said:

well I was one of the lucky ones who had the PC app updated to 63 but still runs.

HOWEVER

Last night oculus notified me there is a new update for the headset, I declined but in the settings it says it will go ahead and install it without my consent 4-26

Just a FYI

I updated to this version and everything still works for me. 

[-Sledgehammer-]

vor 25 Minuten schrieb Qcumber:

I updated to this version and everything still works for me. 

you must be the last unicorn or been playing with steamvr ever since…

[Qcumber]

46 minutes ago, -Sledgehammer- said:

you must be the last unicorn or been playing with steamvr ever since…

I don't know why I am not affected. Maybe I am the lucky unicorn. I am running the latest version of v63 (the one which is mandatory after 26th April) and it works fine on my quest pro and rift s.

The information we have is from a biased sample. So far most people who have accessed this thread state that they have issues after upgrading to v63 (maybe about 50-60; I haven't counted). About 3-4 people have said they don't have any issues. We don't know how many other people are continuing to use their oculus headsets with v63 without any issues and are unaware of the problem because they don't access this forum very often. I don't know how many people play DCS with oculus headsets but I think it is a lot more than 60. Until we have all the information we can't say it's broken for everyone. From the evidence we have on this forum it is something that has affected a small number of people (60 out of hundreds). Maybe there are a lot of other unicorns out there. 

Edited March 29, 2024 by Qcumber

[Dogmanbird]

Qcumber - i completely forgot about bringing home a qpro over easter. 

[Qcumber]

6 minutes ago, Dogmanbird said:

Qcumber - i completely forgot about bringing home a qpro over easter. 

I don't think it's an issue related to specific headsets. Others with QPs have found that upgrading to v63 breaks things. 

[Flappie]

Hi Benno. This is a bug and it's been fixed internally. The fix will be part of the next DCS udpate.

2024-03-29 03:15:47.659 INFO    EDCORE (25644): try to write dump information
2024-03-29 03:15:47.700 INFO    EDCORE (25644): # -------------- 20240329-031547 --------------
2024-03-29 03:15:47.701 INFO    EDCORE (25644): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.19045)
2024-03-29 03:15:47.702 INFO    EDCORE (25644): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\dx11backend.dll
2024-03-29 03:15:47.703 INFO    EDCORE (25644): # C0000005 ACCESS_VIOLATION at 00007ff863eb8c77 00:00000000
2024-03-29 03:15:47.704 INFO    EDCORE (25644): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'Ben'
2024-03-29 03:15:47.705 INFO    EDCORE (25644): OS-Version: 10.0.19045 () 0x300-0x1
2024-03-29 03:15:47.707 INFO    EDCORE (25644): 0x0000000000018c77 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37
2024-03-29 03:15:47.708 INFO    EDCORE (25644): 0x0000000000017788 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68
2024-03-29 03:15:47.709 INFO    EDCORE (25644): 0x000000000000be2e (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x40E
2024-03-29 03:15:47.709 INFO    EDCORE (25644): 0x00000000000a3a41 (GraphicsCore): render::ShadowMapModule::queryCasters + 0x921
2024-03-29 03:15:47.709 INFO    EDCORE (25644): 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F
2024-03-29 03:15:47.709 INFO    EDCORE (25644): 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4
2024-03-29 03:15:47.710 INFO    EDCORE (25644): 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED
2024-03-29 03:15:47.710 INFO    EDCORE (25644): 0x000000000001bb92 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42
2024-03-29 03:15:47.710 INFO    EDCORE (25644): 0x000000000016299a (Visualizer): smSceneManager::regLua + 0x129A
2024-03-29 03:15:47.711 INFO    EDCORE (25644): 0x000000000014deb4 (Visualizer): smCamera_Implement::getClipRegion + 0x19594
2024-03-29 03:15:47.711 INFO    EDCORE (25644): 0x0000000000139cdc (Visualizer): smCamera_Implement::getClipRegion + 0x53BC
2024-03-29 03:15:47.711 INFO    EDCORE (25644): 0x0000000000151192 (Visualizer): smSceneManager::DestroySceneManager + 0x1222
2024-03-29 03:15:47.711 INFO    EDCORE (25644): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71
2024-03-29 03:15:47.712 INFO    EDCORE (25644): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2024-03-29 03:15:47.712 INFO    EDCORE (25644): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14
2024-03-29 03:15:48.104 INFO    EDCORE (25644): Minidump created.

 

[YoYo]

44 minutes ago, Dogmanbird said:

Qcumber - i completely forgot about bringing home a qpro over easter. 

Try it, if you have it. Im on QPro and no issue with v63 Meta Quest Link App (still) & DCS MT OXR.

[Hoirtel]

12 hours ago, NemoFlightSims said:

Meta Quest 2 user.

After seeing the issue with VR not launching I decided to try something different than swapping Oculus runtime files, which I think breaks some 3rd party programs.  I uninstalled Meta Quest/Oculus software and deleted all folders in %userprofile%\AppData\Roaming.  I factory reset my headset.  I installed the software from the meta website https://www.oculus.com/download_app/?id=1582076955407037.  I closed the program at the login screen.  I then setup my Quest 2 headset with my phone app doing all the initial setup.  I plugged my headset into my PC with my link cable.  I then started the Meta Quest\Oculus software. I logged into my account and saw which version I had from a fresh install it was this. 

https://imgur.com/WBuG2Qv

I killed all Oculus processes with the task manager, and turned my headset's Wifi off.  I then went into my Firewall and blocked all incoming and outgoing connections to the Oculus sofware, it looks like this

https://imgur.com/0ChDV66

After that my Meta Quest/Oculus software could no longer reach the internet.  It did see an available update(the update that breaks VR) but it would not download it and was stuck at 0%.

https://imgur.com/msxE8SR

This allows me to stay on the last viable software version and still play DCS as if nothing had changed.  I don't know if this will help others or not but I decided it probably couldn't hurt.

 

Blocking via the firewall! Good idea. Wish I thought of that. I unsuccessfully tried renaming the folders as described many pages ago... And it still updated, just happened yesterday. 

Personally I will have to wait now. I have other things on the PC that need my time, but wish I had seen this last week.

[Crabfat22]

Hello all, I've been following this topic closely as I am one of those affected. I'm new to DCS and have recently spent at least £8500 on a SIM setup specifically to play, learn and enjoy the game. After days and days of installing, configuring, binding, altering, routing wires etc, I got just 2 days of flying time in before it all went fffuuuttt! Being computer literate I did the normal initial diags etc, ended up reinstalling everything from DCS to SIM app pro and C++, nothing worked! I've found this thread and am amazed that there is so many users that only want to complain about ED not putting out an hotfix. Maybe it's just me but after a reinstall, I can play quite happily in 2D content to wait out the fix that will more than probably cure everyone's problem instead of an hotfix that may only cure some. This game is amazingly complicated and once it's up and running in VR with the Q3 again will still be the best option for combat flight Sims, period! I understand the frustrations felt by some, me being one of them, but, am willing to cut ED some slack and have patience. 

 

By the way, if you see me in a server..... Don't shoot me down, I'm so new I can't even use the sidewinder

[FupDuck]

3 hours ago, YoYo said:

Try it, if you have it. Im on QPro and no issue with v63 Meta Quest Link App (still) & DCS MT OXR.

I am also using a Quest Pro, and both the headset and desktop software are fully updated. So far it's still working.

[YoYo]

1 minute ago, FupDuck said:

I am also using a Quest Pro, and both the headset and desktop software are fully updated. So far it's still working.

Windows 10?

[FupDuck]

2 minutes ago, YoYo said:

Windows 10?

Yes.

[YoYo]

30 minutes ago, FupDuck said:

Yes.

So far, when someone writes that it works, it turns out that it's on Windows 10. And where it doesn't work (e.g. my friend) he has Windows 11. I don't know if it has something to do with it also, but this is comment from my side.

[Qcumber]

19 minutes ago, YoYo said:

So far, when someone writes that it works, it turns out that it's on Windows 10. And where it doesn't work (e.g. my friend) he has Windows 11. I don't know if it has something to do with it also, but this is comment from my side.

I've just updated to v64 and am using W11 and everything is working ok.