[0973] Kashan AAS 64 - no attack order

[R-DEV]rPoXoTauJIo · 2011-09-18, 17:49

Description:
When played Kashan, after some time i discovered that we can't attack any flags, due missing attack order

Steps to Reproduce:
Load Kashan AAS 64, hope that flags will be placed in the same positions like on screenshot

Tested On:
Kashan Desert AAS-64, pr2.vbios.com, v0.973

Screenshots / Video:

=HCM= Shwedor · 2011-09-19, 00:03

I've seen this happen on other maps, usually if you were to move to the "usual" next flag it will cap properly.
I see on the map that there is only one person in the cap zone of the next flag (south village) which may be why you were unable to advance. Thankfully with AASv4 it is far easier to identify where to assault next if the attack marker is missing, however I believe kashan's flags are always in the same, and rather unusual, spots which makes it hard if you are unfamiliar with the map and you get this bug.

2011-09-18, 17:49	#1
[R-DEV]rPoXoTauJIo PR:BF2 Developer Join Date: Jul 2011 Posts: 1,966 Belarus Location: Minsk	[0973] Kashan AAS 64 - no attack order Description: When played Kashan, after some time i discovered that we can't attack any flags, due missing attack order Steps to Reproduce: Load Kashan AAS 64, hope that flags will be placed in the same positions like on screenshot Tested On: Kashan Desert AAS-64, pr2.vbios.com, v0.973 Screenshots / Video:

2011-09-19, 00:03	#2
=HCM= Shwedor Join Date: Sep 2009 Posts: 430 United States of America Location: Virginia	Re: [0973] Kashan AAS 64 - no attack order I've seen this happen on other maps, usually if you were to move to the "usual" next flag it will cap properly. I see on the map that there is only one person in the cap zone of the next flag (south village) which may be why you were unable to advance. Thankfully with AASv4 it is far easier to identify where to assault next if the attack marker is missing, however I believe kashan's flags are always in the same, and rather unusual, spots which makes it hard if you are unfamiliar with the map and you get this bug.