Recluse

So here is a track showing what I meant about the Centroid being off. Point Track on the big ship. Designate, and the cross is JUST off the ship. Kept the PTRK throughout the GBU flight. Impacts exactly at the designation, and misses. I did this in VR so not sure how the track will play back. Flir centroid off.trk

Yes, always. Forgot to add that I also did a TDC Depress after the PTRK to be sure the laser was on the target. HONESTLY I didn't think this SHOULD be necessary as the FLIR is already following the moving target, but when I don't the bombs always fall near the point of the original track and miss by a lot.

I just saw this, or something similar! -SEA==>FTT track Right DDI (vector pointer on contact showing speed and direction) -FLIR in LEFT DDI - Slew FLIR ahead of the ship and manipulate SCS until PTRK, Designate. Radar track turns to a + over the target. Strangely, it continues to FOLLOW the brick. - DROP GBU.. - PTRK gets lost. I honestly didn't notice if the RADAR track dropped at the same time as the HUD label showed Designation by FLIR, and in the Radar DDI there was a + over the target NOT the SEA Track with the direction Vector so it SEEMED to be following FLIR instead of SEA tracking at that point. Of course, trying to UNDESIGNATE lost the target for the FLIR as well. The BUG that I was going to report was that when I had the PTRK in the FLIR (LITENING) the CENTROID was NOT on the ship but a little off to the FRONT or REAR depending on the direction. When I did manage to drop GBU with the PTRK intact, they splashed into water JUST where the PTRK was looking. I went to record a TRK to report, but subsequent times, the PTRK kept DROPPING before impact. This turned out to be a blessing in disguise as I could MANUALLY hold the LASER on the spot I actually wanted to hit until Impact!!

As stated above, DO make sure that the VR option (run in Headset) is enabled in the DCS Options->VR. Beyond that: I have had the best success with QUEST 2 (AIR LINK or CABLE) by using the following: - Activate the Link -Enable Virtual Desktop -Browse to my DCS/bin folder, and open the executable (I always use the DCS_Updater.exe) by double mouse clicking. -After a bit I see the starting screen in the Headset and it's off to the races. I have had MIXED results just opening up from the Desktop while LINK is connected and having it show up., or opening from within the Headset from the RECENT tab. It works SOMETIMES but the method above is pretty much guaranteed.

And once you select an AA WPT to correspond with Bullseye, your AA Radar and SA page will show the Bearing and Range from Bullseye of your own ship, the target if any, and the position of the TDC cursor which helps tremendously with interpreting or making Bullseye calls: Here's a video:

That is strange!! I get the part about being unarmed, but spawning unarmed and then loading ordnance SHOULD work. This might be a real bug I noticed that in the Hornet, sometimes the AFAC will call for CANNON even when I am loaded with Guided Ordnance if I have the MB Weapon preference setting to AUTO in the mission editor, which is why I usually set to GUIDED, but then it might glitch if only carrying dumb bombs. Of course, when that happens, I just ignore him...

Thanks anyway, I own the A-10C and A-10CII but don't have them installed currently. No Syria Map. Got more than enough to keep me busy! Good luck with your Mission editing!

No worries. When I posted the screenshot, I realized the difference in the two ENROUTE actions. I wasn't sure the FAC action worked without a specific GROUP. Guess I need to look at how some of the RANDOMIZED missions are setup. Thought maybe they required MIST or other Scripting tools outside the built in Editor functions.

Here's an older mission that I made using MQ-9 instead of Predator. Worked fine just now with .7029 with AV8B. LOL, just got the .7139 update... I see I used FAC-ENGAGE GROUP not just FAC. This might make a difference. When I first set out to program FAC's I believe this was the option I saw in whatever tutorial I looked at. Persian Gulf Tunb Island Weapons Practice_AV8B_AFA_Guided.miz

I hadn't noticed, but maybe you accidentally used some SNAP VIEW? You CAN adjust the seat position, actually, you are just adjusting the CAMERA using RSHIFT RCONTROL KP / and *

