Unexpectedly exploded on touchdown
-
Which SAM launcher? What Unit?
Tiger Spirit Campaign.
Hwangju Airbase (relocated 80th Fighter Squadron there)
14th MIM23 Hawk Air Defense Battalion (4228)
Air Defense assigned: Hwangju Airbase -
… need the campaign files.
For info. I’ve checked the HAWK Launchers hitboxes, they are perfectly fine (12.5ft long / 6ft large / 7ft height)
-
I have had two different examples of blowing up on runways/taxiways.
1: I had used Mission Commander to change a damaged airbase’s runways to “Set Repaired”. When I got into the cockpit for a new mission I could visually see craters on the runway, but AI aircraft were taking off without problem so I continued. BOOM! I later used Mission Commander to change the runway status to “Set No Damage” but the same behaviour persisted. (I realise I am not an expert with Mission Commander and probably missed something important, but I am just pointing out it happened).
The crater is a persistant object that has to be removed separately in Mission Commander (same name tab).
-
Wait … the Campaign files has been edited !!!
… if yes … do it at your own risk.
-
Wait … the Campaign files has been edited !!!
… if yes … do it at your own risk.
I am aware that using Mission Commander to move a FS to a different airbase probably introduces some unpredictability. I didn’t log a bug report because of this.
Still, I posted this story to help the OP understand possible causes.
-
I thought I should test taxiing around the Hawk again as I definitely blew up once, or twice, before.
I did not expect this result …
-
@Red:
One of the consequences of using an outdated version. This doesn’t happen anymore
Is landing on crater fixed on 4.34?
On 4.33 hitting crater just ended mission without any death or plane loss or any other input about crash. -
correct me if i wrong, on a normal mission if the runway was damage, depending on the ammunition there should be a cater, that should be removed after a couple of hours because the progres of the mission and eventualy the runway should be repair, it could mean that even it you set the health in 100 and dont remove the cater of the active objects on the list in missin commander, it dosent mean you eventualy will crash?
-
Maybe bad HMVV hitbox. Or … (and this is what I think about), corrupted campaign file.
-
correct me if i wrong, on a normal mission if the runway was damage, depending on the ammunition there should be a cater, that should be removed after a couple of hours because the progres of the mission and eventualy the runway should be repair, it could mean that even it you set the health in 100 and dont remove the cater of the active objects on the list in missin commander, it dosent mean you eventualy will crash?
No experience of own bombed runways on 4.34 but in 4.33 runway damage is repaired in 6-8h and after that base can launch missions again. Bit of problem is that craters took 2-3h more time to disappear from AF and taxing on those ended mission for human player and yo wingmans won’t taxi on those but still AF was capable to launch AI missions.
-
Recently in 4.34 my runway was attacked and I couldn’t plan or launch any missions, even after 24 hours. I used mission commander to repair the airfield and remove the craters in the persistant object tab and airfield was usable again.
Back on topic I once mysteriously exploded right on touchdown after an overhead approach. Turns out my bomber pattern overhead resulted in my AI wingman landing right on top of me since my pattern was too long according to Tacview replay.
My last untimely demise came when I gave the “switch side” command to my AI wingie as he was rejoining for the overhead. As he was correcting back from overshooting his rejoin to fingertip position he dutifully crossed over right into me and boom! LOL. So my burnt-to-a-crisp corpse was court-martialed for my trouble as he floated down comfortably under his canopy. AI needs some work. LOL!
-
I thought I should test taxiing around the Hawk again as I definitely blew up once, or twice, before.
I did not expect this result …
This happens when you have invulnerability turned on and you crash / die.
-
This happens when you have invulnerability turned on and you crash / die.
I was about to say that I never have invulnerability turned on, but I remember I selected the default pilot for this test to avoid having a death/court martial on my pilot record.
Sent from my iPhone using Tapatalk