AstonMartinDBS

You can have six PP targets (labelled from OSB 6 to 11)

Exactly. No - as long as you load 2 JDAMs per pylon. If you need to deliver the bombs as quick as possible load one JDAM each on four stations. That's correct as well. AFAIK the current behaviour is implemented correctly, but our experts here could give a precise answer.

I've tried to reproduce your issue, but it worked without problems. Track attached. FA-18C JDAM PP prg pre takeoff.trk

Please upload a short trackfile that we can verify what's goin' on. Are the entered coordinates/elevations totally resetted (blank) or do all stations have other/wrong coordinates than programmed?

Please provide a trackfile of your flight, so we can see all relevant details. I guess, the enemy MiG-29s are not within the radar elevation (either too low or too high). That means, that your radar doesn't detect them. Try to increase/decrease the elevation to match elevation to enemie's altitude or increase the scan range to 4B or 6B (via OSB 06).

That is exactly what I suspected.

Thanks for that hint. It wasn't easy for me to find that switch, but finally I've got it... IFEI with standard illumination: Location of the switch at the right hand console: IFEI after setting the switch into the NITE position:

Thx @Tholozor!

I've tried to assign the coordinates from an airfield (Gudauta) to a mark point (MK1) via HSI/DATA page, but that didn't work. Is it intended that mark point data isn't editable as it does with waypoints? FA-18C MarkPointsNotEditable.trk

When can we expect the next patch for the hornet? In particular I'm looking forward to get the JHMCS designation working again ("New elevation tracking model to resolve JHMCS designation drift.") According to Wags' Hornet Mini-Updates announcements the next, big OB should contain a lot of new features and some bug fixing. Hopefully we don't have to wait for the release of 2.7, which is announced for late march 2021 or maybe even later when delayed.

I observed the same behaviour with many switches. I've turned the sync option off again and set the default switches manually prior every mission.

You have to press OSB 06 [MAVF] once again on your SMS page (according to your Screenshot on your left DDI) to activate the MAVF seeker.

Bug is still present in OB 2.5.6.61527

So ED should use frost resistant color for the runway markings!

I've reported that bug in June 2020 but it's still here randomly.

Loadout: 4 x AGM-65F, 2 x AIM-120C, 2 x AIM-9M (without TGP) DCS: current OB 2.5.6.60966 Situation: roughly designating target area @WP1 via WPDSG; SCS to the MAV-DDI; hit undesignate button; slew seeker while TDC depressed; Behaviour: switching FOV works well until the MAV gets a lock; after lock the FOV cannot be changed sometimes - neither via "RAIF/FLIR FOV Select button" nor directly via OSB 15 on the MAV-DDI Is this behaviour a bug or intended? FA-18C MAV-F FOV issue 03.trk FA-18C MAV-F FOV issue 02.trk

Try this:

Did you set the Laser switch to ARM position? Exactly follow the steps in Wags tutorial. If you still have problems, upload a trackfile. I've tested it already but had no problems so far deploying the GBU-12.

Already tested with MAV E, couldn't reproduce your issue.

It's sad that ED didn't even notice this bug report - not to mention that it was investigated or reported to the development team after four days. I cannot believe, that this embarking issue occurs again and again at regular intervals and we have to wait several months to get it fixed every time.

This thread is the report. Only an official respond from ED is missing at the moment.

File can be found in : {DCS}\Mods\tech\Supercarrier\PLATCameraUI\FLOLS.lua Change the value in line 41 from FLOLS:setVisible(val) to FLOLS:setVisible(false) function show(val) FLOLS:setVisible(val) end I guess you have to repeat this after each update. Don't know if integrity check fails if you change this option.

Follow the procedure in Wags tutorial, it's quite simple:

Sure, just use the AOA brightness knob which you can find below the knob for HUD brightness: Not yet, but an option to deactivate this overlay is already planned or in developement by DCS. Watch this thread:

I've tested the "Single player - Dangerous Rescue in Bad Weather" mission: First run: Only 1 of 6 soldiers embarked into the Huey after the first attempt. After that I tried to disembark this single soldier from the Huey, what resulted in a complete embarking of the whole group of 6 soldiers. Second run: Then I replayed the mission (without exiting DCS) and the embarking procedure worked on the first try... very strange.