Bejaymac
the CRC's that you get from FlSpit only tell you the nickname of the offending item, it doesn't tell you where it is or what is causing it.
I know, but looking at the FLSpit output line:
FLSpit : ERROR: ArchDB::Get(0x89b1d005) failed. ID=-1984835579
and plugging the hex code e.g. 0x89b1d005 into CRCTool retrieves the info
cargopod_blue
(C:\Program Files\Microsoft Games\Freelancer\Data\EQUIPMENT\select_equip.ini)
so I can automate that process with a routine that takes all hexcodes from a FLSpit file and runs them through the CRCTool database to create a report.
BUT - I take your point that all the info required isn't in the spit file so I will hang fire on this for now. What I will do is a bit more digging so that I get a better understanding of what is involved in modding so that I might be able to help in future. I've read through some of the stickies in the editing forum and I'm getting a background.
Edit: I see your point Bejaymac, you can identify the file, but it doesn't tell you what is wrong, i.e. the data needs to be at the bottom rather than the top. I'll keep plodding on...
Regards,
Edited by - red777 on 6/18/2006 1:36:25 AM