Similarly, I still have AGM-65G from loadouts created in Missions before it changed to the -F model. Doesn't work any differently, but it shows up as -G

Chuck's Guide has one and if you search in the Downloads section there are numerous Kneeboard collections that include cold start checklist. Like this one: https://www.digitalcombatsimulator.com/en/files/3300740/ https://www.digitalcombatsimulator.com/upload/iblock/3a9/f18 checklists UPDATED.zip

I've not been able to achieve an AIR LINK connection above the Default 0 setting (assumed to be 150?). With the cable I can bump it up to 500. BUT i honestly haven't noticed MUCH difference.

Agreed! I haven't unlocked the 120 Hz yet, but I did try up to 90 Hz. At first I could NOT make an air link connection above 72 Hz but I could go higher with the Cable. Now I can get it working at 90 Hz and the suggested resolution. FPS is a bit higher and it is smooth, but I am torn between this and going back to 72-80 Hz and cranking the resolution down a notch. The clarity is NOT much different and the 36 FPS vs 45 max between 72 and 90 Hz doesn't make much of a difference. Going to try and split the difference and go to 90 Hz and pull resolution back down to the second notch on the 1.0 setting to see how that goes. Honestly the lower resolution actually gave a bit better clarity. I turned Pixel Density to 1.4 or 1.5 in DCS and it seemed like those settings with 1.0 resolution and 72 Hz gave the best overall experience.

You know you have played in VR too long when you go outside and think: Nice Graphics, but there is too much BLOOM on the Sun....

WOW!! Indeed. I find the map pretty useless in VR and only good in 2D with the TRACKIR Z axis zoom in. VR ZOOM is OK but hard to keep VR ZOOM on AND do any manipulation. Be nice if we at least had the WHITE labels that show up well vs. the Green that is hard to see!

I just did some testing with Link Cable at 90 Hz, Oculus Res at 4224x2128, Encode bitrate at 500, Encode Res Width 3924 DCS Pixel Density 1.4 Medium Textures, Low Ground Texture, Water HIGH 2x MSAA 16X Anisotropic Pretty good maxing out at half of the 90 Hz value (45 FPS) and sustained between 38-40. Pretty good and smooth. Tried Maxing out textures and raising RESOLUTION, and it was still playable but a little lower FPS and a little more Shimmer. It was better than AirLink but not SO much better that I won't go Wireless for convenience MOST of the time. My AIRLINK settings are pretty much the same except 72 Hz and Encode bitrate set to 0 (default) My specs are similar to OP: RTX 3070 i7 10700K 32 GB Ram

i honestly didn't see much difference between AIR LINK and the Cable, but I need to connect the Cable again and see if I can upgrade some settings that I couldn't with AIRLINK now that I have more experience with how thinks look in AIRLINK. When I used the CABLE, I cranked the ENCODE BITRATE up to 500 but I don't know if that really improved anything. I have never been able to connect AIR LINK AT ALL at higher than 72 Hz, and my recollection was that while I could get a connection at 80 Hz with the Cable, it led to more artifacts. DCS is pretty demanding and I haven't seen FPS greater than 36-40 (mostly 36 and below) in the PIT. Seems a lot smoother though so I don't know if the built in DCS Frame Counter is really applicable to VR DIRECTLY. The setting that seemed to help a lot was cranking up the RESOLUTION in the OCULUS APP to the first 1.1 setting (I forget the resolution but I think I put it in one of the other threads here). Playing with Pixel Density in DCS and Oculus Debug tools also helped with blurriness. DEFINITELY not as sharp as a regular monitor, but cockpit labels, switches and DDI's are completely readable, especially if you lean forward a little. ZOOM is not HUGE like TIR, but it is enough to see the DDI's better. You can also map a VR ZOOM button but I don't find it too useful unless I want to momentarily zoom in on the FLIR or the ground through the HUD.

So, I tried it the EASY way, just enabling LINK and launching DCS from my computer (NOT going to DESKTOP) then putting the headset back on. Worked fine! I still only got the SINGLE image on the monitor and got the same 36 FPS indicated, so I guess either way works. STILL not sure why you got the double image, but as long as works in the headset you should be good

