Problems with patrols and stations
-
Hi all,
I have a weird problem if i assign a patrol route, namely ive got CTD in the game, no matter what type of routes were assigned (lane, attack, trader, etc…).
And an another problem the stations and ships communications with each other: Ive got 9 stations but only one communicates with the incomming ships and vice versa. I dont know why this one is different from the others and what i have to do to set this communications for all bases.thanks in advance,
-
did you modify the mbases.ini and add a [BaseFaction] entry to the base for that faction’s patrol?
All patrols who want to land on a base must have their faction listed in the mbase.inis [BaseFactions]
Yes i added them to the base but nothing has happened but ctd. Is there any rule where should i start the patrol route? (near the base, in the base…etc)
-
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.
-
@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.
-
-
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. -
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.
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.
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. -
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. -
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.
-
@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