Recluse

Here is what worked for me. Apologies if I am treading on ground you already covered: 1) Connect Oculus Quest to a 5 GHz WiFi network and make sure you have good signal 2)On the Oculus App on the PC, make sure to go to settings and under BETA, enable AIR-LINK. Must be enabled on this end for AIR LINK. For regular link cable you just have to make sure you are connected. 3) In Headset Settings, go to Experimental and make sure Air-Link is Enabled there. It should find your PC and let you PAIR, then Launch. For Link Cable, just enable Oculus LINK. 4) You should then get the expanded Ribbon where you can choose Virtual Desktop (built in one) and launch DCS from there. I haven't used the PAID Virtual Desktop app, so I don't know about that one. If you don't use the STEAM version of DCS you don't need STEAM VR. I found that AIR-LINK would NOT work for me if I selected anything other than 72 Hz. Similarly, if I tried to up the Encode Bitrate it similarly would not work. I had to leave at 0 (DEFAULT) in the ODT. I kicked it up to 500 for Cable Connection. Not sure there was much difference. I managed to get CABLE LINK working at 80 HZ but it was really unstable and DCS did not run well. I did raise the Encode Resolution width to 3946 in the Tray Tool, and it then appeared in the Debug Tool so Tray Tool was no longer needed. You don't need OCULUS TRAY TOOL, but you can use it. Just the DEBUG Tool is OK, though the TRAY TOOL gives you some more options. I have my Headset set to 1.1 (first setting) 4480x2256. I cranked it up one more notch and it was fine in Air LInk/Cable LINK, but then it wasn't and I was getting crappy frames and artifacts. Probably because other settings changed. I left Pixel Density at 0 in the Debug Tool and cranked it up to 1.4 in DCS. I tried so many combos of settings in OTT, ODT and DCS I lost track of what actually worked, so now I just leave it here. I believe by setting it a little higher in the Tray tool, I got A LITTLE better clarity in the pit. - I still have a bit WOW!!! Factor when I fly, but now that I have gotten more comfortable I do notice the shimmer and less than perfect readability of DDI's. and sharpness of certain objecs. Leaning forward a little helps as does the VR ZOOM, but in this regard, TRACKIR was superior. I tried building a TRACKIR profile that ONLY had a Z axis for Zoom but it seemed to get really confusing with the VR Headset on and TrackIR at the same time with the competing head tracking. That and having to do without the Keyboard make it less than PERFECT but I can't lie.. I get a thrill every time I sit in the cockpit and roll down the runway. My Specs: Core i7-10700K RTX 3070 32 GB RAM Just updated to latest NVIDIA Driver.

