Tomcat388th

Here are my Quest2 settings I'm running the same cpu and gpu as you with 64GB ram. I had trouble with OTT getting corrupted at times so I use the oculus debug tool for the extra settings. One other setting that I did do was in the amd gpu settings set max frames to 45 for me it really smoothed things out. If the cockpit seem to large on the dcs vr page change the force ipd num to scale it up or down Hope these help J

For those of you that use the open xr toolkit. In the appearance tab and I believe under post processing. There is the option for sunglasses with 3 different selections light, dark, true night That does a pretty good job of taking the edge off of the glare Plus you can tweak the colors to make the outside world look a little better J

The trunk popped open last night during our training night but this time it was cat 1 not 2

Got everything setup and working this afternoon eye tracking is the bomb I pushed density up to 1.6 in the oculus debug tool just messing around and then got on the 4ya syria server. On the ground 45-50 fps smooth and about 500ft off the ground 72 and never fluctuated. J

Mbuccia Thank you sir I bought this quest pro used without controllers thinking that I had read that the quest 2 controllers would work. I'm waiting on a pro controller. As of right now it still has another profile and I need to do a factory reset so I can pair it to my phone. Which I'm nervous to do I did the reset on my quest 2 last week and it bricked it. Headset fires up fine and does the start up to the pair code but phone app will not pair and no selection to manually enter it. Any way I'll use the pro as is until the stuff comes. I do like the pancake lenses clear and sharp J

I'm trying to get my quest pro going with DVR not sure if I have missed something or what. This is what I have done so far. Open xr tool kit set to safe mode entered game and reset to default. Back to desktop and installed quad views. On the headset eye tracking is enabled and calibrated and works in the test. Using DCS openbeta mt exe. Dcs stand alone Splash screen shows in the headset and desk top. The headset spash screen will go to a generic grey back ground with loading when that happens the desktop will have this image. This is as far as i get. Also this is using link cable. Picture and log attached J Quad-Views-Foveated.log2.52 kB · 0 downloads

I have a Q Pro on the way, hopefully later this week. I have been reading up on the install process with M bucchia programs. With the Q pro other than enabling eye tracking in the oculus software is there any calibration setup or is it just off or on. This will be an upgrade from my Quest 2 . I'm running a 5800x3d 64ram ssd and a 6950xt Open Beta stand alone Thanks J

I just pulled the trigger on a used quest pro on ebay it fit my price range. Has 30day return if I don't like it will be upgrading from Q2 curious to see how much of a difference the eye tracking will be and clarity compared to my Q2 once everything is dialed in. J

With SC sometimes I feel like I bought a used car from dealership that the trunk keep popping open while driving. Take it back to the dealership and they say well it was closed when you pulled in. If it happens again call this number they'll get back to you in 2 weeks. My only concern is if we finally get the full deck crew that it's going to tank performance for those of us on mid range rigs especially in VR J

I have had the problem at times where in MP after I choose my slot I will not get the fly button after clicking brief. DCS will hang and I have to use task manager to exit out. For me the slow repair fixes it but the regular fast repair will not. J

I had this happen once before had to do a repair of the oculus software and had to do it on this latest oculus update. I was getting a hesitation about every 30seconds looked like the headset was losing track just enough to make the image twitch. Go to meta's website and select the software download for your headset. when you run it there will be the option to repair.

If it ends up being a cable problem I have been using a Kuject 3.0 link cable from amazon for a couple of years now. It charges while you play and speed wise it test out at 2.9gb with the oculus link test

Thanks for the reply I have been pleased with it so far J

The only things that come to mind is maybe the headset is loosing usb cable connection. I have mine zip tied to the headset close tothe plug so it doesn't wiggle plus I had to plug my quest 2 into one of my motherboard 3.0 usb ports on the back to get the best speed. Another thing which still ties in with your usb ports open up device manager in windows and click on the usb items then open up the propeties tab. In that tab you will see power management click it and under that menu make sure to deselect "allow this computer to turn off device to save power". You will have to go through each one to do this. I was fighting my keyboard not responding mid mission in dcs and this fixed for me. I just upgraded my gpu from a 6700xt to a 6950xt and I have the red warning now in oculus. From reading on the net in my case it not on the list as a tested card or something like that. And lastly have you put in a troubleshooting ticket with Oculus support I used them a couple of times and they have been quick getting back and helpfull. And one more lastly are you able to try dcs with airlink to see if the headset still drops out J

I got it figured out from your track. I did not realize you could link a static object to a unit Thank You J

I'm trying to simulate the carrier still underway but with the flight deck having a huge fire. Is there away to link the huge fire and smoke from the trigger list to the carrier. I tried the attach unit in the create trigger zone but nothing happens. J

I see the tab shows investigating We had it happen again last night during a squad mission night. During launch Cat 2 and Cat 3 would not hook up jet no action from flight deck crew and JBD 2 stuck up . Cat 1 and 4 were working this was on CVN 73. Cvn 75 worked fine for the guys launching from it. I attached the miz file Falklands if that helps any Operation Wipeout.miz

Thank You J

Not sure if this is the right forum if not please move it . Any way I live out in the sticks and have been using US cellular as my internet provider for the past couple of years. Other than having 2 seperate accounts 1 for my wife for working from home and the other for myself for DCS and our TV's I have 0 problems other than the cost and data cap. Anyway we have access to Star Link now and I was curious if anyone is using it for gaming of any kind. Thank You J

I have seen some older post about this and have seen it in my own missions and I believe its a MP problem not recognizine the Group in zone command. One work around I have read about is to use "Unit in zone" which I will be trying this week with our wing mission to see if it works. I am just learning to use mission editor and it trial by fire for me at time's. J

I will soon be getting a 6950XT from Ebay. I'm currently running a 6700XT and have been happy with it. Was just curious if anyone is running the 6900 series and how you like them. I'm running a Quest 2 J

Yep that was the post I've have been happy with these setting for my Quest2 I consider my system mid range. MP servers run really smooth and I have a nice clear and readable cockpit F18. For anyone looking at my screen shots this is for my quest 2 setup I dont want to derail the original post

Just bumping this back up again would love to hear some feedback from ED. At least the LSO board got fixed for super carrier stable CVN-74 USS John C. Stennis No Number in LSO Display. This was really taking away from the immersion with the JBD's stuck up.

Did you get openxr tool kit running ? As for your quest setting I see that you have default ASW mode as "adaptive" select disable Adaptive gpu scaling select Off or disabled. and on the "encode dynamic bit rate" select disable and see what happens. I think I mentioned it before I had nothing but grief with traytool with my system it would say there was a update even though there wasnt and the only way to clear it was to reinstall. And another problem my keyboard would quit and exiting out of traytool would fix it and lastly it would lose my profile. I know a lot of people used it but it hated me. And all traytool is doing is changing the settings in the oculus debug program. If you want to try debug its in your oculus directory.Mine is here "C:\Program Files\Oculus\Support\oculus-diagnostics\oculusdebugtool" I made a shortcut on my desktop takes me about 20 seconds to put in my settings. The only downside if you have to restart your computer you have to reapply the settings. You can kind of compare my settings to your traytool setup J

I dont know if this would even apply since I'm running a quest2 but here is what I'm running with link cable. The encoding and bitrate numbers I got either form this post or another quest pro post.