sze5003

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.

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.

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%.

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.

Internally it's 200 but the actual default in oculus debug tool is 0 for bitrate.

Yup im familiar with that one. I've also tried parking each core that shoots up to 100% and then the next one just assumes all the load. No clue if that is supposed to be happening but all the suggestions from there haven't helped. I guess the only thing I have not done is roll back to 2.8.

I was only able to have one stutter free session last week. It was after I installed the latest Nvidia drivers and then deleted fxo and metashaders. Then I shut down dcs, and launched it later that night and it was back to randomly stuttering in instant action missions. HAGS was still off but after this I turned it back on because I was also playing Alan Wake 2 where you need it on for frame generation. I also tried disabling hyperthreading but that didn't seem to do much either. I run 500 bitrate with 90hz and oculus home resolution at 1.0. Hoping to have more sessions like the one I had Friday but so far the stutters in flight have been pretty sporadic. There's no more tweaking for me to do as I've done it all. Last thing I can do now is install quad views.

Same thing I'm noticing. I have tweaked as many settings as I can. I lowered my bitrate for my quest pro headset too, tweaked windows os, turned off HAGS, unparked cores, parked cores, disabled hyperthreading, disabled efficiency cores,etc. The stutter and drops are very random and some days are very bad whereas randomly one day I'll do an instant action mission and everything seems fine. More often than not there are more stutters overall than not at all. Hoepfing for a fix or patch in the future so I don't have to roll back to 2.8. I've even reinstalled DCS on a different SSD thinking maybe the drive was going bad.

Some say it helps in dcs and others say they don't notice a difference. In other titles this helps with DLSS implementations.

Update: I'm convinced DCS MT version isn't using my CPU properly. Using processor lasso I noticed CPU core #8 is 100% and other cores not taking much load. So I uncheck core #8 from affinity and then core #9 is the one taking 100%..uncheck that one and then #10 is at 100% so I continue removing them from affinity so on until core #11 is then taking 100%. After I remove #8-11 from affinity I then start seeing a random e core at 100% while the rest again are not sharing load. No clue what to make of this.

So I installed processor lasso last night to see maybe that is why MT mode is stuttering me for me so much in VR. While I'm in an instant action mission I notice processor lasso reporting dcs is using 5% of the CPU. I see CPU #8 at 100% others doing squat. Nothing crazy running in the background, windows is optimized, drivers up to date,etc. So I park #8 using lasso affinity and then #9 goes to 100%. I do the same to 9 and 10 goes to 100%. Same thing for 11..after parking all these I notice a random e core is always at 100. Not sure if it should be behaving this way. Single threaded DCS also has stutters even on lowest settings with constant 90fps or 45 if ASW is on. But they are not as severe as Multithreaded mode.

I have seen the same thing happen. With e cores disabled instead of CPU #8 and 10 and being hammered at 100% it's two other cores. Eventually if it does freeze I go into task manager and select affinity and uncheck CPU #8 and then it unfreezes. Im on a 13900k and 4090.

My oculus debug tool says Default under the encoder I'm not seeing h265 selected. My headset just updated last night to v59 too.

Also tried disabling e cores. Instead of cpu #8 and #10 taking 100% of the load it was #11 and #16 taking all of it. It still stuttered and the stutters happen as I'm watching the fps dcs chart, as soon as I see the frame time graph spike up and down that's when I get the stutters. The longer I'm testing the worse it becomes it seems.

Mine is set to Normal by default. What I did do was download oculus tray tool, then in oculus home settings I set the headset to 72hz , set the slider to 1.0. In oculus tray tool I set super sampling to 1.6, encode resolution width to 3905, and bit rate to 650. I have pretty much all high settings in DCS, SSR to on, and terrain object shadows to flat. Visibility to extreme, clouds to ultra, water high, shadows high, civ traffic off, MSA x2. I noticed less stutter but it's still there. CPU graph seems a bit better for some time but it randomly has spikes up along with the fps graph spiking at times too. Normally asw stays on when I'm low at 36fps and 72 when I'm up higher. For the timea it's not having random stutters it looks great and feels smooth. Also I noticed CPU 8 and CPU 10 constantly at 100% while other CPU's aren't helping much. So I went ahead and disabled e cores in bios but then in resource monitor while dcs is on I only see CPU 11 and 16 working at 100% and others are not getting shared load. Not sure if they should be. Sometimes if DCS freezes or drops fps drastically I have to go into affinity and disable CPU 8 and then it unfreezes. Not sure what to make of all this but I think I'll just renable e cores and try installing quad views now. I don't think I'll ever get it running smoothly and I've tried just about everything.