Recluse

I don't think the issue is boxing DESG. The issue is that if the TARGET that is designated is outside the field of view of the DMT, it will show INS rather than TV. As you bring the nose around within the FOV limits of the TV sensor, you will get the TV image of the designated target. At least this is my experience. I think you are confusing the LST symbology with the INS symbology.

Well, I guess I answered my own question. I set the Encode Resolution to 0 in the Tray tool and didn't see any difference. Of course, I also tried bumping up the Oculus Resolution with this setting at 0 and didn't really see any difference there either .

So, in the video below (not DCS related) the guy says that the Encode Resolution setting in Debug/Tray tool is no longer needed as it is handled by the Resolution Slider in the Oculus App. Is this true? If so, which one takes precedence? Have I been locking myself out of the higher res on the Slider by setting a value in the other tools? Most of the DCS specific videos (Tactical Pascale etc..) still recommend a value for this setting.

So I tried it, and it worked perfectly for me. When you said: I have 6 JDAMs loaded from a previously sucessful JDAM mission. Did you mean you took off, fired off some JDAMS, then landed and reset targets, or refueled and took off again? I seem to recall some bug reports about issues when landing, re-arming and taking off again. In my case: - ARM with JDAM (I used 4 rather than 6) -F10 Map - Put down 4 Target Points - SHF-CTL-8 (or whatever it is) to bring in the Targets. - VIEW on CAS RCALL page - Select JDAM and tick off Targets 1-4 on the ODU - Set FUSE to -IN (Keep QTY at 1. - Take OFF - AG Mode -Box DESG on EHSD - All Symbology appears in HUD and EHSD - Proceed to target. - HOLD DOWN PICKLE when about 60% -ALL 4 JDAMs drop and HIT.

Yep. Works well. I do the same with FLIR in the other DDI. The trick for me was Gripes' suggestion to designate the ship and then Point Track (AUTO TRACK in ATFLIR). I was hung up on leading the target for a point track like a vehicle, but for the big ship it wasn't necessary. Got the POINT TRACK and the LASER spot right in the middle of the deck. Still think it is a BUG that the Radar drops track when you put the TDC in the FLIR, but it makes this handoff process much easier.

Some updates were made. - EHSD: DESG must be boxed for any AUTO drop, including JDAM. - PICKLE needs to be held for ~1-1.5 second before JDAM is released. Here is a more recent video..

Some of this behavior (FLIR assuming designation priority). IN previous builds the Radar retained track unless heroic measures were taken to get the FLIR in priority. In my last several attempts, similar to the TRK I posted, the FLIR did maintain the PTRK when the radar went out of GIMBAL. The FLIR losing PTRK (for me) seems to have been due to something else.

Both of you are right. Once you have the link you don't NEED Virtual Desktop. In my experience, however, this is the BEST method for assuring DCS will open properly in the Headset. When I have simply LAUNCHED from the PC while LINK was active, even though on screen it seemed to be opening in VR, it was not appearing in the headset, or it would initially show the launch screen and then CLOSE. The Virtual Desktop method was just the one I had consistent success with, so I do it that way.

Yeah, in the track, I was oblique, very near broadside. I tried again approaching longitudinally and yes, the cross was on the ship that time. I didn't try an initial designation followed by PTRK. Good idea to establish the designation first. I have been used to the "lead the target" to achieve PTRK which makes sense for smaller vehicles, but not necessary for a big honking ship!! I was also disappointed at how little damage 4xGBU12 or 2x GBU-16 did to that ship (when they hit). 4xGBU-12 amidships did 7% damage. I also rearmed and fired 2 Harpoons and two Mavericks, all of which were shot down by Gunfire Also it seemed that as soon as I put the TDC on the FLIR, the radar dropped the lock, (CROSS but no FTT) and I got a stabilized diamond in the FLIR that the ship was moving out from under until I slewed to capture the PTRK. I don't remember that happening in previous patches.

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!