Number Translation
-
-
If you mean to translate the number you have shown to a decimal number, that is not useful.
This number is a CRC “hash” code which is generated from the name of a game component such as a ship name or weapon name or texture name or planet name or other name. Using these instead of the full names helps FK to run faster.
FF has given you the link to the CRC tool, which you first use to generate all the hashcodes from the Freelancer game or mod you have installed, and these are then stored in a database - you can define the name and its location on your PC.
Then you can search in the database with the CRC tool for your hashcode. If it is found, it will be shown.
You can also use the tool to calculate the hashcode for any text or name you enter.
Hope this helps.
-
Hey,
Thanks for trying. The program works just like the previous version. The database is clunky and it lacks a filter to sort un-needed information. Between DB_Hash, FL Spit and FL Scan II the data is was seeking never showed in my mod. Yes, it was active when I checked the DB. The trio all kept giving me one hash for something not in my ini files. So, like all brave modder, I restored the backup and went back to the drawing board. Glad I have that backup paranoia ingrained. I do thank you both for responding.While we are readinging this, are there any tutorials on how to set zones and patrol paths?
I hate to use one thread to segue to another, but why waste the page?
Pascal05
-
I don’t think there is any “un-needed info”, since the tool generates hash codes only from your installed FL version (mod).
Anyway, since you got what you needed, all is OK.
-
If FLSpit is showing an error saying it’s missing, then you will never find it…you didn’t mention what it said so just guessing.
-
Thanks for responding,
The message;
ERROR: ArchDB::Get(0xaae40e4b) failed. ID=-1427894709
WARNING: Failed to preload archetype ship = o_osirisis what is showing. THis was part of my project to add a nodock Osiris to my mod.
I have stripped everythig from my systems ini file and this still appears.
None of the hashes are related except o_osiris, which in no longer anywhere to be referaanced. I used FL Hash to predict the visit hashed (all confirmed). I used FL Scan and Fl Scan II as well as DB_Hash_CRC_Calc and its new beta version. Prognosis: I may have to delete even more stuff to get to the bottom of this. I decided to take a break for a couple days, before obsession becomes something worse.
I tried to get a program from EOM, but the link is dead. The Mod Tools program is FlHDB – find the strings belonging to those hashes! Probably long gone. But I have learned quite a lot about FreeLancer’s hashes and those pesky visit definitions. I would probably be better off if I possed progamming skills, instaed of engineering technology skills.
If you have any ideas let me know. Thanks again for responding.
Pascal05
-
Thanks for responding,
The message;
ERROR: ArchDB::Get(0xaae40e4b) failed. ID=-1427894709
WARNING: Failed to preload archetype ship = o_osirisis what is showing. THis was part of my project to add a nodock Osiris to my mod.
I have stripped everythig from my systems ini file and this still appears.
None of the hashes are related except o_osiris, which in no longer anywhere to be referaanced. I used FL Hash to predict the visit hashed (all confirmed). I used FL Scan and Fl Scan II as well as DB_Hash_CRC_Calc and its new beta version. Prognosis: I may have to delete even more stuff to get to the bottom of this. I decided to take a break for a couple days, before obsession becomes something worse.
I tried to get a program from EOM, but the link is dead. The Mod Tools program is FlHDB – find the strings belonging to those hashes! Probably long gone. But I have learned quite a lot about FreeLancer’s hashes and those pesky visit definitions. I would probably be better off if I possed progamming skills, instaed of engineering technology skills.
If you have any ideas let me know. Thanks again for responding.
Pascal05
-
So you already found the missing object, it is o_osiris
But it is being requested somewhere in the mission files.
So you need to find where it is requested, and delete that.
Or put o_osiris back in.
Or did I misunderstand completely?
-
Hey,
Actually, the answer is yes. It was only entered into the system and solararch ini files. It is all that is required to add such objects. With the entries deleted, it should not be showing up. The FreeLancer folder has no undeleted files which occasionally FLMM does. I have checked my FLMM mod folder also. When I have finished “walking away” for a while, I will probably replace the FL directory and my mod ini files, just to be sure.
The thing that is iritating is that if I do a search within files the o_osiris only shows up in the shipsarch file in the actual or_osiris battleship collision_group (s) fuse = .
As you can see, this is perplexing and when I get back to it I will report as to what worked. I will make replacements one at a time to verify the problems location.
HOLD ON!
I had an idea and quickly did this;
In the {archetype} section I had ship = o_osiris
I had forgotten about it as most times it seems to be ignored when the game runs. It is eliminated.Odd thing though, whatever crashes the launch is not showing in spit, only the mp3 referances which I never bothered to add the Adoxa patch. Directions are too fuzzy.
So I will end this thread, aside from any additional vcomments anyone has on the subject, and move on.
Pascal05
-
Regarding the MP3 fix. Extract MP3codec.dll from MP3codec.zip, placing it in your EXE directory. Edit EXE\dacom.ini and you’ll see [Libraries]. Go down to the bottom of that list and add MP3codec.dll. Save, done.
... ximage.dll .\flmaterials.dll MP3codec.dll ;;EMAURER ... -
Good-oh!
