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

[Grodin]

1 hour ago, Shibiswag said:

Okay cool thanks, don't see what Wifi has to do with anything as both my router and switch are rated for 1Gig. My computer is in my bedroom and my switch, router and modem are in a small closet rack with lines running through the house.
Kind of like how you would see in a small business setup. The wifi is only used for my printer, phones, and tablet. Everything else is connected to the switch.

Fully agree, and that's what I pointed out earlier. If people going to come on and act the way they have been, then they going to leave the admins no choice but to close this thread and all others like it.
Then nobody will have a say in anything.
When I get my Taxes in, first thing I'm going to buy is Helldivers 2. FOR DEMOCRACY!
Yeah, kind of broke at the moment lolz.

Because the headset is recommended to connect to the router with Wifi 6.

[slughead]

If you fly single-player, you can set up your machine's Wi-Fi as a hotspot and connect the headset directly to the machine. Wi-Fi6 is necessary to provide enough bandwidth via WiFi to the headset.

[MRMAN]

I can get vr to work using steam vr and the steam version of DCS. Problem with that is I don’t have any modules for steam. ED should allow my standalone version modules to work with steam version until they fix the issue. 

[Shibiswag]

5 hours ago, Grodin said:

Because the headset is recommended to connect to the router with Wifi 6.

I have the headset connected directly to the computer.
Don't have wifi on my PC.
I have USB-C 10Gig cable

4 hours ago, slughead said:

If you fly single-player, you can set up your machine's Wi-Fi as a hotspot and connect the headset directly to the machine. Wi-Fi6 is necessary to provide enough bandwidth via WiFi to the headset.

Don't have Wifi on my PC.
I connect my headset via USB-C 10Gig cable

Edited April 5, 2024 by Shibiswag

[draconus]

10 minutes ago, MRMAN said:

I can get vr to work using steam vr and the steam version of DCS.

Run standalone DCS through SteamVR instead.

[Shibiswag]

4 hours ago, MRMAN said:

I can get vr to work using steam vr and the steam version of DCS. Problem with that is I don’t have any modules for steam. ED should allow my standalone version modules to work with steam version until they fix the issue. 

You need to add the actual executable from the stand-alone version to your steam library.
Just click add game at the bottom of your game list on steam and navigate to the MT version or ST version, which ever you want to use.
Make sure you select Use VR.
Than just launch SteamVR as normal and luanch it through that.
Oh also, make sure if you use openXR toolkit, make sure you have DCS disabled for it and if you have OpenComposite, just delete it. Otherwise, you will get about 5fps in the game.

Edited April 5, 2024 by Shibiswag

[Nano]

I just got my Meta Quest 3 yesterday and I can say I was able to test MSFS2020 using OpenXR (So the device seems to work on VR with cable link)

When I tried to run DCS with VR support, I simply launched DCS, went into settings enabled VR support and when clicked "Save" the app exited to the desktop, in order to launch again.

Since then DCS was unable to run ever again.

I tried both MT and ST modes.

With and without  --force_OpenXR on the shortcut.

The result is always authorization, nVidia Splash screen, DCS splash screen, then back to desktop - logs attached to the thread.

 

My new pc (just built it 2 weeks ago) specs are:

AMD 7800X3D

DDR5 64Gb @ 6000Mhz

nVidia 4080 SUPER

About 240 GB free space on the disk DCS is installed in, OS disk has 325 Gb free space

Attached as well regional settings on my windows machine.

Windows 11 up to date

Windows AV (No other AV solution)

nvidia drivers up to date

Oculus App up to date (Not PTC)

OpenXR toolkit installed.

 

Need help with this bc the reason for upgrading my pc and getting the Oculus headset was to play DCS on VR for once and for all

 

Thanks!!!

nullnull

dcs.log

[rob10]

[Shibiswag]

1 hour ago, rob10 said:

