Problems with patrols and stations

@Ruppetthemuppet:

The solution? Never, ever, ever write patrol paths in FLE. Open a text editor and do it manually. Writing Encounters in FLE causes all kinda of buggery, try and do it by hand, see if that helps.

Well, thanks, i will try to do it manually.

The second problem i wrote remains, if someone could write a solution i’d appreciate that.

@Bejaymac:

Station communications - when in doubt always check the obvious, open the system ini and check the base entries actually have the correct “voice” entry. You have a choice of 3 possible voices for the base, they are atc_leg_m01 for the male voice, atc_leg_f01 for the female voice & atc_leg_f01a for the robot, anything else results in a silent station.
Because your using FLE this is the most likely candidate for the problem, as FLE lets you use any of the voices in FL for the station, when in reality only the 3 listed above will actually work.

I use atc_leg_f01 and atc_leg_m01 for all stations i checked them in FLe and in the system file also unfortunatelly they dont talk except only one base.

@Forsaken:

The reason your base isn’t communicating is possibly due to the fact that there are no behavior = trade encounter zones or patrols ending at it. If there are only behavior = wander type encounters… the base won’t communicate (as far as I know)

I made my ambient for that base with area_trade_trader, area_trade_freighter_pirate, and area_freighter_smuggler, but all of my bases have ambients contain trader behavior.

@Vital:

Check the distances from the end of the patrol to the bases, maybe this is the reason, maybe station loadouts, not sure, equipment = rumble_station or kinda this, dunno.

What the relation between loadouts and communications?
The distances same as in the vanilla systems.

@Forsaken:

are these ships docking with the base?

No, nevertheless all of those factions have been listed in that base.

@Vital:

Try to delete the base they dock and communicate with and see what happens(kinda neurological way lol   )

They do not dock, this is the problem, they do not communicate, this is the second problem.

@Vital:

@Davis:

one communicates with the incomming ships

@Davis:

they do not communicate

As i wrote only one does it, i wont delete that works properly. “They do not communicate”––> everybody else except this one…

@Bejaymac:

Have you checked the client error log (FlSpew) to see if it’s a dodgy loadout, any missing archetypes will be listed in it.

The mBases.ini is the usual culprit with crashing patrols, and it’s not because you forgot to add the faction to the base, the mBases is one of the touchiest files in FL, the slightest mistake can stop the file from working.
A typo in the mBases means that FL will stop reading the file at that point, which means everything else in the file is ignored by FL.
An FLE speciality is the doublicate base entry, every barfly will be ignored from the first of the base entries right to the end of the file.

I didnt know about his FLspew but i will try that, thanks.
This doublication is interesting, could you write more about this?

It seems i found that row in the mbases.ini that is responsible for communication and docking procedure:

[MVendor]
num_offers = 5, 7–—> num_offers = 2, 4 When i rewrite this two numbers all of stations communicate the incomming ships, and traders dock sometimes with the bases.

Weird thing is, many stations in the vanilla systems with num_offers = 5 , 7 could communicate with the ships in unique systems they can not. Howsoever with 2 , 4 it certainly works.

Thanks all answers and tips anyway.

@Bejaymac:

@Davis:

This doublication is interesting, could you write more about this?

When you delete a base with FLE it doesn’t always remove the mBases entry, then if you add a new base to that system at a later stage FLE uses the first available number, usually the same one from the deleted base, it then ignores the existing mBases entry and sticks a new one at the bottom of the file giving you double trouble

Ah i see what you meant
Yes, it doesnt remove the old ones, and if i delete them manually Fle searching for the old entries also.

@Legion:

[MVendor]
num_offers = 5, 7

All this controls is the minimum and maximum numbers of offered missions at any giving time! Meaning atleast 5 missions must be offered and no  more than 7!

You should really code the mBases yourself from scratch and not use FLE for that… Infact only use FLE for positioning and things such as making base exteriors…

I can have a look at your mBases.ini if you want m8!? all I need is the nicknames for those you’re having problems with…   mail the file to me if you want a hand

EDIT:

I would also need the ini for the system your bases are placed in

Email has been sent contains my mbases.ini, but after i retyped this two numbers everything works fine, nevertheless this row doesnt seem to have relation with this communication and docking things.
If you spot something else that may cause this problem please email back or post that here.

Thanks in advance,

Edit: I forgot to tell you that system code which is contained this problem: codes are: from bw11_01 to bw11_12