Recluse

Take a look at your AXIS commands as well as the button bindings Edit: You beat me to it!

Check your Radar Elevation Caret. I noticed in the TRK that after your initial selection, when you returned to the RADAR, the caret was WAY down the screen so it wasn't seeing the surface any longer. Maybe you have radar elevation mapped to something that got moved around. Happens to me often as it also controls the FLIR zoom.

No problem., This stuff changes so often it is hard to keep track!

Make sure you are in TV mode (DMT) or TPOD mode (for Litening). Slew is much slower in INS mode and faster when in a dedicated sensor mode. That said, I have always had issues slewing with the COUGAR ministick. For awhile I had it working OK with saturation and curves, but now, DCS will ONLY recognize ONE axis on my mini stick and not both, but it is working OK with the one axis, and I had to program the OTHER axis elsewhere PAIN in the AFT...

Not true. Pickling with MAV-E selected will auto fire the laser. - One press of Pickle fires laser -PRESS and HOLD fires laser and fires missile when it picks up the spot. The issue where the TDC could not be assigned to the MAV-E page and have the missile acquire the laser got fixed some time ago.

The way I remember it working In the past, a Simple Undesginate allowed slewing of the MAV seeker (while holding TDC DOWN) It remained Ground Stabilized in that position after the Undesignate which made it easy to slew to a new target. After the second time, though the seeker caged to boresight. To be honest I have always been confused by the PTRK behavior of the TPOD. When engaging moving targets, it seemed that after PTRK, another TDC depress was needed (Offset cross appears) to really keep the laser on a target (when using Echo Mavs or GBU, that is). It always seemed to me that the PTRK should serve as the target designation without the extra TDC depress, but I always did it. I haven't tried using the Maverick Slew recently...good to know this new step is needed.

What helped me is learning to do a STABLE approach with On Speed AOA. There are numerous videos. Here are 2 plus Matt Wagner's original VFR landing Video Practice lining up from a fair distance and trimming to On Speed to land with the Velocity Vector (Flight Path Marker) where you want it, On Speed controlling your descent with throttle only. Then you can progress to circuits. A good rule of thumb is to try and maintain 3 degree glideslope, so about 300 feet altitude for every mile from the runway. Start at 10 miles and 3000 feet, trimmed to on speed and take her down. Then progress to shorter approaches keeping this in mind, then circuits. Honestly, it is pretty easy to make your own mission. Open the Mission Editor, place an aircraft where you want it on approach to a runway so you start more or less lined up and practice on speed approaches. I think there are some Instant Action missions that get you more or less in the right place as well. The Missions are located: X:\Eagle Dynamics\DCS World - Open Beta\Mods\aircraft\FA-18C\Missions where X is the drive your DCS is on and the DCS folder (DCS World or Open Beta or whatever you named it) If you edit the mission, be sure to save it under a different name, and preferably in your X:\Users\<username>\SavedGames\<DCS>\missions folder, usually on C drive, but you may have it somewhere else.

It seems like I have seen this oddity if I plotted a CRS line through a TARGET and then selected a TACAN without UNDESIGNATING I would either NOT be able to create a TCN CRS line OR I would end up with TWO of them (TGT and TCN). Didn't really pay attention at the time, just UNDESIGNATED since I was finished with the TGT point anyway. But it is odd.

Also, FYI since you are new to the Hornet, in order to toggle between Area and Point Track on Litening or Scene and Auto on the ATFLIR you have to move Sensor Control Switch in the direction of the FLIR DDI ONCE for Area/Scene and again for POINT/AUTO. The ATFLIR can be slewed in SCENE mode, but the LITENING cannot be slewed in AREA track

Do you have a LItening Pod or an ATFLIR? That symbology is for the LItening. The ATFLIR will say "SCENE" or "AUTO" in the bottom of the DDI for the equivalent ATRK/PTRK

Previously, right or wrong, you could populate each station. Pressing UNDESIGNATE would remove the current designation, but leave the stations already populated in the JDAM. This seemed to make sense, when a station with 2 GBU's had a TOO1 and TOO2. If DESIGNATING populates the JDAM coordinates and UNDESIGNATE removes the designation completely from all JDAM, then what possible use is it to have a TOO1 and TOO2??? The Workaround is to use MarkPoints to recall the coordinates for each bomb, but If it is ONE bomb at a time based on Designated target then the TOO1 and TOO2 options are useless. Maybe they don't exist in real life and it it has been wrong all along? I think we are all just looking for Clarity on whether the change was INTENDED or not.

This is current behavior. Probably a bug.

Holy smokes!! I never knew this. THANK YOU!!!! I cannot count the number of times I set up a station and forgot to hit STEP and enter the code, and, of course first drop is off the station without the code. I just tried it, and it worked for all GBU stations, but I also had some Laser Mavericks, and still had to set them separately, but still, this is a HUGE improvement to the armament setup!!

Well, there is currently a bug where the FLIR won't slave to the Waypoint if the TDC is assigned to the FLIR. Workaround is to move TDC to another DDI, Designate and then return TDC to the FLIR page. MAYBE this is happening here, but it doesn't seem like the FLIR should STILL be pointing at the old target if it was undesignated.. BUT give it a shot.

IMHO there are 2 show stopper bugs: At least there is a workaround for the second one, but the first really breaks GPS guided TOO use.

Do you mean the Paid Virtual Desktop App or the built in Oculus Virtual Desktop option that pops up when LINK is established? I never knew there were settings for the latter. Here's a funny anecdote regarding the Cable: In another thread there is a discussion of whether turning on the Pilot Body helps or hinders immersion. For fun, I turned it on. In the AV8B the Pilot Body includes an oxygen hose hanging on the chest area. It was almost exactly where my LINK cable was lying and I honestly felt like I was feeling the oxygen hose from the Pilot Body!!

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.