Don't understand why I was quoted on this but okay.
I myself don't use the steam workaround. I use the oculus fix on page 16 of that thread.
Nvm, I see what you did there. Smart

Edited April 5, 2024 by Shibiswag

[Shibiswag]

1 hour ago, Nano said:

I just got my Meta Quest 3 yesterday and I can say I was able to test MSFS2020 using OpenXR (So the device seems to work on VR with cable link)

When I tried to run DCS with VR support, I simply launched DCS, went into settings enabled VR support and when clicked "Save" the app exited to the desktop, in order to launch again.

Since then DCS was unable to run ever again.

I tried both MT and ST modes.

With and without  --force_OpenXR on the shortcut.

The result is always authorization, nVidia Splash screen, DCS splash screen, then back to desktop - logs attached to the thread.

 

My new pc (just built it 2 weeks ago) specs are:

AMD 7800X3D

DDR5 64Gb @ 6000Mhz

nVidia 4080 SUPER

About 240 GB free space on the disk DCS is installed in, OS disk has 325 Gb free space

Attached as well regional settings on my windows machine.

Windows 11 up to date

Windows AV (No other AV solution)

nvidia drivers up to date

Oculus App up to date (Not PTC)

OpenXR toolkit installed.

 

Need help with this bc the reason for upgrading my pc and getting the Oculus headset was to play DCS on VR for once and for all

 

Thanks!!!

nullnull

dcs.log 14.81 kB · 1 download

It's a bug that has been going on since February when Meta released an update it broke DCS. Has nothing at all to do with your system. ED has already fixed it internally and is going to come with the next patch when they release it this month, the Estimated date is the 10th.
There are currently 3 known work arounds to play in the meantime. 
Please referee to page 16 of the thread listed from Rob10 for the actual oculus link fix.
The 2nd is to add either the MT or ST launcher to your steam launcher and run it through steamVR via the oculus link.
To do this simply go to your steam library, at the bottom select add game, select non-steam game, locate the executable for DCS that you want to add, which I stated above.
Make sure that you select VR mode.
The third option is to run it through Virtual Desktop.
For the Oculus fix it is recommended that you uninstall the oculus app and reinstall it, also make sure all automatic updates are turned off, both in the app on the pc as well as the headset and make sure you are not in the "Public Test Channel" in the app, IE Early beta releases.
Also make sure you have update when powered off on headset disabled. If this is enabled the headset will still update regardless of what settings, you changed.
This can be done by holding down the power button to turn the headset off and unselecting it when the power off menu appears.
You should have V63 of the Oculus app on both PC and headset.
Make sure you back up the three folders before you copy in the new ones from the thread so that way when the patch comes out, you can drop them in to revert back to original.
Also, here is a fix for DCS not running at all as the issue was happening to me and I couldn't figure out why if you just want to play it in standard 2D and use a webcam with opentrack + aitrack. No LED or anything special required as aitrack is facial tracking software that works extremely well.
1. Download Notepad++ if you don't have it already.
2. Delete any DCS shortcuts you have on the desktop as these won't work now.
3. Go to your saved games folder: C:/Users/*Your username*/Saved Games/DCS/Config
4. Find the file called Options.lua or just Options if you don't have file extensions on.
5. Open that with Notepad++
6. Once in do a search (Ctrl + F) for VR
7. look for the option tagged "Enable" It should say true you want to change it to false by typing in false.
8. go to file and save.
9. Create new desktop shortcuts from your main DCS directory if using MT it will be C:\DCS World\bin-mt\DCS.exe
For ST it will be C:\DCS World\bin\DCS.exe or whatever corresponding drive you installed the game to. C is just the default.
Game will now launch without VR and go to standard 2D.
Do not change the VR back on once you're in the game.
If you want to re-enable VR, just do the exact same thing with the options and change it back to true if you want to try the oculus/steam/VD fix.
Though obviously this option would be for if none of those worked.
the only other way would be to just delete the DCS folder in the saved games, along with the desktop shortcuts This would require you to re-set everything up, controls, graphics, etc... upon relaunching the game from the main install folder.