I have the standalone version of DCS so not sure how SteamVR interacts with Oculus, but it seems that the Oculus software is directly affecting any LINK that is made, while STEAMVR might affect other settings concurrently? I also "fly" Elite Dangerous via STEAM (which is absolutely STUNNING in VR and that uses SteamVR. I haven't messed with any of the STEAM VR settings because Elite has to launch in a wonky way through the LINK virtual desktop from STEAM and autoloads STEAMVR in the background. For some reason it won't launch properly FROM the STEAMVR platform. EDIT: Adding on here rather than making a new post: I noticed that with exactly the same settings, I get higher framerates in the F/A-18C than I do in the AV8BNA Harrier. Consistent 36 in the Hornet, and 30 or lower in the Harrier. Transient issue or has anyone else noticed it? Still seems to be relatively smooth and maybe I wouldn't notice it without the framerate counter running.

Thanks! I read that, which was what initially inspired me to try messing with the settings. I tried values from 55 - 70 (my measured IPD is 62.8) and honestly didn't notice much difference, though in the Harrier, I did manage to make the cockpit look A LITTLE cozier. To me, the apparent size of the throttle/stick didn't really change all that much (OOPS that was in another thread! I will try your seat measurment test) In the F/A-18, I ejected while on the runway and then walked around the jet. Great fun if you haven't tried this. Jet did look a little bigger than I thought it should based on videos and having walked around static displays at airshows and such, but I didn't do a good set of IPD experiments under those conditions. Haven't tried it in the Harrier. The main thing that breaks my immersion is seeing the rudder pedals much farther away than my own feet are on my pedals

Got things working relatively smoothly in my Quest 2 using Air-Link! Look ma, No Cables! Had to crank down the Encode Bitrate to 0 (default). I had it up to 500 with the cable, but Air LInk Virtual Desktop was unstable at anything 200 or above. Similarly, had to leave it at 72 Hz. I left Encode Resolution width at 3946. Pixel Density in DCS at 1.2 and Resolution in QUEST APP at 1.1 Set to 45 Hz no ASW (not locked) and framerate counter in DCS showed steady 36 FPS, but it seemed like more, Was zipping my F/A-18 at Treetop altitude in the Caucasus without noticeable stutter. May have looked a little clearer with the cable and higher bitrate, but honestly it was pretty good with Air Link. MSAA 2X Anisotropic 16X I have been messing around with the Scaling (DCS IPD) and not really noticing MUCH difference. Hornet cockpit looks good. In the Harrier, I feel like I am too LOW. The top rear view mirror is above my head, but I cranked UP the seat using the camera controls so I could just see my helmet and the HUD was still where it was fully visible. Clarity of DDI's is not as good in the Harrier no matter what I do, but I gather that is common since one of the 2.6 updates.

Thanks, I also found THIS: This helps with the WINDOW OUT OF FOCUS, but is there a setting that will allow better access to the back of the Cockpit in VR as well? It seems that the misleading "FORCE IPD" setting can change cockpit size, so I wonder if fiddling with that would help? SO far I have left it unchecked and let it default to whatever it defaults to.

Question to VR Harrier Drivers out there: Just got a Quest 2 and couldn't be happier! Things are pretty well sorted out for me in the F/A-18 (though always tweaking to get it better). Harrier looks great and is a blast to fly in VR as well, but I have one issue: When doing Cold Start or Shut Down, I have a lot of trouble "reaching" the switches and controls at the back of the panels. Ejection Seat Safe, OBOGS, DECM, Fuel Cutoff lever etc.. Seems like my head tracking doesn't work that far even when I crank myself around and when I try to get the mouse back there it kicks the dreaded "WINDOW IS NOT THE FOCUS" error. I have the checkbox in DCS VR for keeping the Mouse within Window Boundaries so I don't know why it keeps kicking the focus out. Happens in the F/A-18 as well, but for that the head tracking pointer works great, and I have been using THIS METHOD: Any ideas for a setting? Mask maybe?

Brand new VR user here (Oculus Quest2). THANK YOU for this utility. I am getting stuff working little by little. I didn't realize just how much I relied on the keyboard as I kind of maxed out the buttons and switches on my Cougar HOTAS. THANK you for implementing the SHIFT function using HOTAS buttons. I had used some Modifiers in DCS but they are all Keyboard modifiers so they don't work well in VR. NOW I can operate the radios again without juggling the headset.

THANK YOU for starting a good thread. I definitely learned stuff!! BTW how is Desert Convoys going for you? The few times I tried it, I could never find the SAM convoy..but boy did they find ME! I always ended up killing a ZSU and a few TELs in the main convoy. Had 2 bricks in GMT, but neither of them seemed to have the SA-11's. Will get back to it one of these days.

If the ship is MOVING you cannot use AREA track. You have to go to POINT TRACK (LITENING POD) or "AUTO" mode (ATFLIR). Both are entered with successive Sensor Select Switch movement in the direction of the FLIR DDI to "catch" the moving vessel. In SEA mode Radar, slewing cursor over the brick and SSS in the direction of the radar DDI will give you a Radar FTT track. The FLIR will automatically track this target as long as the radar has it in GIMBAL limits. At the moment there seem to be some issues with getting the FLIR (either pod) to get into a PTRK/AUTO trk with a moving target at the distances that it used to be possible at. I just tried and managed to get a PTRK with LITENING on a moving ship, but not until about 8 nm. Conditions were perfect, and pre-2.7 it would have tracked long before. SEA RADAR tracking worked perfectly at a longer distance.

I find myself pressing TDC A LOT..just to make sure. In the HARRIER, I always feel like I am MISSING something by NOT needing to do it. I might enable TDC Action/NO Action in AV8BNA Special Options just so the muscle memory transfers between aircraft.

Not knowing how it works in REAL LIFE I couldn't say whether it is a bug or realistic. That said, I am struggling NOW to come to grips with how it SHOULD work in DCS. Apologies for the small aside, but this is my FLIR Moving Target Track Journey in a nutshell: - It used to be relatively simple to achieve a PTRK on a moving target by getting the FLIR in the general area using a Waypoint, VVSLV or other designation method and slewing the PTRK captains bars ahead of a mover. A little hit or miss but generally worked. -SEA/GMT radar was a godsend! No more searching around for the movers. GMTT/FTT track, FLIR is tracking, AGM-65F away. Some issues with AGM-65E or GBU, because of the RADAR GIMBAL limits, when RDR shows up in the HUD as DES method, so have to slew the FLIR away and PTRK as above to make the FLIR the designated sensor with FLIR in the HUD. Worked well to do a pseudo-handoff. -With your posts, as I have tested Desert Convoys, it now seems that it is fine as long as you prosecute the initial targe from GMT. the FLIR PREFERS to lock onto the same target that the Radar had locked, even though the FLIR is now the operative sensor and everything should work as in the first bullet. THIS would be a BUG, IMHO if true. - So there are two strange things going on now, the absurd difficulty in getting a moving PTRK under certain circumstances, and the difficulty in CHANGING targets from what was originally radar designated. Not sure what to make of this. -It seems to me that the ATFLIR does a better job than the Litening. In fact, I was suprised to see that in one mission, I got PTRK on a stationary vehicle and the AGM-65F I fired hit a neighboring vehicle causing the targeted vehicle to move. The ATFLIR actually KEPT TRACKING the vehicle as it moved and I was able to fire again and hit it. I don't recall the LITENING doing this, but maybe I never found myself in that particular situation. - IT seems that the OFFSET cursor ought to be good for SOMETHING here, but darned if i could ever really find a reason to use if for anything.

I managed a couple of times to PTRK a different target from the original GMT track in Desert Convoys, but admittedly it was difficult and kind of a crap shoot. I did it in Active Pause, so doing it "for real" while flying would be even more difficult. I thought at first it was the sand/dust being kicked up that was affecting things. I did also try it on another mission I had with a moving convoy, but no dust trails and it was definitely easier to grab a different vehicle.

Do you mean SEAM mode? This is for AA Sidewinders.

That is all I ever used it for, but seeing the video above, it seems to be needed to transfer target points to the Inertial system as well. Seems like hitting DESG on the EHSD does the same thing for this purpose. EDIT: DESG doesn't do the same thing, though it does create a TGT point. WPINC LONG will make the Target Point the current Steerpoint so the symbology merges.

See this BUG THREAD.. I got excited when we got a small update the other day but this one probably requires more work. I find the Litening pod still works, but others have seen the issue with that pod as well.

[Aside from TPOD issues] Problem I have with Desert Convoy now that I tried it is all the Sand and Dust being kicked up by the convoy makes it hard to ID the vehicles. Got a good shot off at what I thought was the SA-11 Command Vehicle but it was a ZSU-23.. I think I had the WRONG convoy as the briefing says the main convoy is protected by 2 ZSU, and the SAM convoy is ahead of them...

OK. The trick is to transfer the SOI from RADAR to FLIR once the RADAR has you on the movers. YES it is a PITA, but it can be done relatively smoothly with manipulation of SCS and SLEW Here's a quick TRK I just recorded...not from that mission. Did you mean DESERT CONVOYS? I couldn't find CONVOY HUNTER I will try that mission and see if I can get a TRK/Video. In this TRK, I transferred the SOI from RADAR to FLIR and switched targets in the Convoy by slewing the FLIR out, going to PTRK and capturing another vehicle. Once the FLIR is SOI, you can repeat as necessary. I took a quick look at DESERT CONVOYS, and it is true you don't have the luxury of a lot of time to mess with this. OOPS... I re-watched, and the FLIR snapped back to the initial target vehicle instead of capturing a new one. Have to mess with it some more.. GMT_FLIR_AGM65F.trk

When you designate the convoy on the GMT, and you load up the FLIR, you should see it slaved to and tracking ONE of the vehicles which you can then prosecute with AGM-65F. Gets more complicated with Laser weapons as you need to HANDOFF to the FLIR, which is where the issues come in. But you should easily be able to attack a vehicle directly from GMT lock.

Use the GMT Radar, Luke!

Yes, but ALSO the coordinates the JTAC gives you are USUALLY not a SPECIFIC TARGET but the general area where there may be multiple vehicles, so even if he gives it to you in PRECISE format (which that MOD allowed), you still can't really blindly drop a JDAM on the PP coordinates.

This is a mod that I once used to make the JTAC give you the COORDS in a format suitable for JDAM (or PRECISE waypoints) but as mentioned, it probably isn't too useful for PP attacks. This was from back when JTAC only gave GRIDS, so it probably isn't needed now, if it even still works..

JTAC coordinates are RARELY directly on the target, so it would be best NOT to try PP mode, so YES it is preferable to find the target and use TOO mode. You can create a Waypoint from the JTAC coords to get you close, then slave the TPOD to it to search for the specific target. One of many tutorials on entering WPS. Of course, we can also enter GRID coordinates now.

OK. I just tried and all was fine. I didn't need the WP INC as I used a WP Desg as the initial target point, then slewed the pod so the EHSD already had it. Keeping the TPOD/LASER on the target throughout, or at least in the terminal phase is key.

OOPS Posted while you were posting. Save a TRK file and we can see what is going wrong possibly. Just released: I haven't tried yet. The need for WP INC LONG to feed coordinates to the INS before pressing DESG is new. Wasn't necessary before

YES that one. It is too far down. It should be co-located with the Bar on the Left side more or less, or else the radar is pointing almost straight down (or as far as GIMBAL limits allow). Look at the position of the caret in the screenshot where Contacts are showing up.