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.