Still Land Attack Woes

[Pnzrldr]

Running a 688 with VLS in the 2004 campaign mod. Land attack missions easier to get the missiles away... but still need some tweaks. Ordered to attack Gremikha. While enroute, encountered two nuke boats, within the specified 100 miles of Gremikha in the mission orders. Sank both, but didn't esc out of the encounter. Checked range to target - well within 100 miles. Launched all TLAMs. All hit. But when I esc out I got no credit for the land attack. Mission failed. C'mon guys - we can do better.

[stratege1401]

one of the objectif i guess was to remain undetected ... sinking two nuke sub is not. objectif fail.

[-Pv-]

Can the OP confirm one of the objectives is to remain undetected?
Impossible to remain undetected while launching VLS.

It should be possible to sink vessels and not have your sub targeted.
-Pv-

[Mspot]

one of the objectif i guess was to remain undetected ... sinking two nuke sub is not. objectif fail.
Agreed. However, that is stated in all orders in all missions -- either remain undetected and or avoid ASW patrols. If that is an actual parameter then it should be "spelled out." Otherwise, as noted by Old Man, you are detected as soon as you launch. So, if detection after launch is permissible then, again, such things should be coded in the mission and that made clear in the mission orders.

[Delgard]

I am not sure, but I escaped out pretty quickly on a Gremika TLAM mission. The ESC page said the TLAM strike was completed 8 for 8 but I got a mission failure. I wondered if my TLAMs actually struck in the quickness of my ESC from the mission.

It made me wonder how long the TLAMs take to fly the distance so that I need to stay in the mission until they actually hit the target. Should I wait?

[GeneralGamer]

I wondered if my TLAMs actually struck in the quickness of my ESC from the mission.
Should I wait?

Short answer yes

[Delgard]

Normally, I sit and reload tubes after every mission. If I remember correctly, I did not have anything nearby.

Maybe I should play some chess with the XO before ESCing out. :o

[-Pv-]

Short answer yes

Is that "yes" to BOTH questions?
-Pv-

[GeneralGamer]