Edited April 5, 2024 by Shibiswag

[rob10]

51 minutes ago, Shibiswag said:

Don't understand why I was quoted on this but okay.
I myself don't use the steam workaround. I use the oculus fix on page 16 of that thread.
Nvm, I see what you did there. Smart

Sorry, I just linked to that thread generally and you happened to have been the last post apparently.

[Shibiswag]

2 minutes ago, rob10 said:

Sorry, I just linked to that thread generally and you happened to have been the last post apparently.

No worries, I wrote a lengthily fix for him to do as well and the exact page # where he can find the link to get the folders for oculus.

[Nano]

Sorry for some reason, I'm receiving no replies in my inbox.

If I download the folders for the older version, stop the oculus service and replace the folders, the oculus software crashes on launch (attached screenshot)

[Grodin]

4 hours ago, Shibiswag said:

I have the headset connected directly to the computer.
Don't have wifi on my PC.
I have USB-C 10Gig cable

Don't have Wifi on my PC.
I connect my headset via USB-C 10Gig cable

 

But for VD you connect headset to router with wifi and router to your computer with a cable. Quest 3 cable support seems pretty much abandoned, doesnt work very well for many people compared to VD. You can't use virtual desktop with a cable, only by wifi to the router.

[Nano]

Nevermind, got it to work. Now DCS is working. 

 

 

Thanks!!!

[Shibiswag]

1 hour ago, Grodin said:

But for VD you connect headset to router with wifi and router to your computer with a cable. Quest 3 cable support seems pretty much abandoned, doesnt work very well for many people compared to VD. You can't use virtual desktop with a cable, only by wifi to the router.

Yeah, I actually bought it and got it working, really impressed. Definitely notice a huge difference. I get anywhere from 890Mbps-1Gb from my router for wifi6, so the headset has plenty of bandwidth.
Haven't tested it in multiplayer yet, but single player running smooth as butter at 90FPS with MSAA X2 and everything set to High in game, except water, terrain, and shadows. Hell, I can even have SSAO and SSLR on as well.
So, if it goes good in MP, then I'll just use that going forward.
I was wondering maybe I could connect it to the PC or an Outlet with the USB-C still just to keep it charging while it's in use.
Idc if it's wired or wireless, just want good performance.

Edited April 5, 2024 by Shibiswag

[slughead]

37 minutes ago, Shibiswag said:

I was wondering maybe I could connect it to the PC or an Outlet with the USB-C still just to keep it charging while it's in use.

Yes, you can do this. It is probably best to use the wall charger that came with the headset, as it will probably deliver much higher power than your PC USB-C can. I bought a second Meta wall charger to keep the headset charged and kept the original to charge the hand controllers. The headset will still discharge, and maybe more so whilst using WiFi for VD.

[Shibiswag]

53 minutes ago, slughead said:

Yes, you can do this. It is probably best to use the wall charger that came with the headset, as it will probably deliver much higher power than your PC USB-C can. I bought a second Meta wall charger to keep the headset charged and kept the original to charge the hand controllers. The headset will still discharge, and maybe more so whilst using WiFi for VD.

Thank you for that.
Yeah, I noticed that after only an hour of flying it went from 100% down to 31%.
So definitely going to plug it into the wall while running Virtual Desktop. Overall, I like it. However, I am noticing one drawback and that I'm getting ghosting. Not in everything, and more so imparticular in flyby view in F3.
I have a 10ft USB-C 10Gig cable so more than enough length to connect the oculus plug from the wall to my VR.
I don't even use the controllers, so no need to worry about them being charged.

[slughead]

1 minute ago, Shibiswag said:

