Ehrm whats that?^^

*** WARNING: alloc_equip: Archetype[0x8000bec6] not supported/equippable!

What this basically means is that you’ve stuck a piece of equipment into the loadout of something that shouldn’t get it. Engines, Scanners, Powerplant and Tractor beams will all cause this error if added to the wrong object, Bases don’t get engines or tractor beams, Non-dockables don’t get engines and wrecks don’t get any of the 4.

@M.o.D.:

…
Where can i find the clientside error logs??

In C:\Documents and Settings<your user=“”>\Local Settings\Application Data\Freelancer
Use FLSpit to read client side error logs.</your>

**Well I found a few things, Im at work now so I can’t look at the list. You have a torpedo 3 mount which doesnt exist in FL.

I was attempting to start up the FL exe but I had to kill it when it attempted to start something in my Temp folder, a definate no-no, usually attempted by viruses.

Also, you had alot of missing entries for IDS and quite a few that were out of range, this usually doesnt cause crashing though.

All of this I found using FLEC…**

What is the dll used for (capital_mod.dll (sp?)) ?

send us a link m8… ;D

Can’t promise I’ll find anything that lancer hasn’t already but i am pretty good at squishing
bugs under my boot… lol… & considering it may or may have not been the code i sent u that did this…
I feel somewhat responsible for trying to kill this one for ye

Cheers.

I just remembered, I ran into this exact same problem when I attempted to do this the first time. It turned out that I had to create new nicknames and shiparch entries for the capital ships before they worked properly. I never could get it to work right until I did that…(you already did the second part)

Codebase and .cmps i gave M.o.D. are largley “untested” LS…
well they were tested about a year ago… lol… but not since… could be i muffed up
a param over the past year playing with other stuff… or just slipped somewhere
at the end of a long night… also i updated my Shiparch soon after sending the pak…
so cross referencing is now pointless…

The engine in particular could even have a XLR FX ref in it??.. pointing to a FX
that isn’t in vanilla… so im curios now… hehe…

I really need to update and release that ship scripter so adding ships is simply a few clicks…

Hmm… on first glance… try adding the engine to the engine goods as well??..

Not shure if the anticheat tech might flag a item without a good entry as bad… but its a good
idea to add them all in … for priceing anyways… lol…

I cant so far see anything else wrong though…

I checked ths engine type in the vanilla engine_equip.ini:

[Engine]
nickname = ge_lb_engine_01
ids_name = 263888
ids_info = 264888
volume = 400.000000
mass = 10
max_force = 3000000
linear_drag = 100000
reverse_fraction = 0.100000
flame_effect = gf_li_largeengine02
cruise_charge_time = 5
cruise_power_usage = 20
rumble_sound = rumble_battleship
indestructible = false
outside_cone_attenuation = -3
inside_sound_cone = 90
outside_sound_cone = 270

That “mass” in your file equale 0. I saw through this .ini and no engine has mass = 0. Maybe thats the wrong.

If you just removed the engine from the battleship station’s loadout, which should not have an engine, then this error would have disappeared.

It was mentioned thrice in this thread, but ignored.