Fixing errors found by FL Error Checker

DwnUndr

Did I ever tell you that you rock?! ;D

The UnderVerse currently has zero errors from all the checkers including your 009 FLEC. But one problem still shows in flspew related to atc_leg_f01a voice (from many vanilla systems and mine too since it is there as well):

WARNING: invalid MSG id (2147483648) for voice profile (0xb02cfbc0)
–-------------------------------------------------

The following is probably already fixed in your next release (where is it! hehe)

System ‘E:\Freelancer\DATA\UNIVERSE\SYSTEMS\LI01\li01.ini’

Line 470 : Encounter ‘area_trade_transport’ : Total 1.000
Line 549 : Encounter ‘area_trade_transport’ : Total 1.000
Line 775 : Encounter ‘area_trade_transport’ : Total 1.000
Line 1126 : Encounter ‘tradelane_trade_transport’ : Total 1.000
Line 2320 : Encounter ‘tradelane_trade_transport’ : Total 1.000
Line 2832 : Encounter ‘tradelane_trade_transport’ : Total 1.000

etc…

Found 10 encounters not equaling 1.0

Keep up the good work!

LancerSolurus

**Thanks!

I will see about the voice error. I’ve already done a CRC decompile on the fl exe so I will see if I can find it.

The encounters bug has already been fixed and I also added in an extended version of the encounter check, thanks to Star Trader for pointing out to way encounters work.

Look for the latest version to be released in the next few days here.**

DwnUndr

Found a second invalid ID. Here is more info about the first and some about the second:

WARNING: invalid MSG id (2147483648) for voice profile (0xb4902287)

atc_leg_m01
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\RH01\Rh01.ini)
atc_leg_m01
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI04\Li04.ini)
etc….

atc_leg_m01
(E:\Freelancer\Data\MISSIONS\M12\m12.ini)
atc_leg_m01
(E:\Freelancer\Data\MISSIONS\voice_properties.ini)
atc_leg_m01
(E:\Freelancer\Data\AUDIO\voices_space_male.ini)

WARNING: invalid MSG id (2147483648) for voice profile (0xb02cfbc0)
WARNING: invalid MSG id (2928013708) for voice profile (0xb02cfbc0)

atc_leg_f01a
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI04\Li04.ini)
atc_leg_f01a
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI03\Li03.ini)
atc_leg_f01a
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI02\Li02.ini)
atc_leg_f01a
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI02\Li02.ini)
atc_leg_f01a
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI02\Li02.ini)
atc_leg_f01a
(E:\Freelancer\Data\UNIVERSE\SYSTEMS\LI01\li01.ini)
etc…

atc_leg_f01a
(E:\Freelancer\Data\MISSIONS\voice_properties.ini)
atc_leg_f01a
(E:\Freelancer\Data\AUDIO\voices_space_female.ini)

Bejaymac

WARNING: invalid MSG id

How many custom factions, systems & bases do you have, as this error is usually caused by using a “msg_id_prefix” that doesn’t exist in the UTF files ie “msg_id_prefix = gcs_refer_faction_da_x”, only two ways to fix this, use existing entries for your custom content, or make brand new sound files for them and add them to the UTF & INI files.

LancerSolurus

**Those errors are not checked for. The systems aren’t scanned due to that they use the permutation stuff in them and I haven’t added a scanner for it yet. So unfortunately you won’t get anything flagged for a bad sound file in the systems or missions folders.

Orginally it did scan those systems but the error count was quite high, most of them were due to permutations that the NPCs use to speak to you out in space.**

DwnUndr

@Bejaymac:

WARNING: invalid MSG id

How many custom factions, systems & bases do you have, as this error is usually caused by using a “msg_id_prefix” that doesn’t exist in the UTF files ie “msg_id_prefix = gcs_refer_faction_da_x”, only two ways to fix this, use existing entries for your custom content, or make brand new sound files for them and add them to the UTF & INI files.

