Bug #7478

People left behind on Skalisty Prolev Island Lopotev Mission

Added by dbeaty2 over 5 years ago. Updated over 4 years ago.

Status:Expired Start date:12/28/2009
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Campaign
Target version:-
Affected ArmA II version:1.05.62017 First affected build:
Reproduced by another DH user:No First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:No NGUrl:
Related to content of DLC: WIKIurl:

Description

Dogs of War Campaign, I took a command USMC UH60 to Skalisty Island after the USMC joined the campaign in search of Loptev. This was a waypoint I assigned to the the UH60, I did not fly the Blackhawk. Razor landed and left the UH60. After capture of Lopotev, and boarding the EVAC helo that gets sent, both helo's would take off leaving Lopotev and at least one or two Razor on the island.

History

Updated by Fireball over 5 years ago

  • Category changed from AI Issues to Campaign
  • Status changed from New to Assigned

Updated by Fireball over 5 years ago

  • Due date changed from 01/12/2010 to 04/12/2010

Updated by kju almost 5 years ago

  • Due date changed from 04/12/2010 to 10/01/2010
  • Status changed from Assigned to Feedback
  • Audio card set to Please specify!
  • Size of OS swap file set to Please specify!
  • I am using some Mods set to No
  • Reproducible for you set to No

Still true in 1.07 or better latest CO?

Updated by Hanzu over 4 years ago

I just played this part with 1.57.77159 patch, but I have arrived to very same island by "swimming" with USMC APC so I did not have those three UH-60 Blackhawk's to transport or back me up (they were shot down or crashed earlier).

After wounding and capturing Loptev I boarded Mi-17 (Civilian) helicopter that got sent for us and all 3 Razor Team members and Lopotev boarded it too quite fast after me (without me giving any orders to do so). As we know both AI helicopter pilot and AI movement behaviour has been tweaked a lot lately around patch 1.57 builds so I assume this bug can not be reproduced anymore.

I suggest set Status to Resolved/Closed/Expired until proven otherwise.

Updated by kju over 4 years ago

  • Due date deleted (10/01/2010)
  • Status changed from Feedback to Expired

Thanks Hanzu!

Also available in: Atom PDF