Cache stated as "unknown" for OPFOR but "known" for BLUFOR

If you find a bug within PR:BF2 (including PRSP), please report it here.
Post Reply
Dude_Nukem
Posts: 131
Joined: 2010-07-25 19:20

Cache stated as "unknown" for OPFOR but "known" for BLUFOR

Post by Dude_Nukem »

Not sure if its a known bug or reported already, checked the forum though.

Description:

Like the title says, cache was "known" (blue diamond) for BLUFOR but stated as "unknown"(purple diamond) for OPFOR.

I had noticed this while I was watching a stream and joined the same server and was on the opposite team. Streamer was on the US side and I was on the ARF side.

Steps to Reproduce:

I don't know. But it was the 3rd or 4th cache.

After US destroyed the cache, 3 caches appeared on the map, which one of them was destroyed (the bugged one) but still the Purple diamond was shown on the map for OPFOR (I know this is a known bug).

The cache that was "bugged" was located in G5.

The BLUFOR only sees 2 caches at the same time, and not 3 like the ARF did.

Screenshots / Video:

Link to the streamer:
1911_Kev

Link to the vid:
http://www.twitch.tv/1911_kev/b/424729116

@ 40:30 you can see a cache in G5
@ 44:35 you see the cache is destroyed, in the top left of the screen and if you keep watching it is disappeard on the map

NOTE: Nothing much to see though. You can only see the cache is known for the BLUFOR, that's all. But nothing about someone mentioning that wasn't "known" for OPFOR. Or any other examples that it clearifies that it wasn't "known" for OPFOR.

Tested On:

Ramiel, Insurgency, PR Official Test Server - US, v1.0.21.0

It occured about 10:00 PRT, today.

Pretty much a game changer, I should say ;) . Hope I've informed you enough.

P.S.: Yeah I know, watching a stream and joining. But wasn't abusing it, it was just a coincidence I spotted that problem, so had a feeling to check it out and to share this with you.
Last edited by Dude_Nukem on 2013-07-02 11:03, edited 8 times in total.
DonDOOM
Posts: 819
Joined: 2007-02-10 11:42

Re: Cache stated as "unknown" for OPFOR but "known" for BLUFOR

Post by DonDOOM »

This issue has been posted up in our bugtracker, and is being taken care of.

Thanks for reporting it.
Image
Post Reply

Return to “PR:BF2 Bugs”