possible problem(s) with CRCTool Beta 2
First of all this is a great tool for debugging mods and the main reason that I found a couple of possible issues is probably due to the size of this mod?
I processed FL with the FrontierSpace mod installed and this generated a .cdb file of 383 megs and I exported this to a text file that was 412 megs in size.
Firstly, it took me a while to figure why there were hex values in the .cdb file that are not in the exported text file but I now think that the problem is that when you export to the text file CRCTool is silently failing when it runs out of memory writing the text output. I believe this is the case as I know there are values in the .cdb file that are not in the .txt file, the 2 files and my used memory add up to about 1 gig which is what I have installed.
Second issue. In .txt output file there are 9 mill. lines but I believe that there are many duplicated lines, specifically I found that the entry for:
0xe981eddd 2380211782
WeaponPlate.tga
C:\Program Files\Microsoft Games\Freelancer\Data\SHIPS\Frontier\FIREBASE\RAVENCL
AW\RavenCLaw.3db
is repeated 2,871,339 times. I noticed this after looking at chunks of the .txt file towards the end to find hex values to use as test data for a routine that I'm working on and seeing the repeated values. This is easy to verify, just run a findstr command on the .txt file and pipe the output to a file then look at the file:
C:\temp>findstr /I 0xe981eddd tmp.txt >lc.txt
and count the lines in the 68 meg output lc.txt (preferably with a program or dos version of the Unix lc command - not manually )
I know that the source to CRCTool is distributed with it and I have had a look. I know enough Cpp to read the code and have a good idea what it is doing but determining if it is going awray it is something else.
Anyone else found this problem or have any suggestions?
Finally, I should point out that I have no reason to believe that using CRCTool with the .cdb database by itself is in any way wrong, the two issues that I found are w.r.t. to the "save as text" option.
Rgds.
I processed FL with the FrontierSpace mod installed and this generated a .cdb file of 383 megs and I exported this to a text file that was 412 megs in size.
Firstly, it took me a while to figure why there were hex values in the .cdb file that are not in the exported text file but I now think that the problem is that when you export to the text file CRCTool is silently failing when it runs out of memory writing the text output. I believe this is the case as I know there are values in the .cdb file that are not in the .txt file, the 2 files and my used memory add up to about 1 gig which is what I have installed.
Second issue. In .txt output file there are 9 mill. lines but I believe that there are many duplicated lines, specifically I found that the entry for:
0xe981eddd 2380211782
WeaponPlate.tga
C:\Program Files\Microsoft Games\Freelancer\Data\SHIPS\Frontier\FIREBASE\RAVENCL
AW\RavenCLaw.3db
is repeated 2,871,339 times. I noticed this after looking at chunks of the .txt file towards the end to find hex values to use as test data for a routine that I'm working on and seeing the repeated values. This is easy to verify, just run a findstr command on the .txt file and pipe the output to a file then look at the file:
C:\temp>findstr /I 0xe981eddd tmp.txt >lc.txt
and count the lines in the 68 meg output lc.txt (preferably with a program or dos version of the Unix lc command - not manually )
I know that the source to CRCTool is distributed with it and I have had a look. I know enough Cpp to read the code and have a good idea what it is doing but determining if it is going awray it is something else.
Anyone else found this problem or have any suggestions?
Finally, I should point out that I have no reason to believe that using CRCTool with the .cdb database by itself is in any way wrong, the two issues that I found are w.r.t. to the "save as text" option.
Rgds.