Mission 12 targets invincible

[Augermc]

On mission 12, I have foud the targets to be invincible.  I fired all of my hellfires, one by one, into a truck with a gun mounted. Every one hit, and even tho it killed the soldiers around the vehicle, it did no damahe to the vehicle.  I checked the stats, and they say "hit" on each hellfire, but never a kill.  Damn thing shot me down when I tried to close for rockets or guns.  

[Florence201]

On 10/18/2024 at 3:35 AM, Augermc said:

On mission 12, I have foud the targets to be invincible.  I fired all of my hellfires, one by one, into a truck with a gun mounted. Every one hit, and even tho it killed the soldiers around the vehicle, it did no damahe to the vehicle.  I checked the stats, and they say "hit" on each hellfire, but never a kill.  Damn thing shot me down when I tried to close for rockets or guns.  

Do you have a trk or TacView file I can look at please?

No units should be set to invincible 

[Augermc]

Here is a video clip.  I actually shot it 4 times, but am only able to share a 50 meg file so I had to trim it.  Each shot is a direct hit, with both IR as well as radar hellfires.  Result is always the same....truck keeps on firing away. Maybe I have a setting wrong? Not sure, but all of the other missions up to mission 12 have worked perfectly.  

 

 

[Athlon]

Same here, Playing as I type. Technicals and infantry are indestructible

 

[Florence201]

OK, there's a debrief in my feedback area of the Fight's On discord.

But 

 

BLUF

Are you pressing SPACEBAR when told to inform JTAC that you're in hot?

 

If not, then the visual firefight triggers i have set (so you get good visuals and still have targets to engage) will not fire. When working with JTACs you MUST follow their instructions.

[Kharrn]

shameless copy/paste from FoS discord, just as an "add on" answer to what Florence already said.

Zitat

JTAC calls smoke out -> space to contact smoke -> JTAC 5 line -> copy 5 Line -> Foghorn will distribute tasking for Ugly -> calls IN (meaning you are IN from the IP/BP to the target and wait for the "hot" call) -> ARSON calls JTAC for sitrep/check-in, JTAC will tell them to standby and will give you the "cleared hot" -> then you can engage targets close to Widow!

 

The targets further away to the east (mortars and AAA) are not for Ugly to engage. I dont know if they are immortal too. but that is part of the JTACs gameplan that you stay west of the convoy and later on ARSON will dust the targets further east.

 

[Its a great mission to play as CPG and let loose the gun doing 90° strafing runs parallel to the convoy or to Pilot with FFARs and train some mid range FFAR skills

cheers and have fun]

So always follow procedure and tasking, especially when working with controllers (eg ATC, FAC, JTAC, CCT).

cheers

[MSMStannyl]

Came here originally because I was having the same invincibility issue. I even set myself to invincible to make 100% sure and yeh, could not kill anyone.

That said, it does seem there are some triggers you have to pay attention to. The text doesn't stay on the screen too long so it's possible to miss it. Make sure you hit spacebar when you see the red smoke. Then there will be another prompt for a nine-line. Make sure you hit space to that as well. Then you should be good, but just pay attention as I think there may be another spacebar required for calling yourself "in". 

Once you get that, you should be good to go and enemies are no longer invincible.

 

Side note, there is still a bug for me with my wingman. Even though the radio comms in the beginning says "Two is ready to lift", the other Apache is not started or spinning up and will not follow me on mission. It just sits at the FOB. I didn't see any prompts other than the initial spacebar to request takeoff (which gives the "two is ready to lift" message) but, as I said, he never takes off with me and it ends up being a solo flight.

[MSMStannyl]

Actually, to add to my above bug with the wingman, it did end up working but strangely not until I was on the way back to the FOB and had to change freq back to FOB freq (131.6). Once that happened, the script of Ugly 5-1 "lifting" happened and the wingman took off, just in time for me to land. Lol

 

I've waited for quite a long time at the begining of the mission and the "lifting" communications never happens.

[Kharrn]

Am 21.12.2024 um 20:37 schrieb MSMStannyl:

Actually, to add to my above bug with the wingman, it did end up working but strangely not until I was on the way back to the FOB and had to change freq back to FOB freq (131.6). Once that happened, the script of Ugly 5-1 "lifting" happened and the wingman took off, just in time for me to land. Lol

 

I've waited for quite a long time at the begining of the mission and the "lifting" communications never happens.

If ppl know and follow procedures like i already stated in above comments, you wont miss triggers. Campaigns usually require knowledge about A/C and TTPs and are not a "basic learning environment". Dont take it personally, its just how i see this.

 

For the wingman you need to put in the correct Freqs at startup as stated in the mission brief and kneeboard. Afaik Florence changed all missions so that there are random freqs set up in the cold Apache. So you really have to change them before continuing. Maybe check if you got the last update to the campaign

Greetings and gl

[Florence201]

As Kharn points out, despite previous versions having the freqs already there at start up, there was a core Apache issue that meant the triggers in the ME were not picking up the radios correctly. 

Ai have now changed a ll pre-start freqs to jibberish, such that once you input as per the brief, all should be good.

 

And yes, there are a number of trigger/spacebar points before you are cleared hot by the JTAC. If you do not press when required, then you will not be cleared hot (and the enemy WILL remain INVINCIBLE - Done so i can have a fire fight, but leave something for the player to still attack).

