sze5003

I still am having a lot of trouble with this one. Yesterday I was seeing some odd behavior with the F16's not merging into me, they kept flying off in the distance past me. That and Chig kept dropping lock. No mods installed so I did a long clean and repair and it seemed to have helped. But 3 times now I've been shot down before the merge even if I notch right when Paco says notching. I come back left when I hear the tone go away but then it comes back and I ended up getting shot down before the merge. Uploading a track since I have no idea what I may be doing incorrectly but it feels like in this track I at least got killed after the merge? Hardest part after the notch is acquiring a lock manually since Chig is no help here. Not giving up but probably will take a break. f14a.trk

I haven't passed this one yet, run 1 went fine for me. Run 2 Chig always drops the lock if I roll to 320. Even staying too long on 310 you have to watch the TID and correct more to the left once you see the targets go too far abeam. My understanding is you do want to fire your phoenix here and then crank right but this means not just following what Paco says, basically think outside the box which also means do whatever you need to keep the target locked.

Check the qvr log to see if there are errors. Usually after a restart it works.

In VR it's a little easier but once I get a "good job" in close parade and then Paco starts turning or climbing unannounced and i have to keep up with him, makes it much more difficult because he changes pitch too much. I still did not pass this one yet but I did notice staying somewhat close to him does not trigger the "you're too far" message where you have some wiggle room to correct and try to stay close until the grade pops up.

If anything that is what you do in the first mission of the speed and angels campaign. You can replay it as many times as you want to get better. You will be graded on the maneuvers and landing. There are some important concepts in that first mission like level turns and maintaining speed, and vertical maneuvers.

I did the in game tutorials. Landed on the boat a few times, did the landing on an airfield a few times too. Then I purchased the speed and angels campaign. It will teach you to fly the plane correctly. For any of the issues in the campaign I just look for playthroughs of it on YouTube.

The same thing happened to me! I'm glad I was able to get through the mission but I'm not even upset. I'm learning to improve with each retry. Having some issues with axis interference because I'm using a quest pro and I have a wifi 6e router right next to my PC which apparently interferes with my vkb mcg pro making the axis movement jumpy..I'll manage. I love these types of campaigns because hands on with instructions like this is how I like to learn.

Whether or not the headset will maintain charge on an official cable will depend on your motherboard's USB C port and how much power in can deliver. Mine supplies enough power that it does deplete the charge on my quest pro but it only goes down about 10-15% in 1-2hrs.

If you set VD to God mode it helps with the visuals some but still not as crisp as link cable from what I saw. But again that mode will be more taxing on a title like DCS compared to other games. Personally I prefer link cable as performance was similar and I never have been able to rid of the microstutters but at least with link cable and quad views they have just become more tolerable.

I came from a G2 and I use primarily link cable. The official one because I tried a Kuject one and followed the instructions for connecting it but the oculus app kept saying the connection was USB 2.0 no matter how many ports I tried on the back of my computer. This cable is supposed to charge the headset too but I never ordered a second one to try again after I returned it. My motherboard has a USB C port that keeps the pro partially charged too which is nice. I also tried virtual desktop on a 6e network. It worked but I prefer the visuals of link cable. Performance was similar and I think the use of the oculus app in the background and USB for data transfer creates some performance issues at times.

I have a wifi 6e connection with the pro being only item on the network. I definitely have had stutters in virtual desktop but I also get stutters using link cable with a bitrate of 500. While the microstutters could be dcs, they are intermittent, not related to lowering settings either. I noticed they still happen even with steady fps because I now use quad views foveated rendering which keeps the fps steady but the stutters are still random and intermittent. Last I checked my pro was in version 59 oculus software.

My experience with the 13900k is if I use single threaded instance I still have some micro stutters in VR but they are not as bad since I'm also using quad views with foveated rendering. As for MT, eventually it will freeze at which to unfreeze it I have to unselect cpu 8 from affinity. With cores unparked it still seems dcs only selectively hammers 2 cores to 100% and if I disable those it puts the load on the next one available. Similar experience on windows 10 and then a clean install on windows 11.

I received v59 update a month ago and then a week and a half later the headset updated on its own again. I just checked the version now and you are right it's still v59.172. It may have gotten a hotfix or patch.

For me the audio cutouts have improved slightly with v60. I'm not on PTC but on v59 the cutouts we're much more pronounced.

No I did not unpark all cores. Since it was a fresh install with the latest drivers and everything I wanted to try DCS before I started putting more of my programs on the PC. I will try to unpark them next time I'm on the computer but I suspect the same thing will happen, dcs will just hammer 2 of the cores as it does now and eventually after a while it will freeze until I uncheck CPU core 8 to get it unfrozen.

I recently fresh installed windows 11 and DCS multithreaded still does not properly use the cores for my 13900k. I still have to deselect CPU core 8 whenever DCS would end up freezing, to get it unstuck. I also had to do this one windows 10. At least with quad views installed it's easier to get better fps but the microstutters are still there.

I may have to go to windows 11. Although I'm probably gonna need to do a clean install. I don't trust the upgrade option.

I had/have similar experiences. Yesterday I turned off sliced encoding in oculus debug tool since I fly in VR and after that I noticed less stutters..but I also wonder if I'm experiencing the same thing as you because I've definitely had days where it was smooth flying and nothing changed at all but the next day I would be in dcs for 1 hour or more and notice it either will randomly freeze on me or it would micro stutter like crazy...all random when it would occur too.

I tried H265 on link cable with my Pro tonight. At 220 bitrate it wouldn't smoothly load oculus desktop, it would take some time and the screen would lag. It loaded DCS but it wasn't smooth at all. I had to lower the bitrate to 200 then it was ok. It looked a little brighter maybe more detailed on the outside and the terria but cockpit text wasn't as sharp as using h264 with 500 bitrate. I still had microstutters on h265 with link cable. When ASW kicked on and off it produced some microstutter along with a smearing effect I wouldn't see on h264. I still have microstutters with h264 codec but they seem to happen when the frame/CPU graphs spike. I also saw microstutters in single threaded DCS even when fps seemed stable too with both codes. But I'm convinced multithreaded DCS is not using my pocesor properly as sometimes after a while it completely locks up. If I remove processor 8 from affinity it unfreezes but this doesn't happen every single time so it's bizarre.

That's odd, I have stuttering too in DCS but I didn't consider it to be the headset or oculus link itself. Isn't h265 the default for airlink and for link cable it's h264 because it can achieve a higher bandwidth? H265 is higher quality but limited to like 200-250Mb bitrate. Whereas h264 you can push a higher bitrate so to me it doesn't make sense that there would be no stuttering with a lower bitrate over link..also h265 will push the processor more too on the headset.

That mt.lua didn't make a difference for me unfortunately.

Thanks yea I tried that. It did not seem to remove any of the intermittent stutters. When checking processor lasso dcs was still overloading 1 or two cores to 100%.

No I don't think so. I've been getting bugged from windows update to upgrade to windows 11 for over a month now.

My headset just recently got the v59 update and now it randomly will have white lines appear and disappear randomly, very subtle while using the headset so the updates do cause different issues it seems. I only ever got audio cutouts if my bitrate was over 650. I just set it to 500 and left it at that. Hopefully the next update will smoothen things out because I didn't have this previously.

That's good to know, although in my case I'm still on windows 10 and I only ever had it running to investigate what was happening to the cores in DCS when it stutters and then would eventually freeze, which would happen before the application was even installed.