Mission 12 - Point Blank / Some inconsistencies

[IceyJones]

Im at Mission 12 now. 

Several minor issues.

- Tool Tip Popup stating, I shall be tuned into 275.000 instead pre-programmed 275.500. Radio worked with the .500 so the text is wrong

- I orbited 3 times already before the "I'm in orbit" triggered. I entered orbit at 9 miles from WP6. so a normal distance. the trigger recognized me only when I was near 5 miles iirc. then the mission proceeded. 

- diamond flies back to main objective after the wingmal attacked the transport. detaching her FAR behind me. she also seems to not joining up again at all

 

PD: please move to "Bugs and Problems" @Nix Mills

Edited March 27 by IceyJones

[Nix Mills]

Thank you so much for that, IceyJones.

I have corrected the orbit reminder popup to say that you should be on 275.500 on COMM1. I have increased the trigger zone over Deir ez Zuir to a radius a little over 9 nm (it was 7 nm) and I removed a single insurgent in the town that could cause the AI wingman to return to attack that instead. We'll do our best to get this included next time they run a patch update.

I'm impressed that you're up to M12 already.

[IceyJones]

Hey Nix! 

great work! those changes should help this mission a lot! specially the trigger zone size. as the ingress point for the bomb run is at 8.8 miles, one tends to orbit at that distance.

despite some hickups like that, great campaign so far! i enjoy it a lot.

 

 

[Razor18]

Hay Gents,

I dropped the two JDAMS by the book (PP coordinates, terminal settings, altitude, ATTK HDG  double checked), even "Bank building destroyed" message, still mission failure,.

BTW, my "I'm in orbit" trigger (WM stating situation) only kicked in after I overflew the target. As long as I orbiteg 5-6 NM out, nothing happened.

[5e EVC Chappy]

4 hours ago, Razor18 said:

Hay Gents,

I dropped the two JDAMS by the book (PP coordinates, terminal settings, altitude, ATTK HDG  double checked), even "Bank building destroyed" message, still mission failure,.

BTW, my "I'm in orbit" trigger (WM stating situation) only kicked in after I overflew the target. As long as I orbiteg 5-6 NM out, nothing happened.

I had the same issues. I flew it twice, both mission unsuccessful, target not destroyed. Even though I double checked JDAMs parameters. I think there is still a bug with JDAMs with the F/A-18C, am I correct?

Also took couple orbits before the "I'm in orbit" triggered, I was within the 7 nm the whole time.

Edited May 18 by 5e EVC Chappy

[Nix Mills]

14 hours ago, 5e EVC Chappy said:

I had the same issues. I flew it twice, both mission unsuccessful, target not destroyed. Even though I double checked JDAMs parameters. I think there is still a bug with JDAMs with the F/A-18C, am I correct?

Also took couple orbits before the "I'm in orbit" triggered, I was within the 7 nm the whole time.

19 hours ago, Razor18 said:

Hay Gents,

I dropped the two JDAMS by the book (PP coordinates, terminal settings, altitude, ATTK HDG  double checked), even "Bank building destroyed" message, still mission failure,.

BTW, my "I'm in orbit" trigger (WM stating situation) only kicked in after I overflew the target. As long as I orbiteg 5-6 NM out, nothing happened.

I have "relaxed" the criteria for both a bit and added a failsafe to help detect impact on bunker, in case the others didn't work (it happens for some reason). Should be out with one of the next updates. 

Note that Player is reporting that they're on station when they start orbiting the target, not the moment they get visual on the target. The first task is to confirm civilian activity visually. 

Edited May 19 by Nix Mills

[Razor18]

What are the proper orbit procedure to start orbit, so that the game can see I'm starting my orbit? Altitude, position, bank angle, or?...

[Nix Mills]

1 hour ago, Razor18 said:

What are the proper orbit procedure to start orbit, so that the game can see I'm starting my orbit? Altitude, position, bank angle, or?...

Check in with Devil, then establish orbit over Deiz-ez-Zur at 20,000 ft (stay within 9 nm of target). Make sure you're monitoring Devil on PRI and wingman on AUX. You'll get a reminder after a while you haven't passed this step.

[Razor18]

Thanks!

Just a non campaign-specific question comes to my mind: why is the altitude recognition somwhow off? Tanker says he is orbiting Angels 25, but in fact he flies at around 24 500. Or if I fly at 28200, my check in message to Magic says I'm at Angels 29. Probably core DCS related, just asking, if it is a known bug?

Edited May 19 by Razor18

[5e EVC Chappy]

2 hours ago, Razor18 said:

Thanks!

Just a non campaign-specific question comes to my mind: why is the altitude recognition somwhow off? Tanker says he is orbiting Angels 25, but in fact he flies at around 24 500. Or if I fly at 28200, my check in message to Magic says I'm at Angels 29. Probably core DCS related, just asking, if it is a known bug?

Did you set altimeter to 2992 above Angels 18 ?

[Razor18]

Yup, when I heard Angels 29, but it only changed a couple of ten feets, I was about 28140ish

[Kurnass1977]

On mission 4 ( I'm actually playing) when feet dry I had to set the altimeter at something like 30.70 to match the hud alt with the altitude in external view

[Nix Mills]

On 5/19/2025 at 10:10 PM, Razor18 said:

Thanks!

Just a non campaign-specific question comes to my mind: why is the altitude recognition somwhow off? Tanker says he is orbiting Angels 25, but in fact he flies at around 24 500. Or if I fly at 28200, my check in message to Magic says I'm at Angels 29. Probably core DCS related, just asking, if it is a known bug?

It seems to me that when the air pressure in the weather settings is increased, increasing the altimeter setting doesn't quite keep up. From what I've noticed, but I could be wrong, the difference between you what you see in your HUD and what is the 'true' altitude (which you can see on the F10 map) gets greater the higher the pressure.

The script that talks out player's altitude (e.g. when checking in with Magic), is based on 'true' altitude and then rounded down to more or less match what you'll normally see in your HUD , which by default always seems to be 200-500 ft higher when you're up in the 20s. If you have also changed your altimeter settings, there could be an even bigger difference between what your HUD reads and what the true altitude is. You will also notice that this sometimes also affects your fuel state readings, which can be off with one or two decimal points - even when using the native DCS option to check in with Marshal.

Don't worry too much about it. The missions are set up with enough tolerance and your altitude "in the CAS stack" or in the transit corridor doesn't need to completely accurate.