Page MenuHomeFeedback Tracker

No entry
Closed, ResolvedPublic

Description

Got this while playing a multiplayer match. {F17858}

Details

Legacy ID
2121949677
Severity
Minor
Resolution
Duplicate
Reproducibility
N/A
Category
Error Message
Additional Information

Event Timeline

AmmokK edited Steps To Reproduce. (Show Details)Mar 11 2013, 6:17 PM
AmmokK edited Additional Information. (Show Details)
AmmokK set Category to Error Message.
AmmokK set Reproducibility to N/A.
AmmokK set Severity to Minor.
AmmokK set Resolution to Duplicate.
AmmokK set Legacy ID to 2121949677.May 7 2016, 12:18 PM

Cant read, image too small.

Usually, no entry pops up if some config ref in the PBO's is messed up, as is expected from some weapons, attachments, clothing at the current stage of the game.

So nothing to worry about too much, but still post the exact error message if you can get it, so we know what caused the message.

Thx.

AmmokK added a subscriber: AmmokK.May 7 2016, 12:18 PM

Also messed up here :/
Here the normal version, sry...
http://www.abload.de/img/2013-03-11_00003yiu99.jpg

Config cpp, either something on the map you played (cpp is unpacked and unbinarized .BIN), or it is wrong in the game files (then it usually shows "No entry config.BIN:")

Something wrong with the markers.

If it was a multiplayer map, somebody used a broken Map marker reference to maybe mark an objective or player vehicle marker.

Havent seen the error in my playtime, so cant reproduce.

Dev's will be able to tell what happened.

Would be important to know which map it was if you remember.

Thx for info.

Sorry, can´t tell you since there isn´t a way i know off to tell you the latest maps i played.
If there is, please tell me and i will update the post.

This is a problem with a mission wen its have been made!

Script error probabli.

^ as above and as I said in the 3rd post - it is most likely that they used custom markers or a "player marker +update script" which couldnt find the marker for "Vehicle" (like, a player was in a vehicle or something and it fired that error).

If not many more people get this, it was definetly a map error.

Getting this error msg every MP match