Thanks TotalBF2, DICE did try to Fix it!

[imported_Bama2]

As a Pilot one of my biggest bitches was the Bombing mode bug which was in game from day one. This bug is where a Friendly team mate enters a vehicle then gets out and it lights up as an enemy vehicle. Even when a Friendly re-entered it would still show up on my HUD as an enemy for several seconds. I posted on every forum I could find about this bug, wrote email to DICE & EA but nothing was done. Then TotalBF2 placed a forum here just for this kind of stuff so I posted again.

The first thing I did when I installed the new patch was to check if this bug was still in the game. It was, but it was also evident DICE had tried to fix it, which is a big step in the right direction. Now when a friendly exits a vehicle it remains lit as an enemy for only about 4 seconds, not permanently as before, and when a friendly reenters the same vehicle the HUD light goes out. Several AA sights still remain lit as enemy on my HUD even while no one is in them. You see this more often when a map is played twice.

This bug is still a problem to Friendly troops which I found out rather quickly. I killed a Clan member twice right off the bat because both times he had exited his Tank to repair it, and for 4 seconds while he was repairing it was shown to my HUD as an enemy. All in all I'm just happy they even tried to fix this bug, and maybe next time they will get it right.

Also thanks to TotalBF2 for getting this bug to DICE when nothing else worked.

[Paas]

Re: Thanks TotalBF2, DICE did try to Fix it!

This could be a balancing act.

I mean, if a jet knew "Exactly" when a vehicle was operated by someone, and knew "Exactly" when they left it; things would get kinda' pointless for the Tanks and APC's.

...I truely belevie, as a Jet Pilot, we shouldn't see ANYTHING on the ground other than Manned SAM sites attempting to gain a lock on us. If we want to bomb somthing, it needs to be designated by the ground pounds, and we should have to find it ourselves and deliver our ordinance with skill and precision.

The currently system is entirely too easy. If anything, only the "Bomber" in the bombing craft should see operated ground vehicles, as it's his official job to take them out.

If you wanted to keep the Radar in play. It needs to spot "Every" ground vehicle, regardless if it's friend or foe. Same with SAM sites and Linebackers. It should be up to the player to figure out what's friend or foe without some type of designation from a friendly. Thata' way, there is a level of "caution" involved in using these weapons.

But, I'm all about teamwork. So, maybe I'm a bit extreme.

{WP}Paas

[imported_RingMasTeR]

Re: Thanks TotalBF2, DICE did try to Fix it!

As a Pilot one of my biggest bitches was the Bombing mode bug which was in game from day one. This bug is where a Friendly team mate enters a vehicle then gets out and it lights up as an enemy vehicle. Even when a Friendly re-entered it would still show up on my HUD as an enemy for several seconds. I posted on every forum I could find about this bug, wrote email to DICE & EA but nothing was done. Then TotalBF2 placed a forum here just for this kind of stuff so I posted again.

The first thing I did when I installed the new patch was to check if this bug was still in the game. It was, but it was also evident DICE had tried to fix it, which is a big step in the right direction. Now when a friendly exits a vehicle it remains lit as an enemy for only about 4 seconds, not permanently as before, and when a friendly reenters the same vehicle the HUD light goes out. Several AA sights still remain lit as enemy on my HUD even while no one is in them. You see this more often when a map is played twice.

This bug is still a problem to Friendly troops which I found out rather quickly. I killed a Clan member twice right off the bat because both times he had exited his Tank to repair it, and for 4 seconds while he was repairing it was shown to my HUD as an enemy. All in all I'm just happy they even tried to fix this bug, and maybe next time they will get it right.

Also thanks to TotalBF2 for getting this bug to DICE when nothing else worked.

The way it was explained to me, was that this is not a bug. It was hard coded to be this way. Any enemy or friendly that exits the vehicle will have it show up in your HUD because the "engine is still warm". I used to belive this was a bug as well, but IVfluids was able to correct my thinking.
AFIAK this is working as intended .

[imported_Bama2]

Re: Thanks TotalBF2, DICE did try to Fix it!

All you say is fine for competive play, but Pub-Servers no way you will ever get that level of Team Work.


RingMasTeR:
Maybe it is working like they intended now, but it was not before. Also the secont Map rotation leaves many vehicle lit up as enemy from the start of the second game to the end of the game, even after respawns, including most every AA Stinger site.

[imported_RingMasTeR]

Re: Thanks TotalBF2, DICE did try to Fix it!

RingMasTeR:
Maybe it is working like they intended now, but it was not before. Also the secont Map rotation leaves many vehicle lit up as enemy from the start of the second game to the end of the game, even after respawns, including most every AA Stinger site.

I agree that it was bugged, I too have seen empty stinger and tow sites that stay lit the entire round even after they have been destroyed. I just wanted to be sure that it was understood that empty friendlies showing up on the HUD in and of itself was not a bug. But again, you are right on that occasionally the vacated vehicle remains lit when it should not. I've not had enough time in game post 1.2 to see if this has improved though. :hmm: