Tomcat388th

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.

I ran into this when I was using Air Link I had to set my Encode Bitrate to 0 to fix the problem in Oculus Debug tool. I use the link cable now and I set encode resolution to 3902,encode bitrate 400,spacewarp disabled, link sharpening enabled and pixel per display override 1.15 My quest2 is 90hz 1.3 4224x2128. I would start bumping up the encode bitrate and see if that helps. J

Thank you I will give that a try this week when I fly with the guys J

Pepin1234 I was in the same boat as you awhile back with an older system. I still consider what I have right now a budget system computer wise but have been really pleased with it. I average around 70-80 fps with my quest2 along with the openxr toolkit to finetune dcs J

When on the LSO platform is there a way to be able to talk to other sqaud members with SRS when not slotted to a jet like if you were in the spectators section thanks J

One thing that I did to help was moving my windows taskbar from the bottom to the left side of my screen. Plus there are the options in the DCS config screen and vr to confine the mouse.

For me i get a little shimmer right at the horizon line even on missions I build

I sent in a support ticket to Meta they had my send in troubleshooting log file which showed some errors. No idea what kind. Had me do a repair of the oculus app and everything is back to normal plus I was able to max out the slider for 90hz. On 4YA's Syria server I was pretty well locked in at 45fps I will probaby back the slider back a couple of clicks just to give me a little wiggle room J

My app is 53.0.0.98.132 headset 51.0.0.182.268

My oculus software updated a few day ago and for me it messed with the 90hz option. I'm running 4128x2096. While flying about ever 10 seconds the headset acts like it loses tracking for a spit second and the whole image jumps. 72hz and 80 are working fine so far. Just though I would post this in case someone else was chasing their tail trying to figure out what was going on. J

I get confused on which pixel setting does what and in which program. My DCS pixel is 1.0. I copied the debug tool settings from one of the oculus pro post in this forum. I was just experimenting around and was surprised oh how well it worked. I believe in their post they had a 4090 card and could run the oculus software at 90hz and the slider maxed out. I started out with the slider maxed and just started working my way back down until I found the balance of fps and clarity in the jet. I done all my testing on the 4YA Syria server it seems to be the most demanding for my rig to keep up.

Here are my latest setting with my quest 2 +link cable. Oculus software 90hz 1.3 4128x2096. Oculus debug setting in attached file. SP or MP I'm in the 45-60fps depending on the mission. Not sure if my signature is up to date ryzen 5800x3d 64GB ram radeon 6700xt ssd hard drives. I have a little shimmer on the horizon line but everything else is nice clear. Here's a couple of sceenshots in MP. This is openbeta and DCS multithreading .exe and forcevr/openXR shortcut. Jnull

Your Welcome

heres the work around that I ended up doing with the f18. This was the file failing IC ck for me Dcsworld openbeta\mods\aircraft\fa-18c\cockpit\scripts\device_init.lua Before you start VA Do a quick repair of dcs then go to the int_device lua right click then on properties make it read only. Mine was the one in cockpit scripts that was failing the IC ck. All the radio commands will work but the down side no interactive kneeboard. But it wont trip the pure scripts check or give you the red shield And you can join any MP server even if it has pure scripts active like hoggit and such. And lastly with this method when DCS has an update come out you have to change the file properties back, after the update change it back to read only. And one other workaround if you don't change the int_device lua. But this is only for MP servers that are not using pure scripts. You have the red shield showing. Just click on the server you want to join and on the left you will see the IP address listed then click join by IP enter the IP plus the password this way you don't have to restart dcs after every misson. You can go from one misson to another. But if the server has pure scripts enabled you will get booted out. I stopped using Vaicom, when it worked I loved it but I had a lot of issues and they alway showed up during MP with our squad. I just use voice attack now with a handfull of commands J

No change for me also slow repair and deleting fxo and shaders but its still playable for so at least thats a plus

amd 5800x3d 64gb 3600 ram 3060 12gb gpu. HP G2 ver 1. In the main menu screen with the fps counter on it shows CPU bound. I have a simple refuel mission f18 fps counter shows cpu bound render thread and cpu main. As for any gains i might of improved 5 fps with my G2. If I swap over to my quest2 it has lost fps and has a bad stutter. In a level turn about every 4 seconds you can see it hesitate. I know my 3060 will be my bottleneck but I'm surprised with the cpu message. dcs.log

Here are my settings but mycpu is a 5800x3d and my ram 3600 the rest is the same as yours and I do run airlink. I will only note what settings I have different from your screen shots Quest2 90 Hz4128x2096 nvida cnt pnl anisotropic filtering Application-controled antialaising mode Enhance the application antialaisning setting 2X DSR factor OFF MFAA OFF Shader cache 10GB Texture Filt Negative lod Clamp Texture Filt Quality VR pre rendered frame 3 Ocululus tool tray Game settings tab Default Super Samp 0 Adaptive gpu scaling on Link Tab Distortion curve high Encode res 3960 Encode bit rate 0 Sharpening enabled Dcs Res of cockpit display 1024 Anisotropic filt 16x SSA 1.5 Pixel Den 1.0 I'm also using the openxr toolkit using FSR upscaling with 90% size and 40% sharpness These setting are pretty well giving me a solid 45fps whether I'm in SP or MP even on 4YA's Syria server. This is using the oculus runtime and the force open xr shortcut for DCS. J

yes just MP SP ok

I have been fighting this for awhile resetting the toolkit helped me for a bit but it started to hang up again in MP hit the fly button and that is as far as i would get. The final fix for me was a slow repair again with removing any extra files box checked.. I backed up my dcs saved games folder and moved it to another folder then deleted the original so DCS could build a new one. For me I believe it vaicom and voice attack getting corrupted with something in my save games folder. I loaded everything back up and I could repeat my problem. Now I'm just running voice attack along with srs and the open xr toolkit. Everything is running really nice now. All my troubles started after this last update I rarely had a problem unless it was self-induced.