sze5003

I heard that boresight on the ground will not matter now due to the parallax errors that have been introduced in a previous DCS update. Mission 7 which I just finished you did have about 5 minutes or less to lock two targets or 1, fire a Mav and then turn back and go low and come back quick to get the SA6. Nonetheless I'll try once in mission 8 to boresight on the ground before heading out.

Thanks zooming out does help a little bit. I was able to boresight this way and didn't bother with the hand off modes. I still ended up hitting a light pole instead. I don't think I was able to see the pole before firing.

I'm stuck on mission 4 for some time now. I'm not sure what the proper approach should be. Should I let Bug get the triple A at waypoint 4 and then I attempt to use Mavericks in the pop up targets later? Do I lose points letting Bug take them out? I just can't ever seem to get the Mavericks to hit my targets. Auto hand off barely works. It locks on and says hand off in progress then I see the blinking cross hairs on the WPN page so I fire, mav looks like it's heading in towards the target but then misses. They seem to mistakenly lock on to near by buildings or other objects. Boresighting them is tough because I can't see anything properly on the WPN page. Im flying in VR and even with my quad views focus resolution set to 2.0 it's hard to make out anything on the weapons page. I tend to set the tgp on a target then use the HUD to slew the Mavericks on or near the tgp box, then try to view what I'm locking up on the WPN page, seems to work and I get blinking cross hairs but I fire and of course I miss again. I feel like I'm missing something here but I love the campaign so I'll keep trying as I'm learning a lot.

I’m about to fly the mission once more in a few minutes but I’m going to say it was between 8-10 miles. I’m able to lock up the SA-8 on the targeting pod well before that distance. But it’s super hard to see on the WPN screen when trying to boresight (specifically in VR). I will probably use the GBU-38’s instead on the first target and try the Mavericks on subsequent targets. I’ll save the track if I fail again which I probably will but I like the practice.

I’m currently stuck in the Weasels campaign on mission 3 trying to use Mavs. What did you to do achieve a better lock? For me the auto hand off only worked in the tutorial missions and never seems to happen if I set point track on an SA-8 with TGP and then try to hand off when Mav is in PRE and TGP is on Auto.

Yea I found the blog post and followed the instructions to replace the v68 updated desktop app files with v67 ones. Now if I want to try the PTC update I need the desktop app to update again back to v68. But it is not triggering an update so I will need to uninstall it and reinstall I suppose.

I can try it tonight but I'm skeptical. I just went through the process to roll back desktop oculus app to v67 files since it updated a while ago. I also did the os update disabling on the headset. So if I go into PTC and it doesn't work I'll be screwed lol.

Funny I just set up sidequest today, loaded filemanager+ and disabled oculus OS updater app. Thanks for the info, once the update is out at least it will be an easy revert.

One thing I don't like about link cable is how inconsistent it can be. A day ago I flew a mission in weasels over Syria, no stutters, no hourglass loading while flying randomly, it was great. Last night I hook it up to do the same thing because I failed that mission and this time I had instances of the loading hourglass 2-3 times. Usually it's oculus services so I force close all of them and usually this helps but I can't say this is 100% the solution. I'm running 1.0 resolution in oculus home app, 90hz, quad views, in oculus debug tool 2.0 super sample and 500 bit rate. It's very inconsistent when I end up with the hourglass pauses. There's days where it does not occur at all.

Not so much the speed, the point of a separate 6ghz router is to create a stable and quick connection that's isolated from other wireless traffic. What is commonly recommended by the Virtual desktop discord is TP Link Axe5400. I got mine for $150. I have a separate mesh system at home since I can't drill through walls to wire stuff as we are renting, so I have the tp link wired to a satellite in the office and then an Ethernet cable form the TP Link to my desktop. This is the important stuff, your PC must be wired into the standalone router you are using for the quest. I don't have gig speeds either just 400-500mb down/up and VD runs fine for me. VD performance overlay says my speed is 2100mbps. I'm not on v68 yet so I'll use link cable until I can't anymore.

Minimum is 1Gb for VD. Only thing is if you need higher resolution other than “god mode” in VD then you can bump up Pixel density within DCS settings.

Oddly enough I went to do this today. This is what my Oculus folder looks like and i never made changes to it. Somehow my headset was able to update to v67 from 64 today. Should I delete the bak.tmp and bak.Staging?

Definitely looking forward to it! Bought the Gambler’s and just now started learning the F16.

Thanks. Glad to be back to the same performance I had months ago. I'm sticking with link cable 500 bit rate as 960 still caused audio cutouts.

