Crashes in Edinburgh

Sat Aug 05, 2006 11:13 am by Igiss

Since last summer when I released first version of Discovery, I've several times experienced (and got occasional reports about) client and server crashing in one specific place - Edinburgh system, between Perth base and nearby asteroid miner. As I'm now working on next Discovery version, I decided to finally fix this thing (although it doesn't happen all the time, and few people ever visit this place).

I didn't introduce anything new into this system, except for a jump hole into Dublin. I've removed jump hole, and removed the asteroid miner (since I edited solararch.ini), however, the problem persisted.

Then I started to look through encounters and patrols, which I didn't add or modify. After some trial&error I was able to track the reason of crashes - patrol called Zone_Br06_path_planetform2_1 between Perth and roid_miner.

Here's its code (taken from SDK 1.5, though it doesn't really matter cause they all SDKs are identical about this, and my mod had the same):

[zone
nickname = Zone_Br06_path_planetform2_1
pos = 17675, 0, 10723
rotate = -90, -68, 0
shape = CYLINDER
size = 750, 5154
property_flags = 131072
sort = 96
toughness = 6
density = 5
repop_time = 30
max_battle_size = 4
pop_type = mining_path
relief_time = 20
path_label = planetform2, 1
usage = trade
mission_eligible = true
faction_weight = co_ti_grp, 10
density_restriction = 1, patroller
density_restriction = 1, police_patroller
density_restriction = 1, pirate_patroller
density_restriction = 4, unlawfuls
encounter = miningp_trade_transport, 6, 0.330000
faction = co_ti_grp, 1.000000

There wasn't a single crash after removing this section.

I wonder if anyone has ever encountered similar problem and what might be causing it... is it specific to my mod (for some mysterious reason) or a known problem of original FL? If latter, then why is it in SDK?

Sat Aug 05, 2006 12:39 pm by Cold_Void

its the 1.5 SDK - don't ask me why(I didn't assemble it) but its got more fatal errors in system/encounters than the 1.3 SDK.

the edinburgh crash is only one of many errors i eventually eliminated from my own mod by switching out the 1.5 SDK system/encounter files with the classic 1.3 SDK files

Sat Aug 05, 2006 1:18 pm by Igiss

That's strange. Br06 (Edinburgh) files in 1.3 and 1.5 are identical. Moreover, it's obviously not only 1.5 mistake, cause my initial system files were from 1.4 unofficial patch. The error was there too.

Which raises a question - what file(s) are responsible for this?

I've made a full comparison of SDK 1.3 and 1.5 files via CSDiff... and generated a report that's viewable here:
http://cyrodiil.net/fl/report.htm
There are not so many changed files, and most changes are minor. So, if you could give me clue what should be replaced with 1.3 originals, I'd be most grateful.

Sat Aug 05, 2006 1:35 pm by Cold_Void

swap the 1.5 system file and encounters, that should fix edinburgh
- if i knew how to find the actual problem-difference i would say 'here it is' - but since i absolutely HATE debugging zones and encounters, i took the lazy way out and it worked. As much of the 1.5 system and encounter files should be replaced as possible - for me this meant going in and restoring a bunch of solararch's and loadouts i had changed

the morale of the story: SDK 1.5 is the devil!

Sat Aug 05, 2006 3:09 pm by Igiss

I just don't understand how is it possible. 1.4 unofficial patch, SDK 1.5 contain some encounter bug that no one knows about?

So, here's a brief summary of 1.3 and 1.5 differences.

----

universe.ini:

changes/adds several BGCS_base_run_by = entries. Including those for miners. Maybe that's it?

solararch.ini

nickname = surprise_superconductors:
changed shape_name = NAV_surpriseX
to shape_name = NAV_lootabledepot
nickname = depot_construction_machinery:
changed shape_name = NNM_SM_COMMUNICATIONS
to shape_name = NAV_lootabledepot

npcships.ini

nickname = br_n_destroyer_d22, nickname = br_n_battleship_d25:
pilot = destroyer_default
changed to
pilot = cruiser_default

concave.ini

part = Commodity fore01 changed to Commodity_fore01

petalDB.ini

prop = barrel Van_Claussen changed to barrel_Van_Claussen
prop = Cocktail Glass changed to Cocktail_Glass

fuse_surprise_solar.ini

hardpoint = HpWeapon0
changed to
hardpoint = HpWeapon06

formations.ini

nickname = juni_m04: pos = 0, 0, 0,
last comma removed

----

loadouts_utility.ini:

1.5 removes a couple of tractor entries and engine entries (miner, liner)

loadouts_special.ini:

1.5 again removes several tractor and engine entries from battleships.

ships/loadouts.ini

cargo = fc_ou_gun01_mark03_ammo, 8
removed
cargo = fc_bd_gun01_mark02_ammo, 20
removed twice

solar/loadouts.ini

equip = mining_ship_engine_sound,
removed comma in the end 5 times

----

All other files that are different include:
SP mission files
Files for specific systems (NOT including Br06)
Files for specific nebulas/asteroid fields (again NOT including Br06)
Cockpit files
A few base and cityscape files
navbar.ini
cameras.ini
I assume those won't influence encounters in any way.

Sat Aug 05, 2006 4:30 pm by Bejaymac

There's one in Hi01 as well that catches me from time to time, it happens with vanilla, SDK 1.3 & SDK 1.5, so it's not something LD and the gang at EOA have done. One of these days I'll back track it but I'm not looking forward to checking the npcships.ini, loadouts.ini, shiparch.ini, faction_props.ini and most of the files in the Equipment folder looking for a typo.

**shuffles of with a new headache**

Mon Aug 07, 2006 3:58 am by Igiss

So, no one else could help about that? I was hoping for some feedback from those familiar with SDKs, including its creator, Louva-Deus. I guess this issue is important enough to get it fixed somehow. Or at least let modders know how to fix it, what files to check etc.

Or am I wrong?

Btw where in Hi01 the problem occurs (so that I could test that place too)?

Sun Aug 13, 2006 6:47 am by Louva-Deus

I can't fix problems nobody reports. All bug reports have to come to me via the contact form on the =EOA= website, not in threads on Lancer's Reactor. I will add this to the list of things to look at.

Important Message

You are browsing the archived Lancers Reactor forums. You cannot register or login.
The content may be outdated and links may not be functional.

To get the latest in Freelancer news, mods, modding and downloads, go to
The-Starport