v1.4.6.0 Sbena Outskirts INS All Cache Locations Appear

[BattleGuy234]

Odd bug today...on Sbena Outskirts playing as MEC in INS mode we saw that all possible cache locations appeared in the game world. They weren't real and couldn't be blown up...but it made it confusing trying to find the real cache.

[AlonTavor]

Last time I saw that happen was on a server with bad configuration.

[FFG]

Were you on FCV by chance? they seem to have that bug alot.

[Rabbit]

Were you on FCV by chance? they seem to have that bug alot.

Could also be because of a shitty mapper.

[QuickLoad]

I thought it was fixed by now, FCV has a lot of 'ghost caches' since a month or three ago.
I haven't had the chance to play any other servers(why sacrifice good ping for anything else), haven't seen it too recently but there's a good chance it is still apparent.

Happened the most with Fallujah West, though.

[cantpick]

happened ~8 hours ago. 1.4.9.0+Fallujah+FCV. Not sure it was all caches, I went to a couple cache spots and did not see any ... but maybe someone else had destroyed the fake caches at those spots.
Maybe retitle thread, almost made a new thread. for fallujah.

[AlonTavor]

happened ~8 hours ago. 1.4.9.0+Fallujah+FCV. Not sure it was all caches, I went to a couple cache spots and did not see any ... but maybe someone else had destroyed the fake caches at those spots.
Maybe retitle thread, almost made a new thread. for fallujah.

Not map related. All caches are already in the map when it map loads, the Python code starts with destroying every single one of them.
It uses a lot of BF2 engine calls to get and delete these objects, impossible to debug these.

[RENEGADO]

This happened 1 month ago in our server playing the same map in Night layout

[PeppeJ]

Not map related. All caches are already in the map when it map loads, the Python code starts with destroying every single one of them.
It uses a lot of BF2 engine calls to get and delete these objects, impossible to debug these.

Would it be possible to implement an admin command that re-runs the code, just in case this error occurs? Something like "!FixCaches" It's obviously not a fix, but it could help by band-aiding the issue