Should I be on v67 for best results? If not I will stay on v64. I shut down all oculus services in task manager if I am not flying. Leaving them running in the background I noticed causes my other full screen games to get minimized or go out of full screen. It was driving me crazy trying to figure out why that was happening and it all stopped when I shut down OVR and Oculus server, and other Oculus services running in the background when the pc boots up.

From what I understand, v68 has issues with DCS if you have openXR/toolkit installed and enabled. I don’t use it so I should uninstall it. I’m on v64 still on my quest pro. I turned off automatic updates in settings when last time it was broken for a while in DCS. I am going to try the 960 bitrate again to see if I get audio stutters. I usually run super sampling 2.0 via oculus debug tool with quad views, DLAA and DLSS Quality with the latest nvidia DLSS dll toggled via OVGME. I am still waiting for a company to make a headset of similar size to the Pro, decent FOV, decent resolution and eye tracking but with Display port. Seems like pimax missed the opportunity not including eye tracking in the Crystal light but I feel like they would be shooting themselves in the foot if they did that.

Those are the exact settings I use with oculus link except 500 bitrate because 900 gives me audio stutter and I don’t want to wear extra headphones. I figured a 13900k and 4090 would be ok to drive that bitrate but I suppose it also depends on the encoding chip you get in the headset. If quad views is working as it was before on link cable without the hourglass pauses or stutter then i will be happy with how it looks.

It said something along the lines of enable tracking data and then has two additional check boxes for for SteamVR controller tracking or another option. I enabled it, not sure how it got disabled. Now I see it working properly. I remember setting this up properly but then it broke with the last update and I used the unsigned dll fix until the recent update fixed it. It looks like I may have been running link cable without eye tracking because the Quad views log was was not picking it up. Now the log shows it being picked up in Virtual Desktop. I will need to test link cable again. Found option 'smoothen_focus_view_edges=0.2' 2024-07-26 17:13:07 -0400: Found option 'sharpen_focus_view=1' 2024-07-26 17:13:07 -0400: Found option 'turbo_mode=1' 2024-07-26 17:13:07 -0400: Found option 'horizontal_fixed_section=0.5' 2024-07-26 17:13:07 -0400: Found option 'vertical_fixed_section=0.45' 2024-07-26 17:13:07 -0400: Eye tracking is supported 2024-07-26 17:13:07 -0400: Recommended peripheral resolution: 1536x1608 (0.500x density) 2024-07-26 17:13:07 -0400: Recommended focus resolution: 1076x1126 (1.000x density) 2024-07-26 17:13:07 -0400: Stereo pixel count was: 19759104 (3072x3216) 2024-07-26 17:13:07 -0400: Quad views pixel count is: 7362928 2024-07-26 17:13:07 -0400: Savings: -62.7% 2024-07-26 17:13:15 -0400: Session is using quad views 2024-07-26 17:13:15 -0400: Edge smoothing: 0.20 2024-07-26 17:13:15 -0400: Sharpening: 1.00 2024-07-26 17:13:15 -0400: Turbo: Enabled When using Virtual desktop is it advised to increase PD in DCS or should I be doing that in the Quad views config?

I think this is the right forum topic for this inquiry. As of the latest DCS update I noticed a lot more hourglass loading and stutter using Oculus link cable. So i decided to try Virtual desktop with VDXR and HVEC-10 bit codec. I also tried other codecs. Using God Mode quality. Hvec-10 bit max bit rate is 150 and for H264+ it is 400. I am using a TP Link AXE5400 WiFi 6e router set up as an AP and the Quest Pro is the only device on it. Virtual Desktop loads up quickly and DCS also is very performant. I get a speed of 2100Mbps in the performance overlay. There is something weird going on I feel is related to eye tracking..basically it feels like I am wearing my HP G2 again. Everything outside of where my head is focused straight ahead appears as if there is Vaseline smeared all around the viewbox. I have to move my head and look at what I want for it to become very clear. Is there a virtual desktop config for Eye tracking? I don’t have this problem at all with link cable and Quad views eye tracking. I used the default Quad views config and you can barely tell stuff is blurry outside of your viewpoint and it is not noticeable at all because as soon as your eyes move, what you are looking at becomes clear. Whereas with Virtual Desktop it feels like there is some sort of foveated rendering happening but it’s like the “box” is too large so everything outside of your immediate straight ahead gaze gets blurred out? Don’t know if I am describing it correctly but again I don’t have the issue with Link cable so not sure what is going on and if maybe someone else has noticed this?

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.