The mission is stealth. get in and avoid all contacts, including mine fields. When the coast is clear (no contacts in sight,fire and after all missiles have hit you can either leave the mission by the escape key, or fight your way out. Press F3 to make sure your last missile hit.

I agree with you PV.

If you want a shooting contest the MPA and Helos plus the warships will be all over you in shallow water. :ping:

[-Pv-]

So, Stealth until missile are fired, then the stealth restriction is lifted?
-Pv-

[GeneralGamer]

So, Stealth until missile are fired, then the stealth restriction is lifted?
-Pv-

I wasn't clear on my answer. Sorry. My bad. Stealth isn't essential...unless the updates changed the requirements.

However once you are detected it's almost impossible to fire the missiles and avoid all the MPA's, Helos and Warships, so yes, stealth is better to get into position.

I also found you can end the mission right after the last missile hit's (unless there are aircraft near, etc. You still have to leave the area, but at least you have all your weapons to use, to accomplish it. To me it's better to have all your weapons trying to get out of the zone than use them to get into the harbor.

I'm not saying you can't kill a Warship if he gets to close (going in) but if your position is reported and or discovered, it's way more difficult to fire missiles. In other words you can try any way that you think will work for you. I like the stealth way, It avoids possible complications

Here is an older Specops mission that is a good example of what I'm trying to say. No missiles but the stealth is well illustrated. I hope it helps, until I can do another TLAM mission.

https://www.youtube.com/watch?v=9PGnRIno_dc

[-Pv-]

The devs seem be trying to make stealth harder, so keeping my ear to the ground on this one.
-Pv-

[Killerfish Games]

Stealth is no longer a factor in Land Strike and Insertion mission success.

The issue the OP had was they they encountered an ASW patrol close to Gremikha. So this spawns a combat mission.

At the end of this combat, the OP sees that he is within striking distance of Gremikha and lets the TLAMs away. Only problem is that this is a combat mission, NOT the land strike mission. So the TLAM launches don't count.

Had the OP left combat, sailed closer to Gremikha they would have got another briefing stating "We are in the deployment zone", at which point they could fire the TLAMs without an issue. In addition, when pressing escape, they would also see the end mission menu stating whether the land strike was successful or not.

This is a limitation of the way we generate separate combat and player missions from the strategic map. We've tried to make it clearer with the "We are in the deployment zone" message in the briefing along with the exit mission menu stating whether a land strike was completed or not. But clearly this is not sufficient.

Ultimately the solution will be to merge the actual player mission success parameters into other mission types such that if they are ever met, the mission is a success, regardless of whether the player is actually on that mission or not. This is a complex feature though.

[GeneralGamer]

Stealth is no longer a factor in Land Strike and Insertion mission success.

The issue the OP had was they they encountered an ASW patrol close to Gremikha. So this spawns a combat mission.

At the end of this combat, the OP sees that he is within striking distance of Gremikha and lets the TLAMs away. Only problem is that this is a combat mission, NOT the land strike mission. So the TLAM launches don't count.

Had the OP left combat, sailed closer to Gremikha they would have got another briefing stating "We are in the deployment zone", at which point they could fire the TLAMs without an issue. In addition, when pressing escape, they would also see the end mission menu stating whether the land strike was successful or not.

This is a limitation of the way we generate separate combat and player missions from the strategic map. We've tried to make it clearer with the "We are in the deployment zone" message in the briefing along with the exit mission menu stating whether a land strike was completed or not. But clearly this is not sufficient.

Ultimately the solution will be to merge the actual player mission success parameters into other mission types such that if they are ever met, the mission is a success, regardless of whether the player is actually on that mission or not. This is a complex feature though.

I have the latest update and just tried the strike from the sea mission. I made it out alive but there is still a circle as before in the mission. Is that the deployment zone, or is that where you shoot your TLAMS into?

Or is the single mission different than the campaign missions?

Now I'm confused lol

Thanks:yep:

[Mspot]

Ditto, above. I've encountered what KFG states and now understand. Still, can be a bit confusing when not totally immersed in the game. But, sounds like KFG is aware and has fixed, or nearly fixed. Perhaps some sort of aural notification from the crew and or textual indicators would help?

[-Pv-]

One possibility would be to place the text "Encounter Mission" at the top of the briefing when intercepting a non-primary combat mission along the campaign map route. When your sub intercepts the main campaign mission, place the text "Primary Mission" at the top of the briefing.
-Pv-

[Pnzrldr]

Stealth is no longer a factor in Land Strike and Insertion mission success.

The issue the OP had was they they encountered an ASW patrol close to Gremikha. So this spawns a combat mission.

At the end of this combat, the OP sees that he is within striking distance of Gremikha and lets the TLAMs away. Only problem is that this is a combat mission, NOT the land strike mission. So the TLAM launches don't count.

Had the OP left combat, sailed closer to Gremikha they would have got another briefing stating "We are in the deployment zone", at which point they could fire the TLAMs without an issue. In addition, when pressing escape, they would also see the end mission menu stating whether the land strike was successful or not.

This is a limitation of the way we generate separate combat and player missions from the strategic map. We've tried to make it clearer with the "We are in the deployment zone" message in the briefing along with the exit mission menu stating whether a land strike was completed or not. But clearly this is not sufficient.

Ultimately the solution will be to merge the actual player mission success parameters into other mission types such that if they are ever met, the mission is a success, regardless of whether the player is actually on that mission or not. This is a complex feature though.

Yes, exactly this. Not sure how your mission trees are built, but would recommend that you alter this. Should be possible for a savvy player to exit the strategic map to tactical once w/in TLAM range and let fly, or let fly from a "combat" mission. Building more successful mission success parameters into random "combat" missions will allow much more flexible missions. Rather than just "go do this single task," you can set out things like, "eliminate enemy nuclear attack submarines that may or may not be trying to enter the North Atlantic," or "sink Xxx tons of enemy support shipping." Real combat is not, as I know you are aware, a strict set of discrete engagements. The more merge we get the more immersive the experience.