Hmmm...
The "Get_Zone" errors appear to be unrelated to the mission crashes.
I've noticed that they only appear upon visiting a base.
I'll report findings as I get them.

Watch your 6!

I would guess that the problem is in one of your asteroid or nebula files. It refers to a zone that is not in your system file.

At the top of your system ini file, find all the asteroid and nebula refrences. Open the files they reference and look for any mention of zones in those files. Then look back in that system ini file and make sure they are all there.

If you want to find which zones are causing this, turn up the logging in freelancer.ini all the way up. So it shows everything. It helps alot.

OK... there are several types of Zones:

1. Normal ol' Encounter Zones.
2. Asteroid Zones.
3. Patrols (they're really just a cylinderical Zone type... if you don't believe me, I'll do a proof for you)
4. Vignette Zones (open, destroy, etc.)
5. Wormholes and Gates

I've worked with Encounter Zones a lot, and you can specify them in all sorts of ways without causing errors- they can be spheres, ellipsoids or cylinders, and they'll work just fine. They can also combine a lot of attributes in the same Zone, without causing errors.

All of these can cause problems with things "not showing up", but it's the Wormholes and Gates that can cause CTD or FLServer crashes- and if a Zone is associated with a Base, then it can cause issues too- after all, these Zones have to have ways to "know" that they're near a Base, so that ships will go through docking routines.

The Zones around Wormholes and Gates aren't just used to spawn Encounters there... they're also being used to determine where players enter/leave the System, apparantly. So you can really screw things up by removing them... for example, it's quite possible (and bug-free) to build "one-way trips" through Wormholes and Gates... simply build the Gate, build the appropriate type of Zone... and build another location in the next System, but without a Gate for the player to interact with. It's the Zone that matters, not the Gate, apparantly.

One of the primary reasons why I moved my mod out of NY and into a new, custom System was that various problems with the Zones there turned into a mess, affecting server stability. I built a whole new System which I populated, named etc. through XML scripting via FLMM, and I don't have any Wormholes/Gates at all, and nobody can reach the System from outside. It kept things simpler, and now the mod is running error-free (uh, aside from constant spew about SUR errors, but Anton's working on that one for his next version of FLModel Tool ).

Edited by - Argh on 12/1/2004 10:25:40 PM

Wasabe:
Only one asteroid field in the system, and it's set up and working.

Oroweat:
Already got logging maxed out.

Argh:
Already checked all of those, it's none of them.

As I stated...
I only get the zone error message planetside, and ONLY when I go to the bar!
As a matter of fact...
If you run Privateer: The Reckoning OpenSP Beta v4.0, the system files are the same as what I'm using in the current build.
I've only changed the AI, some ship's loadouts, empathy, and a few other minor files.
I haven't messed with any of the system, or base files.


Watch your 6!