• You can’t change the default variable names. Not without a hell of research into and editing the freelancer.exe file.

• Your best bet, therefore, is to use some form of anti-cheat for the server or be very vigilant

• Some variables are missing yes, and the game uses the defaults if none are present, as you suspected

• Also some variables that are present aren’t actually used by the game, or have no noticeable effect

The ‘hardcore’ guys will be able to fill you in better with any more in-depth info, but I believe that’s the jist of it

“Rotated 180 degress”, ROFL! Yeah right. Like they don’t just slam in all in how they like…

You fuzzkszed that title up eh

So long people have the latest microsoft malicious software detection tool ran, it should all be fine.

No suprise. They’ve given people plenty of pre-warning and time to download and move stuff. Pretty silly to just store the one copy online though and not on a local hdd or optical disc…

Always drama…

One word. LOL. Everyone take some time to chill out ffs.

Hex-rays ;D ;D

Exclude it. Don’t wait for updates, ROFL

Specify all the parameters for the ships: 99999, 99999, 99999, 99999, 9999

He’s clever, lol Good job M0tah

I’m rolling with my ‘workaround’. I actually like the region displayed in more places than just the system jump.

Aigle:

- Error in Mbases.ini on line 2837 - you have 2 entries on one line (individual_name & affiliation).
- You have duplicate reputation entries in multiple system files (as follows):
	COL01 - line 412
	COL02 - line 428
	COL03 - line 278
	COL04 - line 305
	COL05 - line 270
	COL06 - line 251
	CYL01 - line 262
	CYL02 - line 251
	CYL03 - line 255
	CYL04 - line 250
- Error in CYL04 system. Line 228\. 2 entries on one line (nickname & pos).
- Suggestion. You should make new room entries, rather than pointing new bases to existing ones.
- Do you have pathfinding info all under control?
- Something seems to be up with 'br12_07_base' entry in mbases.ini. It's not present in any system file.
 From what I can tell, you need to sort this out to fit in COL06\. I 'think'.
- Some system encounters don't quite add up. Not an 'error' though, just an optional fix.

I read what you put though about you wanting to remove the problematic system which is br12_07. It isn’t in any system file or universe.ini so it should be safe to remove all references from mbases.ini. When exactly does it crash… as you say when you remove that entry it crashes. Something has to be referencing it still. In those files I looked through, none of them do, and if you have no other files with that it, it’s quite puzzling indeed.

It could be something to do with the multiline error in that system, which may solve it if you rectify that. This happens with a dodgy text-edit. Not sure what you are using. I had this issue with either notepad or wordpad once (with wordwrap on), and I have never had it with a more professional editor such as Notepad++ or Editplus. They can handle large files well and represent the text (more specifically the newline characters and tabs) properly. Might be a consideration.

If you don’t mind the system name and region showing up in missions, the navmap and various other places, then just reassign each vanilla system name to a new ids number, and include the region name as Tunicle said above. Then go through the resources .dll and remove the system suffix from each of the variable lines ‘%s’. Then as a final touch, remove the pre-done region names from the system infocards… ‘LIBERTY’, ‘OUTCASTS’ and so on. Looks much better on the info screens on the navmap. It’s a workaround, and a fairly big one at that, with the compromise of having to have the region displayed in more places than you want (due to the system names IDS getting parsed from many locations), but I don’t think it looks to shabby. Give it a go and report back ;D

Yeah was gonna say mate… FL is one thing… RL is quite another. So is words vs. action.

No. I believe it’s because it expect the standard naming convention of system prefix and number… with a max of 2 letters and 2 numbers. I don’t think the actual number/letter thing matters, just the actual max length of 4 for the system… and then same deal for bases, but for a max of 12. Pity Joe doesn’t still develop his FL programs. And no source available… well I remember him offering it up for a price… Out of luck I think man…

About the “blank line eater”, I can’t see how performance can take even the most slightly noticeable boost by removing blank lines. And not to mention the fact it makes the inis absolutely horrible to read through. Opinion I know, but from what i’ve done with a similar method it’s a no go. And those who say it makes the mod smaller are plain looney! White space and return characters compress up to nothing on even the most conservative compression modes… end of

Hmm. Would you mind upping your universe, mbases and system ini(s) to take a look at? Or PM if you don’t want it all public. I know a fresh eye can do wonders. Take all the problems i’ve had

That is normal. Most people get that one. It’s to do with having extra white spaces. The game ignores these anyway, so it’s no biggy. And certainly not the cause of your crash. Does FLScan/FLIA/FLEC give you anything to work with? Or do you have any other errors in the log? Problem with crashing (if it’s the server) is that you don’t always get a helpful message in there.

Can you explain a little better on what it is you have done so far, and what files you have altered? It sounds like something is been referenced that doesn’t exist anymore. FLEC should flag something up though, so give it a run. I can tell you that 3-letter prefixes are fine to use. Never had any issues myself

Nah, I always run error checkers and always make sure they are clean. This is what is puzzling me. First time I actually flew into that system actually, and noticed the crash. Damn encounter-problems (I think :P)… so elusive… i’ve review it later I guess by hand…

Hi folks.

I’m just about to pop off for work, and i’ll try and address this when I get back, but if anyone can jot down any ideas, that would be brill!

Basically, I am having an issue when docking with one specific tradelane. It onlt affects this one, and it is in the Shikoku system (just outside the jump to Kepler I believe). Now, after looking through some old threads of TLR, it seems it could be to do with lane encounters and a royally messed up tradelane (ie. rings not running in sequence, misnamed rings etc). However, the tradelane is fine. I haven’t touched this system at all… at least I can’t remember doing so.

Any ideas on what I need to be looking for. I’m thinking it’s encounter related. Either along the lane or in the area it finishes at. It crashes as soon as I hit dock. I get no errors in any log file, so that’s no help unfortunately…

Cheers

I replaced that one with a blank wav after having an ‘audible’ one in there. Damn annoying. Did it absolutely everywhere you go to dock. Tradelanes, the works I am also wondering about these occasional material errors. If there was some way to quickly browse and create hashes, rather than manually do it, which would take stupid amounts of time. That aspect issue is wierd. If it is indeed a camera entry, check it against this:

[WinCamera]
fovx = 54.431999

[CockpitCamera]
fovx = 90
znear = 2.000000

[ThirdPersonCamera]
fovx = 90

[DeathCamera]
fovx = 90

I’ve never had that crop up. Unless it’s referencing one of the cockpit ini entries directly:

[Cockpit]
mesh = cockpits\liberty\models\li_fighter_cockpit.cmp
int_brightness = 0.500000
head_turn = 50, 40

[CockpitCamera]

[TurretCamera]
tether = 0.000000, 5.780000, 22.874001
yaw_rotate_speed = 2.000000
pitch_rotate_speed = 1.500000
accel_speed = 5

Definately wierd. Is there anything in the archive about this bro?
EDIT

Yep, one thing of interest in the archive. I think we can narrow it down to a ship (player or NPC) that has a pilot hardpoint. but no cockpit hardpoint. Thanks to startrader for this input. Apparently, ships (such as certain capital ones) that have no pilot hardpoint and no cockpit hardpoint don’t get this error. But as soon as you have a pilot but no cockpit, then that throws up. I also read in a few places that hardpoints need to follow the right naming convention, including the capitalization. So i’m guessing you would need to check to make sure you have a: HpCockpit present in there. A HpCockpit01 won’t do it?! Apparently. And HpCockpitEx is just plain wierd… ha!

You know far more than me though, I may still be wrong. Looks logical enough though Get it sorted man!

Yeah…. I just have a feeling I misunderstood what he meant though MK, lol