If you got it running with LINK, then you already got the "built in" virtual desktop running, probably unless I have been missing something all along! So what I do is when the LINK is established, I click on the DESKTOP icon so I can see my "monitor" and then I start DCS from there. It automatically goes into the Headset leaving the window on the desktop. I never tried JUST starting DCS while LINK is active. Maybe I should. I'm also getting a pretty solid 36 FPS with AIR-LINK but sometimes it drops. Since the LINK is 72 Hz, I believe the 36 FPS is 50% of that setting. I have tried the LOCK 45 Hz With and Without ASW in the Tray Tool, but it doesn't seem to do anything. Probably need the 90 Hz link to work. I haven't gotten much success with anything above 72 Hz even WITH the Link Cable. Agreed that GRAPHICALLY the Monitor looks much better, but I think the 3D Immersion makes up for it. A little worse for me in the Harrier vs. the Hornet where the displays are not as clear with the same settings. Haven't tried the A-10C or any of the FC3 aircraft yet as I almost NEVER fly them.

Monitor should be a Single albeit curved image. Here is a thread with some Quest 2 experiences and tweaks..

Are you sure the AGM-65F has timed out? You will not be able to UNCAGE it until it finishes it's Cool Down (warm up?) and the timer has counted down.

As a slight aside, one of the more INTERESTING things I discovered starting out in DCS VR was the implicit assumptions my brain made using TrackIR. It was, no doubt, revolutionary for 2D Simming, but I was initially shocked in VR when moving my head JUST let me look in another direction without the screen panning as it does in TrackIR. Something taken pretty much as REALITY while simming with TRACKIR and all of a sudden shown to be an incorrect paradigm! Don't get me wrong, it still feels JUST fine in 2D, and has the advantage of allowing small movements to result in large view changes vs. having to contort yourself to look (e.g) at the wings let alone your six! In another thread, there was a link to a mod that allowed you to increase the head tracking in VR to more TRACKIR like levels, but I haven't tried it out.

Glad to hear you got the EXPERIENCE. Yes I have landed on the Carrier as well. I feel like I have a bit more situational awareness for lineup and landing on both Carrier and Runway. I find that I never got the sense of how high off the ground you are in the cockpit, which is why takeoff and taxi are so impressive (to me) in VR. I found Carrier TAKEOFF to be more exciting than landings. Get a much better sense of the Cat Shot. I made this suggestion in another thread. Take advantage of your Zero Zero ejection seat and EJECT while sitting on the runway. Then, you can use the arrow keys to WALK AROUND the plane. Gives a really nice impression of the SIZE of things and you get up close and personal to the ordnance on the wings. Good to know the paid for Virtual Desktop has good performance. Might be worth it. In the Headset, there is an EXPERIMENTAL option to turn on 120 Hz. I have it on just in case, but, as I said, wasn't able to crank up the Oculus PC app beyond 72 for Air LInk. Have to crank it up again when I use the CABLE to see what happens. Previously it worked intermittently. Your Display Port connection to Monitor shouldn't affect anything. All of the settings I mentioned regarding Hz are in the Oculus Link (headset and PC App settings) Another thing that screwed me up for awhile..when switching to Cable Link vs. Air Link, you have to turn Air Link OFF in both Headset and PC APP or it will either not connect or it will continually connect/disconnect. It is too bad Oculus uses USB rather than a direct Display Port connection to the Headset for the Cable, but I guess it has more Mass Appeal that way for folks who might not have that option on their cards.

Hmmm... not sure what to say. I don't have any Onboard Graphics enabled. When I enable the link and go to the (built in) Virtual Desktop, I see everything on my PC (except in big screen) I drop the controllers and grab the mouse at this point, though the controllers do work for navigating. Here is a thread which suggests DISABLING the ONBOARD graphics: https://forums.oculusvr.com/t5/Support/FIXED-Quest-2-PC-Link-Black-Screen-But-Audio-and-Desktop-Mirror/td-p/838935 Here is an associated video. Not sure if it is your particular issue..