unlikely_spider

For what it's worth, the headset itself states v62. Just last night I turned off auto-update in the headset.

Yes, it is in my original post above (I am not at my PC at the moment) I have a Quest 3

I as well haven't experienced issues. Running MT. Oculus software v63, headset still seems to be on 62 though. dcs.log

I went from a G2 to a Quest 3 and I consider it an upgrade for sure, in most ways except for comfort. The lenses are much better. And strangely I don't seem to be affected by the recent Oculus update, but I do know that there are many who are.

Yes, that was it, thanks. Man, there are so many dependencies between the systems that aren't immediately apparent. Coming from the Hornet, this thing really has me working trying to understand the sensors and targeting logic.

Oh, good to hear, and glad that it's sorted. And any experienced PC builder will have plenty of embarrassing stories (I have a few for sure) so it's nothing to be self conscious about! Happy flying.

I think that 95 degrees is pretty hot. Especially after 60 seconds as your screenshot shows above. Are the fans running at high RPM? Is there enough airflow? I'd make sure it's not running in silent mode or the like, if you can't tell that the fans ramp up. At that temperature they really should be making a racket. Edit - I can't definitively confirm but I think 95 is where thermal throttling would start. In my opinion that's the issue here.

Download Furmark. Run at high settings so that your GPU is near 100%. It will tell you the utilization and the temperatures.

Clean Nvidia driver install? Is the GPU getting enough power? Are temps on the GPU good? Are you able to run a stress test on it for a satisfactory of time? Make sure the graphics card is set completely into the PCI slot as well.

I can't seem to get to the GMT or GM radar modes in A-G mode. I have to be in Nav. Is there something that needs to be enabled for me to use GMT while in A-G mode? I can find a target using the GMT radar while in Nav mode, but then when I hit A-G, it resets everything of course and I lose it.

Very nice update, and I hope everyone on your team is healthy and recovered. Thank you for your contributions to our great hobby. Looking forward to spending time in this cockpit when it's ready for us.

I get the occasional audio stutter, but the video is fine. A minor annoyance but would be nice to solve. Using a third party USB cable.

Hmm... I am currently on Meta Quest Link app version 63.0.0.216.361 and played last night for like 2 hours with no issues.

That made me chuckle. Thanks for the warning though

Isn't there a way to just change the device ID in your existing user config file?

That's what I settled on as the best mix of image quality and performance. DLSS was too fuzzy on the cockpit instruments with too many artifacts outside (though performant) so I turned it off. DLAA works very well for me.

I've used Corsair for a long time and tend to trust them. I would just stay away from Gigabyte - they are the one recent PSU I bought that wasn't Corsair and was recalled very shortly thereafter due to a tendency to explode

Sadly, I agree that this is a potential cause. Nvidia recommends a 650w for this GPU I believe. Edit - though I'm reading on Reddit that people say they're using 500 or 550w PSUs with no issue. Unfortunately it's physically one of the hardest components to replace

As a veteran PC builder I've had a couple embarrassing incidents where the DisplayPort connector wasn't fully "clicked" into the port. Make sure it's all the way in. Edit - also, what's your PSU?

Well, maybe. I didn't want to spring for the 4090 and the associated power demands though. I do notice a little stuttering at times when I look down at buildings in dense areas if I'm down low, particularly when I'm rolling rapidly. But it's not bad enough for me to spend too much time on it, and it even got better this last patch. Some things help, like lower resolution, no AA, or lower quality textures, but I don't like those so I make that tradeoff.

Sorry, I can't really give good data since I don't chase frame times or rates. I just mess with the settings until it seems acceptably smooth to me. I have the Quest resolution all the way up in the Oculus software, pixel density of 1.1 in DCS, textures to high, DLAA, and most other things to Medium.

I have a worse CPU than you and a 4080. I have a great time in DCS with a Quest 3. Go for it - you'll be happy.

Well, maybe they've got a point. I've spent tons of money on flight sim peripherals and software, and it turns out that all I had to do was completely upend my entire life to join the military and they'd pay me to do the same? It kind of reminds me of the late 80s, when every kid I knew dreamt of being a plumber when they grew up. Most of us didn't end up going that route, but I'm sure for the ones who did that they are in constant sense of self satisfaction that they're able to earn a living by jumping up with their fists and punching boxes in the air until money stops coming out.

The default is for the headset to sleep almost right when you take it off. Somewhere in the settings is one that I changed to 15 minutes I believe. I could be wrong but I think that's the cause.

I have not yet downloaded the patch to verify, but you can just check to where the shortcut is pointing to see if it's still accurate.