Thank you for that.
Yeah, I noticed that after only an hour of flying it went from 100% down to 31%.
So definitely going to plug it into the wall while running Virtual Desktop. Overall, I like it. However, I am noticing one drawback and that I'm getting ghosting. Not in everything, and more so imparticular in flyby view in F3.
I have a 10ft USB-C 10Gig cable so more than enough length to connect the oculus plug from the wall to my VR.
I don't even use the controllers, so no need to worry about them being charged.

For complete wireless, you may be able to get a battery pack that mounts on the headset or put it on your belt.

[Grodin]

1 hour ago, Shibiswag said:

Thank you for that.
Yeah, I noticed that after only an hour of flying it went from 100% down to 31%.
So definitely going to plug it into the wall while running Virtual Desktop. Overall, I like it. However, I am noticing one drawback and that I'm getting ghosting. Not in everything, and more so imparticular in flyby view in F3.
I have a 10ft USB-C 10Gig cable so more than enough length to connect the oculus plug from the wall to my VR.
I don't even use the controllers, so no need to worry about them being charged.

 

ASW causes ghosting in external views (its motion reprojection) try unchecking that from the VD options. Disabling it will lower fps tho because it essentially creates fake frames, thats why you noticed such a huge performance jump.

[Shibiswag]

2 hours ago, Grodin said:

 

ASW causes ghosting in external views (its motion reprojection) try unchecking that from the VD options. Disabling it will lower fps tho because it essentially creates fake frames, thats why you noticed such a huge performance jump.

Okay, Ill tinker around with it. It's not really an issue when I'm in the pit, not even in F2 or any other view, just the flyby view, so it's not really a big deal from what I've noticed so far.

3 hours ago, slughead said:

For complete wireless, you may be able to get a battery pack that mounts on the headset or put it on your belt.

True, I have a pretty good size battery bank for my phone, was thinking about mounting it, though not too keen on having the extra weight, I have the quest pro which in itself isn't exactly that light, at least not as comparable to the quest 2 or 3.
Plus, I'd still have to have a cable going from the battery to the headset which would require me to go buy a shorter one, so not really wanting to spend extra money on something when I'm going to have to plug it in anyways.
The way I have the cord routed to the wall it's not in the way of anything so i still get full rotation on the headset without the cord getting in the way.
I apricate the suggestion though.

[Shibiswag]

5 hours ago, Nano said:

Nevermind, got it to work. Now DCS is working. 

 

 

Thanks!!!

Nice, glad to hear it! Cheers mate!
What was the issue with Java that wasn't causing it to work?
Did you not have it installed or something?
Just curious.

Edited April 6, 2024 by Shibiswag

[Nano]

13 hours ago, Shibiswag said:

Nice, glad to hear it! Cheers mate!
What was the issue with Java that wasn't causing it to work?
Did you not have it installed or something?
Just curious.

 

For some reason, I was removing the newer folders and unzipping the older versions as new folders.

I had to copy the contents of the old version into the new versions folder and replace all.

[Shibiswag]

1 hour ago, Nano said:

For some reason, I was removing the newer folders and unzipping the older versions as new folders.

I had to copy the contents of the old version into the new versions folder and replace all.

Ah yeah, that would do it.
I made the same mistake initially but didn't get the Java error. 
It just wouldn't start up for me at all.
So, I reinstalled it, copied the original out as a backup, copied the new folders in and replaced and it worked.
Though right now, I switched from oculus link to Virtual Desktop. Works right out of the box since it uses SteamVR as an interface, but game runs smooth as butter and actually looks better IMO.
It's $20 bucks on the oculus store, no work around needed or anything, it just works.
Doesn't matter what version of Oculus you have.
My system:
Ryzen 9 5900X @4.8 all core
64 GB DDR 3200
7800XT 16GB

[Flyingfish]

I have V63 in both the headset and the desktop app and it was working fine. I then upgraded from windows 10 to windows 11 and it stopped working so I reverted back to windows 10 and it works again. Might be useful to anyone who is on windows 11 but can't get DCS to work with V63, hopefully not too long to go till the update though