[WAD] HELP MY PLANES WONT SHOOT

[Nicholasarm87]

They ONLY shoot if I manually tell them and they have targets for a land strike mission and there is no errors in the weapon release manual attack menu pls tell me what is going on I attached a photo save

not shooting.png (1.17 MiB) Viewed 224 times

God of War part not shooting.zip

(929.25 KiB) Downloaded 4 times

[blu3s]

How do you setup and assign the strike mission and how the aicrafts were assigned to the mission?

[Nikel]

I see many messages like this:

02-Jul-18 05:15:58 - [China] Wolf #6 (Su-30MKK2 Flanker G) is dropping Kep A/C Tarmac Space 2 (2x Large Aircraft) from its target list (Reason: The target is a waste of ammo).

[tylerblakebrandon]

I see many messages like this:

02-Jul-18 05:15:58 - [China] Wolf #6 (Su-30MKK2 Flanker G) is dropping Kep A/C Tarmac Space 2 (2x Large Aircraft) from its target list (Reason: The target is a waste of ammo).

I typically see such messages either when my ordnance is way OP for the target or if I have sufficiently damaged the target already with an earlier attack.

[Nicholasarm87]

How do you setup and assign the strike mission and how the aicrafts were assigned to the mission?

I created a mission called "Class Strike" (air intercept with land strike).

Initially, I designed a "Patrol" mission with "ASuW Patrol" for ground units. However, the units flew past nearby surface-to-air missile (SAM) sites to reach a target further away, which didn’t make sense. That's why I switched to the "Class Strike" mission. to choose specific targets but they weren't shooting i didn't have the ai or debug message turned on thats prolly why i didnt see that.. so they wont waste ammo on targets is that what Nikel means? where did u see the reason waste of ammo is that in the unit ai message? or the debug message?

[Raptorx7_slith]

All of the targets are already destroyed/heavily damaged so the aircraft doesn't engage them. You can see this in the message log as Nikel showed in his post

[Nicholasarm87]

All of the targets are already destroyed/heavily damaged so the aircraft doesn't engage them. You can see this in the message log as Nikel showed in his post

I'm confused about why the symbol for an airplane in the hangar still shows "1x Unknown unit (Last Recon: 8 hr 26 min ago)" even after I flew by at low altitude with the Mark 1 Eyeball. It still shows the occupied hanger symbol on the China side. When I switch sides in the editor, the occupied symbol disappears for the vietnam side. Do I need a better recon unit? The skies were clear, and the building is at 59 feet elevation. I also noticed the buildings were at 99% damage only after switching to editor mode.I wasn't aware that it was considered destroyed, especially since it usually indicates "destroyed so if its 99% they won't engage," and the occupied symbols were still visible on the hangars. Thanks for the clarification! The editor mode is really helpful.

Additionally, having the debug log file open on the side is great for seeing what happens in the background if you prefer not to go into editor mode to help answer theses questions

I'm trying to understand why the reconnaissance aircraft that flew by at low altitude didn't update the hangars. That's why I kept attempting to engage them, thinking I hadn't targeted the aircraft. Those are the mission targets, after all! I’ll have to restart and try this scenario again; it’s quite interesting, to say the least.

[thewood1]

Recon is no where near perfect. Its part of the game. Recon aircraft can't see inside hangers.

[Dimitris]

I'm confused about why the symbol for an airplane in the hangar still shows "1x Unknown unit (Last Recon: 8 hr 26 min ago)" even after I flew by at low altitude with the Mark 1 Eyeball. It still shows the occupied hanger symbol on the China side. When I switch sides in the editor, the occupied symbol disappears for the vietnam side. Do I need a better recon unit? The skies were clear, and the building is at 59 feet elevation. I also noticed the buildings were at 99% damage only after switching to editor mode.I wasn't aware that it was considered destroyed, especially since it usually indicates "destroyed so if its 99% they won't engage," and the occupied symbols were still visible on the hangars. Thanks for the clarification! The editor mode is really helpful.

Additionally, having the debug log file open on the side is great for seeing what happens in the background if you prefer not to go into editor mode to help answer theses questions

I'm trying to understand why the reconnaissance aircraft that flew by at low altitude didn't update the hangars. That's why I kept attempting to engage them, thinking I hadn't targeted the aircraft. Those are the mission targets, after all! I’ll have to restart and try this scenario again; it’s quite interesting, to say the least.

Flying close to the hangar is not a guarantee of being able to see what is / isn't INSIDE the hangar. The only way to tell for sure is to have a suitable observer near the hangar the very moment that an aircraft goes into it or comes out of it. (This is why persistent surveillance, like e.g. a SOF team camped near the airbase, is so incredibly useful).

Read more: https://command.matrixgames.com/?p=4236