Tomcat388th

@mbucchia @gonvise Ok that makes sense now I knew I had seen it at one point a long time ago so it had to been with my 3060 gpu Thanks Guys J

@gonvise I'm in the same boat I do not see any option for the foveated or eyetracking in any of the toolkit menus while in VR I;m on version 1.3.2. I'm also using a amd gpu 6950xt if that make a difference. Thanks for any info J

Like the title says horrible jitters/shaking seems to get worse as you look closer toward the hud. Quest pro with quad views rest of my specs listed below J

@NineLine @BIGNEWY I was a one man show on our squads server just now and the cat crew would not activate. I know you guys are always needing tracks so I hope this one will help. J 332AEWTraining_Syria_Stable_V1.11 - Sunrise-20240709-125641.zip

I'll let you know how I feel about this delay in about 2 weeks while I run over the deck crew that wont launch me most of the time in MP.

I'm on Starlink which is also CGNAT I ended up getting a dedicated IP with port forwarding through PureVPN that I use on my small server. And my server is nothing to brag about it an old dell t3600 workstation with a 3.2gh xeon cpu. But I have hosted up to 10 players on some simple training mission and it works fine.

You might already have these hot key commands and I dont know if they apply with the Quest3 but on my Q2 and QPro they worked. CTRL+KP1 - Disable ASW CTRL+KP2 - Force apps to 45hz, DISABLE ASW CTRL+KP3 - Force apps to 45hz, ENABLE ASW CTRL+KP4 - Enable ASW to operate automatically Even though it says on the one option force 45 enable ASW with my headset set at 72hz it would go 36. J

I might be wrong but on the hmd page there a button for blink on or off that lets the hms symbology stay in focus while looking at the hud.

I also run a quest pro but with a radeon 6950xt,64 ram same cpu. I will see a little hiccup here and there if I look to the side and at the terrain but I really have to be focused hard and looking for it. In general its really smooth for me. Here are some screenshots of my settings that I usually run. I'm always messing with setting.s As an experiment last night I reset my quest pro to 72 hz and maxed out the slider then on the debug tool I left the pixel per display to 0 and set asw to disable. I also use openxr toolkit but mostly for setting contrast and colors. I had also set my max frames to 36 for this test with the tool kit. We had 40 guys flying in our mission last night and it was smooth. Hope you can find something that helps J

I do not have the F4 but so far I have been running fine. The only quirk I get is a connection time out on MP yet to narrow it down not consistent enough to know if it me,my network or starlink. Just started happening 2 patches ago. J

These problems have been going on forever, myself and others have brought it up many times if its not this its the JBD's getting stuck up. Hopefully it will be fixed with the next super carrier update but who knows when. Part of our hornet squad has decided to go away from navy carrier ops to marine squad airfield ops because SC multiplayer is such a hot mess. @BIGNEWY any new updates on SC? J

10 4 thanks guys J

At the time it had the best reviews on amazon so that what I went with J

@Special K @The_NephilimI do use the open XR toolkit to adjust the colors a touch but no reshade or anything like that. Game itself is running fine other than it seems like the Sinia missions whether it's SP or MP take a bit longer to load compared to other maps. I had seen the log analyzer and was just curious to how it worked J

I submitted my latest DCS log into the discord log analyzer just to see how it works. For error it came back with this error 2024-05-03 20:31:17.799 INFO EDCORE (Main): system affinity mask: 1111111111111111 2024-05-03 20:31:17.799 INFO EDCORE (Main): process affinity mask: 1111111111111111 2024-05-03 20:31:17.804 INFO EDCORE (Main): CPU: AMD Ryzen 7 5800X3D 8-Core Processor [1x L3 caches] 2024-05-03 20:31:17.804 INFO EDCORE (Main): CPU has uniform cache size 96 MB (per cache) 2024-05-03 20:31:17.804 INFO EDCORE (Main): all CPU cores have the same efficiency class 0... (124 KB left) Just curious if this actually is a problem or not plus I attached the full log Thanks J dcs.log

My Kuject is going on a little over 2 years now been very happy with it. Have used it on my Q2 & Pro J

I bought a used 6950XT that I have been very happy with. My Pc specs are similar to your sons and I use a Quest Pro

Your welcome J

When I'm in TWS mode and its highlighted the first contact it shows the bullseye info for that contact. Is there a way to have it show the curser bullseye position while the contact is highlighted? Tws has highlighted my first contact but lets say there is another group 20 miles away and I would like to pass that bullseye info to another flight just by hovering the radar curser over it. HOpe this makes sense Thanks J

I have to agree with you here . Even though this is not ED's fault they screwed the pooch here. If the Oculus update had messed it up to where no one could purchase mods and such this would of been fixed in the first week. Even though there are work arounds, the meta dcs community got hung out to dry. But on the bright side I have been really happy with how DCS performs now on my system and can only hope that it keeps improving J

I had a similar problem found out windows was putting my usb ports to sleep when flying in DCS. Only happened with DCS any other game worked fine. Go into device manager and under the properties for each of your usb ports/hubs tell windows not to put them to sleep or something like that. Should be able to find it in a google search

Its possible it could be something with your Virpil there are a couple of older post in the DCS Virpil forum where a person had to update their hotas firmware. Winwing had a similar issue with their software it kept polling the game for info and causing stuttering. At the time most people just made sure the program didn't start and windows startup. Hope you get it figured out J

I'm on the latest version of DCS but here are some screen shots of my Q Pro settings with link cable if they help any. On the debug tool screen it shows ASW as auto but I usually have it disabled. In the open xr toolkit I run CAS and I throttle my frame rates to 45. Only other thing that comes to mind is do a DCS slow repair and if there was an app for the blue tooth headphones added remove it.

I'm always comparing oculus usb link and virtual desktop. VD on the A2A page radar elevation text was always fuzzy, not that you could not read it but just not as crisp as the link cable. Not sure which one helped but it seems to be better, now curious to see if anyone has seen an improvement J

If its the team in charge of updating/fixing Super Carrier it might be 2 years.