wplatform = 3098097218

Hey Chips .... how can I work these equip / location ID's out for myself .... I'm trying to debug errors in FL Server Errors.log by my LAN server.

TIA

White,

this error occurs when you take 'destroy bases' missions.. and while its annoying.. it gratifying in a way to see that it is not isolated to our mod alone.. lol

We have been able to track some stuff down and isolate the offender but believe its a native freelancer error, that occurs as the weapons platform is created by freelancer at somewhere between 5 - 10 k's out. This weapons platform (the extended 'x' form) is of a type commonly used in freelancer and encounters. In our case it was a mission in Tau from the Outcasts against Bounty Hunters..

a sample loadout looks something like this:

archetype = wplatform
loadout = weapon_platform_co_03
hitpoints = 999, 1600
difficulty = 0.426316, 1.093571
pilot_choices = 4

The loadout can be found in the loadouts/ini in the Solar folder:

[Loadout
nickname = weapon_platform_co_03
archetype = wplatform
equip = infinite_power
equip = ge_s_scanner_02
equip = SlowLargeYellow, HpRunningLight01
equip = SlowLargeRed, HpRunningLight02
equip = SlowLargeRed, HpRunningLight03
equip = SlowLargeRed, HpRunningLight04
equip = SlowLargeYellow, HpRunningLight05
equip = SlowLargeRed, HpRunningLight06
equip = SlowLargeRed, HpRunningLight07
equip = SlowLargeRed, HpRunningLight08
equip = SlowLargeRed, HpRunningLight09
equip = SlowLargeRed, HpRunningLight10
equip = co_wp_turret01_mark03, HpTurret01
equip = co_wp_turret02_mark03, HpTurret02
equip = co_wp_turret01_mark03, HpTurret03
equip = co_wp_turret02_mark03, HpTurret04
equip = armor_scale_13
equip = weapon_platform_tower1
equip = weapon_platform_tower2
equip = weapon_platform_radar1
equip = weapon_platform_radar2


Now despite commenting out all the loadout, the problem does not go away even when you are left only with the .cmp reference, yet the .cmp is the same as is used for normal freelancer weapons platforms that occur around many bases and do NOT throw an error.

If you find out what this is and what causes the problem and how to cure it.. PLEASE post.. lol.. as I think that it is common to many mods.

There is a hashcode database on here somewhere.. you will need to search.. However, anything you make that is new .. i.e. weapons etc.. will have an identity assigned to it by freelancer and will not appear in the database.. you must add your own items, (i.e. stuff you make), yourself

Also if there is known cure for this please can someone post the solution..

Harrier
Harrier


Edited by - harrier on 4/3/2005 11:33:29 PM

Hey Harrier - this was posted some time back - it was found out by Wasabe (thanks or the memory Anton )

However, take all missions items entries like these, copy them from the soloarch.ini file and then paste them to the end of your shiparch.ini file instead.

Edited by - Chips on 4/4/2005 2:57:17 AM

That was Wasabe

Thankyou gentlemen, at least i know what it is now.

Edited by - White on 4/4/2005 1:18:22 PM

hehe, I still remember that fondly, it was my first real contribution to Lancer's community. =)

Chips, Anton, Wasabe,

Many thanks, .. you know...I did a search for this but found nothing, and had I known I could have spent the 3 days fiddling about with this on something else.. oh well....lol
Thank you very much for the answer - it may allow us to create custom weapons platforms that can be created with new .cmp files..

It comes to my mind that a stickied thread devoted to these flspew and fl-server-error logs could be beneficial and save many similar posts... I started one some time ago.. but it has slipped down some since..and given the wealth of knowledge available here it could save the timeneed for trolling through a million posts.

Any thoughts on this??

Harrier.

I think Harrier has a very good point.

When your trying to clean up the mod, it would be very useful to have the errors stickied or have a sub forum for them.

The answers tend to be more complicated and sometimes longer to resolve and usually generate a good discussion or lead to other flspew issues.

A sub forum would be great. With sticky threads for any major (type of) error.

Well the thing is, that wouldn't really help too much. I mean, most or all modders are using the SDK1.3 or 1.4, and those two things fix ALL the server errors. I think 1.4 even includes the fix for the mission solars (not entirely sure acutally). So, every other error that is displayed in the flserver console is because of modding, and of course every mod is different. If people happen to use existing names of equipment, then it may help, but there is always the existing hash code lists. But if someone creates a piece of equipment called "mycustomequipment", it will create a unique hashcode for that mod. Just knowing that hashcode does no good at all unless you also know the name of the equipment, and only the maker of that particular mod would know.

There are some though... the 'head 0' error introduced by FLExplorer for instance. Perhaps it could be combined with a 'this is impossible so don't ask' thread

"Cant find item on client request" the npc usage of nans and bots caused when they die.

These are the things I was thinking of, not the basic stuff that a hashcode and lookup will solve

Ah... that's what it is! lol Cheers Alan, that ones been irritating me