Any ideas here guys how to locate the offending problem?

[TVRRMAN]

ok guys,

I was doing some programming today and have run into a huge problem that I can't seem to locate the cause of. When trying to edit a scenario that has two recently modded cars of mine in them, I'm seeing the following Error message:

Error: Badly Formed XML Document.
FILE: D:\build\CoreRelease\Code\Libs\Foundation\API\core/cFxException.h
LINE:113

Anyone encountered this and able to help solve this one?

Thanks in advance

[PapaXpress]

I am afraid that message means very simply that it cannot read the xml in your files. For example just last night I fixed that error by replacing a bad terrain tile (from my backup). I am sure you can see this error with malformed GEO, BIN and texture files as well. The best thing to do is retrace your steps and see what it was that you added which caused this error to pop up.

[TVRRMAN]

I am afraid that message means very simply that it cannot read the xml in your files. For example just last night I fixed that error by replacing a bad terrain tile (from my backup). I am sure you can see this error with malformed GEO, BIN and texture files as well. The best thing to do is retrace your steps and see what it was that you added which caused this error to pop up.

I think I found the problem and am working on a fix for it. Leave it to the Dynamic numbering to find a way to drive someone nuts...

[SMMDigital]

This is another one of those cryptic messages, like the SoBHH, that tells you something is wrong, but won't tell you what. In my experience, it can be something as simple as leaving a hash or a ">" out of a .bin file that you have edited.

[TVRRMAN]

This is another one of those cryptic messages, like the SoBHH, that tells you something is wrong, but won't tell you what. In my experience, it can be something as simple as leaving a hash or a ">" out of a .bin file that you have edited.

SMM, Thanks for the hints of where to look.

This morning, the problem was narrowed to two posibilities: either the DCSV controlling the numbering, or the Bin file that assigns what number or letter works for what. It turned out to be the DCSV file, which landed up with an extra line on four different number assignments. Once those were pulled out and the numbering double checked, the files were dumped back into the car and the problem went away...

Thanks for all the help guys