72 new factions, 108 new systems, 450 new bases. However, all of those errors also exist in the vanilla systems (not used or edited in my mod). Since they also carried over into my mod, they must relate to something in common with both. I have not placed npcs in space yet, so it is not them.

Interesting about the msg_id_prefix. I had one of these show up on a custom commodity (150 or so of these). FLEC flagged it so I could fix it.

LancerSolurus

The commodities are scanned for errors, so are all of your ships.

LancerSolurus

**For those of you who hate hunting down the loadout errors on the player’s ships, check out the latest version of my error checker and finally fix all of those pesky bad hardpoint references.

Click here to get the latest version**

DwnUndr

Great job again! New errors found:

ship goods “addons”…168 FIXED

Nicknames
Pilot_population
Pilots_story
SoundCFG…51 errors FIXED

All went away except the two pilots ones. Some showed the error even though they were already capitalized, they all still show after fixing (although it may not be possible for the checker to tell if they are capitalized?) If so, maybe those could be converted to warnings rather than errors.

Thanks for the hard work!

LancerSolurus

Actually it should be able to tell, I have a flag setup to turn the lowercase conversion on and off. Most likely I didn’t set it properly.

Tunicle

Hi just checking I am reading the error checker correctly, as an example

encounter = tradelane_trade_freighter, 4, 0.200000
faction = co_be_grp, 0.290000
faction = br_m_grp, 0.290000
faction = co_nws_grp, 0.290000
faction = gd_im_grp, 0.140000

The first line is ok and is the chance of an encounter happening?
But the 4 faction lines need to ideally add up to 1 (at present 1.01)?

Thank you in advance

LancerSolurus

**Actually this feature has been requested by several users. In my opinion I don’t believe it matters since I have some that reach 30 and higher for the encounters and 50+ on the faction stuff. And they still work.

I use the NoCD exe so maybe that is why it works fine, who knows. Even the vanilla files have stuff that doesn’t add up to 1.0. I have also heard that they work better if they are set up to use 1.0 as the final value. I really don’t know so if someone can show me proof that this is the true way it works I will leave it as an error, as it stands now I am switching it to be simply a notice.

I will also be releasing a fixed version of FLEC later today, it turned out to be a single missing letter that was causing it not to work. I was using the string that was being knocked to lowercase rather than the string that was saved right before that was done.**

mknote

I got this error while running FLEC:

