Tomcat388th

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.

I'm running a 6700xt which is no comparison to any of the cards you listed but I have been very pleased with the performance/visuals I'm getting with my Quest 2 and the latest AMD drivers. I know AMD had some issues with the 7 series drivers but I think they're finally getting them ironed out. My system is in my signature I'm using an asus b550 prime plus motherboard. j

On the dcs vr page force IPD setting of 30 you can change that number to scale the cockpit size to what you like. You may of already done this and I might be wrong on this so any expert feel free to correct me. Check one of your modifiers I use ctrl if you havnt already. With safe mode checked go into DCS and I can't remember if toolkit gives you an opening message to do the reset with CTRL+F1+F2+F3 or if you have to do CTRL down arrow to open it up, then hit the keybinds for a reset. Once that is done back out of DCS deselect enable safemode in tool kit and them go back to DCS and hit CTRL down arrow to open up the toolkit menu. Adjust whatever you want and I think when you exit out DCS should show up on the toolkit list. Also on your tooltray under the quest link tab what are your settings. Plus I never did like the default ASW mode I found having it disabled gave me a smoother experience. I'm locking my frame rate to 45 in my vid card settings this is something that you do not have to do.

Here is what I run. Our setups are really close other than Vid cards,I'm running a 6700XT and Win10. I use the oculas debug instead of the traytool. I had trouble with traytool getting corrupted and having to reinstall it no idea why. In the openxr toolkit I use CAS upscaleing at around 40% and turbo mode on. Also in the tool kit if you go to the apperance tab you can adjust the brightness contrast and exposure setting to get a better overall look of DCS. Plus on the sunglasses tab if you click on the first option which I think is "light" the hud won't get washed out if your looking into the sun. And for night flying I use the "true night" I think it helps with the darker backgrounds. I read on one of the post about locking the framerate to 45 fps on my video card setting which I have experimented with and so far DCS has really really smooth. Single player missions and campains I'm usually maxed at 72fps on the dcs frame rate display busy carrier might dip into the 50's but still smooth. Multiplayer the only server's that I have lower fps is the 4YA one's especially Syria. On the ground 36 and once in the air back up in 60 plus but still really smooth even on the ground. Might have a stutter every once in awhile but nothing that will ruin gameplay. Other MP servers I'm in the 60 plus again. I'm running the DCS MT.exe with the force VR&Open XR options and using the Oculus runtime. Here are some screenshots of my other settings. Hope this helps and I am no expert on any of these settings but I have a nice clear/sharp cockpit very very little shimmer J

I have a quest 2 and a reverb g2 ver 1. I mainly use the quest now, I feel that their latest updates have put it on par with my reverb for performance and clarity. I have used their customer support a couple of time when I had questions and they were quick getting back to me.

The only problem I had was I could not get it to recognize any input from my hotas as a recenter bind for dcs but hitting a key on the keyboard worked fine. Other than that its working fine I have mine set to the scroll lock key. Running the latest open xr version with a quest2 J

My launch sequence 1 Turn on my quest 2 let it boot up to your home environment 2 I use the oculus debug tool so it gets started next. to tweak my link setting. 3 Back to the headset and turn on oculus link 4 Start DCS I use the MT exe with the force openxr and VR commands as stated above

Mole I have been using the openxr toolkit and under the appearance tab you can adjust brightness,esposure ,contrast does a fairly decent job of improving the landscape. Plus with the sunglasses option "Light or Dark" activated the hud doesn't get washed out as bad and I can see it even in direct sunlight. Here are a couple of shots in South Atlantic. My DCS gamma 2.6 and if I fly at night I will use the true night sunglasses option I think it helps with the darker colors against the sky, less banding. These pictures are through my quest 2 J

Just to bump this back up Cat 3 JBD stuck during our Thursday night MP Squad mission, South Atlantic. Made for some interesting recoveries J

Our squad fights this all the time absolute pain in the butt. If it not the JBD stuck up, its none or just 1 of the catapults working. Most of us have to do a cat 5 launch. Every once in a while it works with all 4 cats in operation but rarely. J

I run my quest 2 at 1.3 4128x2096 and I use oculus debug instead of OTT it seemed to give me fits with losing its settings. These setting give me a nice clear cockpit F18 and smooth gameplay SP or MP. Your DCS in game setting are about the same as what I run. fps run around 55 fps and up with link cable. I'm running the DCS MT shortcut with the force enable vr_ openXR __ My spec are in my signature J

Thats hilarious. I'm erroring out on 502 also.