This came up in my Error Log:
what is it, and how would i fix it?

Hmm, I've seen that one before, but I've never figured out how to fix it. If anyone knows, let us know so we can add it to the BF2 Errors thread.

pebblefl ? pebbles? ok...

PblConfig: invalid config; 'DATA' chunk expected
chunk.GetId() == _ID( 'D', 'A', 'T', 'A' )

I'm guessing in the config (a munged odf is an example of a config) file for this "pebble" or whatever there was supposed to be a data chunk but it was mysteriously not there. Could indicate a munge error. I'm not sure if pebble is a clever name pandemic made up, or if it indicates some new type of class.

There is an object called pebble in one of the default assests. It crashed my map whenever I tried to add it.

Wazmol have you been adding pebbles?

It could be that the programmers never got pebbles working.

wazmol wrote:This came up in my Error Log:

Code: Select all

Message Severity: 3
c:\battlefront2\main\pebblefl\common\PblConfig.h(30)
PblConfig: invalid config; 'DATA' chunk expected
chunk.GetId() == _ID( 'D', 'A', 'T', 'A' )

what is it, and how would i fix it?

The best way to track down this culprit is to undo whatever changes or additons you made to your map before you started getting this error, then munge and test each time you add something back until the error creeps up again.

It seems like it started happening when i first added a new model, just an average prop.

Actually, if this helps i havent added any pebbles lol Rep. And the map runs fine in the modtools.

I know this is an old topic, but I feel that the bump is warranted. I got this error a couple days ago working on the Pack, and it scared the heck out of me, because it caused nearly every map to crash. (And no one knew how to fix it or debug it, or so looking through old topics led me to believe.)

I ended up fixing it, and with some whittling-down of possible causes I finally figured out that one of my .hud files in a custom side had a misspelling "MesshInfo" instead of "MeshInfo."

I can't say for certain that this error is only caused by an issue in a custom .hud file, but I can tell you that that my problem (which resulted in the same error) was caused by a custom .hud file issue. Hopefully this'll help someone in the future.

Track down Mr. Pebble, and delete him from your mod. And I hope this isn't for BF0!