C:\Program Files\Microsoft Games\Freelancer\DATA\SHIPS\shiparch.ini
Line #5775 ==> “type = engine”
[> * Nickname not found * ‘engine’
Line #6418 ==> “type = bottom_engine”
[> * Nickname not found * ‘bottom_engine’

All well and good, but this is wrong. These two particular nicknames aren’t used anywhere in-game, but they are valid. A full list of valid ‘type =’ can be found in common.dll (don’t know the offset, but just search for ‘bottom’ and you’ll find it easily). All of the unused ones relate to engines, I think. At any rate, I use this to bypass the fact that part names are hardcoded. These particular ones allow me to show ‘Lower Wing’ and ‘Lower Arm,’ respectively.

I noted two other errors. The first was the aforementioned encounter error, in which my encounter adds up to 1 but FLEC says it doesn’t (actually, it says it does but it comes up as an error anyway). I’m using the now latest, v1.011, so you’ve missed something.

The other error dealt with ALE CRCs. The CRC I had worked (it came from your more advanced CRC calculator), but it gave me another CRC to put in instead. Both CRCs work, so I don’t know what’s going on…

@Lancer:

I’ve already done a CRC decompile on the fl exe

It might not relate to FL Error Checker, but this could be very useful. What exactly do you mean by this? Does this mean that you can tell which part of the EXE loads a certain part of a code at a given time? If so, I have a particular request…

LancerSolurus

**Looks like I forgot to include all of the engine types, added.

Could you post the encounters that didn’t add up?

Also could you post the nickname you got the CRC from?

Both will work, but to follow the format that DA set up, it should match the CRC of the name of the root fx in the .ael file. It isn’t a requirement to do so.**

mknote

I found two such encounter errors:

System ‘C:\Program Files\Microsoft Games\Freelancer\DATA\UNIVERSE\SYSTEMS\KU03\ku03.ini’
…
Line 1409 : Encounter - area_trade_transport : Total 1.000

and

System ‘C:\Program Files\Microsoft Games\Freelancer\DATA\UNIVERSE\SYSTEMS\RH04\rh04.ini’
…
Line 1103 : Encounter - area_trade_transport : Total 1.000

Note that these come from my mod, though the encounters in question I hadn’t touched… Still, the offset may be different in Vanilla files.

As for the CRCs, well, as you said, either one works. Still, here are the pertinent files (note that this came from v1.009; I’d ‘fixed’ it when I ran 1.011):

C:\Program Files\Microsoft Games\Freelancer\DATA\FX\ENGINES\engines_ale.ini
Line #767 ==> “effect_crc = 3767204598”
[> Effect CRC incorrect * ‘3767204598’ should be ‘-527762698’ for ‘gf_hi_smallengine01’.
Line #774 ==> “effect_crc = -4174435795”
[> Effect CRC incorrect * ‘-4174435795’ should be ‘120531501’ for ‘gf_hi_smallengine01_fire’.
Line #780 ==> “effect_crc = 4233519957”
[> Effect CRC incorrect * ‘4233519957’ should be ‘-61447339’ for ‘gf_hi_smallengine01_trail’.
Line #788 ==> “effect_crc = -3801310230”
[> Effect CRC incorrect * ‘-3801310230’ should be ‘493657066’ for ‘gf_hi_smallengine01_playtrail’.

C:\Program Files\Microsoft Games\Freelancer\DATA\FX\MISC\misc_ale.ini
Line #2599 ==> “effect_crc = -3773449273”
[*> Effect CRC incorrect * ‘-3773449273’ should be ‘521518023’ for ‘rtc_li06_sun’.

C:\Program Files\Microsoft Games\Freelancer\DATA\FX\SPACE\space_ale.ini
Line #258 ==> “effect_crc = -497059510”
[*> Effect CRC incorrect * ‘-497059510’ should be ‘89811715’ for ‘gf_wormhole_blue’.

C:\Program Files\Microsoft Games\Freelancer\DATA\FX\WEAPONS\weapons_ale.ini
Line #4947 ==> “effect_crc = -13814110”
[> Effect CRC incorrect * ‘-13814110’ should be ‘-490760753’ for ‘ha_gun01_flash’.
Line #4956 ==> “effect_crc = -316752254”
[> Effect CRC incorrect * ‘-316752254’ should be ‘426367732’ for ‘ha_gun01_proj’.
Line #4965 ==> “effect_crc = -297874727”
[*> Effect CRC incorrect * ‘-297874727’ should be ‘-350206561’ for ‘ha_gun01_impact’.

By the way, this tool is a Godsend. It weeded out errors I would never have found. Great work!

MK

edit

What about the last part of my previous post?

LancerSolurus

**Ok for
‘gf_hi_smallengine01’ = -527762698
‘gf_hi_smallengine01_fire’ = 120531501
‘gf_hi_smallengine01_trail’ = -61447339

Hehe, see the trend…I used my CRC calculator for those, not FLEC. I would assume the most likely culprit if the apostrophe ( ’ ). I found after switching to all HTML that when I tried to copy the name it would select the apostrophe at the start and/or end of the name. You may not have noticed but I have stopped adding those into later checks. I really like having them because it makes them stand out a little bit from the whole error. If I find a way around this problem I will start using them again. I will have to remove them soon though.

If you think this version is a godsend, wait till you see the number of hardpoint errors that will be showing up in the next version. With the recent spate of crashes it turned out to be because of the HPBayDoor hardpoints. If they are positioned in the same location, boom, server crash when jettisoning. If they are missing the cargo sometimes disappears or it will appear dead center in the middle of the ship, flipping me about wildly. I was unable to check for the positioning problem due to the way FLEC read UTF files (it only yanks out the HP names), but I was able to check for missing hardpoints. I just got through adding almost 400 hardpoints to my ships and fixing alot more for the duplicate positioning crash. BTW, thanks F!R for pointing out that crash!

Oh, could you post the complete encounters, I need to duplicate your error.**

mknote

Ah, well, here they are (they may be in Vanilla FL); I’ll bold the particular offender

[zone]
nickname = zone_ku03_pop_tsuchima
pos = -28582, 0, -40007
shape = SPHERE
size = 4000
comment = Tsuchima
sort = 4
toughness = 8
density = 9
repop_time = 10
max_battle_size = 6
pop_type = co_shi_grp, single_base_law
relief_time = 20
faction_weight = co_be_grp, 10
faction_weight = co_kt_grp, 10
faction_weight = co_nws_grp, 10
faction_weight = co_shi_grp, 5
faction_weight = co_gs_grp, 5
density_restriction = 4, unlawfuls
encounter = area_defend, 8, 0.1
faction = co_shi_grp, 1
encounter = area_trade_freighter, 8, 0.1
faction = co_shi_grp, 0.4
faction = co_kt_grp, 0.4
faction = co_gs_grp, 0.2
encounter = area_trade_transport, 8, 0.1
faction = co_kt_grp, 0.26
faction = co_shi_grp, 0.26
faction = co_nws_grp, 0.16
faction = co_be_grp, 0.16
faction = co_gs_grp, 0.16
encounter = area_lifter, 8, 0.1
faction = co_shi_grp, 1
encounter = area_repair, 8, 0.1
faction = co_shi_grp, 1

[zone]
nickname = zone_rh04_pop_holdstein
pos = -8230, 0, -29569
shape = SPHERE
size = 4000
comment = Holdstein
sort = 6
toughness = 10
density = 9
repop_time = 10
max_battle_size = 6
pop_type = co_khc_grp, single_base_law
relief_time = 20
faction_weight = co_alg_grp, 10
faction_weight = co_khc_grp, 7
faction_weight = co_kt_grp, 10
faction_weight = co_rs_grp, 10
faction_weight = co_shi_grp, 10
density_restriction = 4, unlawfuls
encounter = area_defend, 10, 0.05
faction = co_khc_grp, 1
encounter = area_trade_freighter, 10, 0.15
faction = co_alg_grp, 0.37
faction = co_khc_grp, 0.26
faction = co_rs_grp, 0.37
encounter = area_trade_transport, 10, 0.13
faction = co_alg_grp, 0.21
faction = co_khc_grp, 0.16
faction = co_kt_grp, 0.21
faction = co_rs_grp, 0.21
faction = co_shi_grp, 0.21
encounter = area_trade_armored, 10, 0.02
faction = co_khc_grp, 1

While we’re on the subject of errors, however, I’ve just remembered one I encountered in 06-07 that held up my second mod. It occured when I had two destroy_vignette zones with the exact same position. Whenever I did that (I think there were other conditions, but I’ll need to dig through emails to find out), a base that used the zones to generate missions would freeze whenever I tried to load it. I’ve not heard of the error since, but I thought it might be something to point out.

MK

LancerSolurus

**I see, that does add up to exactly 1.0. Dealing with floats can be a little finiky with the round-off errors getting in the way. I will reduce it to a 3 digit decimal check (.000) to avoid that non-error being flagged.

Thanks for the tip on the zone, I also found out yesterday that the Y axis is ignored in vignette zones. I have been contemplating adding in a system scruber sort-of routine. This routine would go in and check every last detail in a system to make sure it was right. My favorite is the missing enocounter crashing the server when entering a system.**

LancerSolurus

**Here is that hash list you were asking about, it is just list of hashes from the fl.exe used to get the audio hashes.

Download here**

JONG

@Lancer:

**Here is that hash list you were asking about, it is just list of hashes from the fl.exe used to get the audio hashes.

Download here**

Thanks LS, your are the one !