[Hammer1-1]

Im getting the same issue here. Track is too big to post, but this is the only mission Ive had issues since I reported them first off months ago. Also noticed that several other units were not taking off or spawning at mission start like Ugly 2.

 

Edit: I see what the problem is. Theres no message at the beginning to contact BATMAN for takeoff, so that script never gets triggered. I managed to find this out at the end ; I was wondering why I couldnt select the F10 menu to land back at Batman, but when I landed I tuned it manually to Batman 131.6 and the F-10 menu appeared. Clicked it and it cleared me to takeoff which surprised me. Then I clicked it again and it completed the mission for me as all those scripts finally caught up. 

Edited March 15 by Hammer1-1

[Florence201]

On 3/15/2025 at 2:08 AM, Hammer1-1 said:

Im getting the same issue here. Track is too big to post, but this is the only mission Ive had issues since I reported them first off months ago. Also noticed that several other units were not taking off or spawning at mission start like Ugly 2.

 

Edit: I see what the problem is. Theres no message at the beginning to contact BATMAN for takeoff, so that script never gets triggered. I managed to find this out at the end ; I was wondering why I couldnt select the F10 menu to land back at Batman, but when I landed I tuned it manually to Batman 131.6 and the F-10 menu appeared. Clicked it and it cleared me to takeoff which surprised me. Then I clicked it again and it completed the mission for me as all those scripts finally caught up. 

OK, 

 

SO the F10 not showing at take off MAY be because the frequency isn't set correctly and therefore the trigger doesn't fire. Try setting the frreq away from 131.6, then back to it. This should fire the trigger. Have you been using PRESETS? Throughout the build process i had issues with PRESETs not being detected by the ME triggers.

[Hammer1-1]

6 hours ago, Florence201 said:

OK, 

 

SO the F10 not showing at take off MAY be because the frequency isn't set correctly and therefore the trigger doesn't fire. Try setting the frreq away from 131.6, then back to it. This should fire the trigger. Have you been using PRESETS? Throughout the build process i had issues with PRESETs not being detected by the ME triggers.

No, I insert the frequencies all the time by hand. I didnt know to select F10, I just waited for a minute, scanned the messages to see if I missed it and just took off. I never got a hint stating I needed to use F10 to get clearance to take off. Normally I would get a message stating I was clear to start, didnt get anything in M12.

Edited March 17 by Hammer1-1

[Florence201]

15 hours ago, Hammer1-1 said:

No, I insert the frequencies all the time by hand. I didnt know to select F10, I just waited for a minute, scanned the messages to see if I missed it and just took off. I never got a hint stating I needed to use F10 to get clearance to take off. Normally I would get a message stating I was clear to start, didnt get anything in M12.

Very strange. It normally appears after X amount of time and stays until you select F10. I'll look into it thanks

[Florence201]

On 3/15/2025 at 2:08 AM, Hammer1-1 said:

Im getting the same issue here. Track is too big to post, but this is the only mission Ive had issues since I reported them first off months ago. Also noticed that several other units were not taking off or spawning at mission start like Ugly 2.

 

Edit: I see what the problem is. Theres no message at the beginning to contact BATMAN for takeoff, so that script never gets triggered. I managed to find this out at the end ; I was wondering why I couldnt select the F10 menu to land back at Batman, but when I landed I tuned it manually to Batman 131.6 and the F-10 menu appeared. Clicked it and it cleared me to takeoff which surprised me. Then I clicked it again and it completed the mission for me as all those scripts finally caught up. 

Having looked at mission 12, the prompt is to select SPACEBAR when ready to lift, so there is no F10 menu. I have increased the time the prompt message is displayed, so there's no confusion as to what needs to be pressed one ready.

As for UGLY5-2 not spawning, the trigger for that fires off both player altitude AND the take off comm having happened

Hope this helps

Edited March 23 by Florence201

[Hammer1-1]

4 minutes ago, Florence201 said:

Having looked at mission 12, the prompt is to select SPACEBAR when ready to lift, so there is no F10 menu. I have increased the time the prompt message is displayed, so there's no confusion as to what needs to be pressed one ready.

As for UGLY5-2 not spawning, the trigger for that fires off both player altitude AND the take off comm having happened

Hope this helps

Im not saying the F10 menu wasnt there, Im saying there was nothing telling me to press F10 to get clearance.

[Florence201]

1 minute ago, Hammer1-1 said:

Im not saying the F10 menu wasnt there, Im saying there was nothing telling me to press F10 to get clearance.

That's the point, you don't press F10 for clearance, you press SPACEBAR in this mission

[Hammer1-1]

And I never got that message, even though I tried hitting the space bar a few times to try to trigger something. I didnt get anything, so I just took off and completed the mission. Only after I landed did everything catch up, but thats only because I saw the F10 menu and decided to give that a shot.Its been over a week since I finished the campaign, so the finer details are out of mind now, but again I just never got a message to do anything. Just had the convo with the gunner and thats it.

If you want, I can replay the mission today and post the track..I dont mind.

Edited March 23 by Hammer1-1

[Florence201]

Up to you buddy, but i have made updates that hopefully will make life easier for others lol