Custom Ships cause CTD when taking a mission

addon = sw_s_scanner_03, internal, 1

This is not vanilla, does it exist and work?

addon = blue135, internal, 1

I assume this is the engine? Or a shield? It needs one of each

The easiest way to test things like this is to substitute in vanilla parts. This would troubleshoot away half the equation.

Yep, it is missing a shield (probably a CTD in itself)

Also, Lancer Solurus’s Error Checker to the rescue:

http://digitalbrilliance.com/Downloader/index.php?action=downloads&id=1 (register before you can see it)

-> Missing ‘hppilot’ on ‘coralskipper2’ *** E:\Freelancer\DATA\ships\swships\yv_coralskipper\coralskipper2.cmp
-> Missing ‘hpbaydoor01’ on ‘coralskipper2’ *** E:\Freelancer\DATA\ships\swships\yv_coralskipper\coralskipper2.cmp
-> Missing ‘hpbaydoor02’ on ‘coralskipper2’ *** E:\Freelancer\DATA\ships\swships\yv_coralskipper\coralskipper2.cmp
-> Missing ‘hptractor_source’ on ‘coralskipper2’ *** E:\Freelancer\DATA\ships\swships\yv_coralskipper\coralskipper2.cmp

I think it MUST have the tractor hardpoint as well or CTD
You can comment out or delete the first 3

My time is up for now but here are some more hints…

ship_class = 1
and
msg_id_prefix = gcs_refer_shiparch_hfighter
both indicate that you want this to be a heavy fighter

but

hp_type = hp_freighter_shield_special_4, HpShield01
hp_type = hp_freighter_shield_special_3, HpShield01
hp_type = hp_freighter_shield_special_2, HpShield01
hp_type = hp_freighter_shield_special_1, HpShield01

are mounting freighter shields on a heavy fighter. Pick which you want and make it match in all 3 locations.

HP_tractor_source = HpTractor_Source
should read
HP_tractor_source = HpTractor_Source01
to match the hardpoints in the cmp

Good luck, this should get you started. For goods.ini copy the stuff from li_elite if going the heavy fighter route and continue troubleshooting.

**A missing HP_Tractor is one of those random crashes I experienced many times. If the ship has a tractor beam installed without the hardpoint, it will randomly crash when the player is beaming something in. Also, something that FLEC does not test for is the baydoor hardpoint, if both are set to the exact same position, you will get a crash when jettisoning any cargo and I mean a server crash, not just the client. This can’t be used as a method of crashing the server (sorry cheaters) if the server side ship CMPs are fixed, it will simply crash the client only if they change the hardpoint positions. This is fully verified after losing half of my hair by pulling it out

BTW, don’t rely on the HP test that FLEC has, it is for NPC’s only, not the players as OP has told me more than once. (thanks OP for the clarification). I use the exact same loadout for NPCs and players in my MOD so it worked fine for me, it’s just that all of the other MODs dont do loadouts the way I did…**

@KarrMcDebt:

Thanks for the Tips,

I’ll be working on the ships this weekend and I’ll check all this out. I also have a line out to Sushi since he works with the same base TC mod, he may have some ideas as well.

Once I isolate the problem (if I can, sometimes they remain unfound even after the problem is fixed) I will update the thread with the results.

Thanks so much.

Karr

Sadly, Karr, I don’t work on FW 1.66 base anymore. I haven’t touched that code, in significant amounts, since I started working on FW:ToW. The amount of errors it has accumulated over the years is staggering and I wouldn’t even know where to begin to bug fix if I wanted to. You’ll also note that the 18.45 version of FWs runs without missions, because they’re so many bugs with missions in general. Personally, I think you’d be better off starting from scratch and I think, in the long run, it will save you a lot of frustration.

Anyways, back on topic here, I do not know about what is crashing it. It could be so many different things.

Best of luck, Kerr. As they say over at FWs….“May the Force be with you.”

Personally I’d take Sushi’s advice and start from scratch.

I had a quick run around with 1.66 earlier and the amount of errors being generated in FlSpew is horrendous, why these were never addressed before release is beyond me ???.

and before anybody shouts out ;D they’re not voice errors

18.2f is not stable, Karr. It has a multitude of NPC errors that cause spontaneous crashing of the server. However, kudos to you for keeping that mod alive!

1.65 is actually pretty good in terms of stability. It’s just very outdated in a lot of aspects.

FlSpew.txt is FL’s Client error log and can be found in (XP) “C:\Documents and Settings<username>\Local Settings\Application Data\Freelancer”.
Both Local Settings & Application Data folders are hidden folders so you will need to change your folder settings to see them, or you can use FlSpit which is a small script that locates & translates the FlSpew into something a little more understandable :P.

Edited to add the link to FlSpit</username>