FOTRS no objectives from port

[KaleunMarco]

Originally Posted by Starforce2

I am getting this message again. I was able to head out of port last time by returning to base from an earlier save. This emant I atleast got to use my new balao, rather than take command and then be unable to relaunch.


Is there any way to force it to give me an objective? Could it be mistakenly picking one of those "no objective" ones that you get when you use the status report? (you know the..no mission at this time patrol or rtb at you descression ect ect)

I just got done bottlenecking a convoy through the subnet (and showing me where it was) and did some major damage, including a huge 41000 ton linter, a medium passenger, a pair of nkss-kat (whatever those are for 5100 each) a DD that got too close, a freighter hung up on the net and an old subchaser.

I still had all my tubes loaded, including my compliment of 3 cuties, and if a betty hadn't given me 30% hull damage I'd have stuck around, there was an oldsubchaser and DE convention outside the subnet...and they all park at night

But this crap of "no objectives" is killing me. I've not tried transfering yet..that's next.

Yes, this is a fifteen-year-old post but occasionally i run into it and forget how to fix it. this is one solution not covered by lurker.

When a user displays their orders for their next mission and sees Objective <null>, the cause can be a disconnect between the mission.mis file and the mission.tsr file.

1. Browse to your SH4 save folders and find the save folder for the current carrier. it will be the most-recently created folder.
2. Find the file named CareerTrack.UPC. open it with a plain text editor.
3. Look for a line that has PlayerCurrentObjectives=IDnnn, where nnn are numbers. This is your mission ID and a pointer for the next step. Write down that ID-number. Close this file and do not save.
4. Browse to \Data\UPCDataGE\UPCCampaignData and look for a file named PatrolObjectives.cfg.
5. open PatrolObjectives.cfg with a plain text editor. Find the IDnnn in that file. The line just under the ID-line will begin with FileName=Data\Campaigns\CampaignGE\PatrolObjective s\ followed by a folder and file of your next mission, the one giving you the <null>. Write down the folder and file name. Close this file and do not save.
6. Browse to the folder that you just located: Data\Campaigns\CampaignGE\PatrolObjectives\ followed by a folder and file of your next mission.
7. In that folder, you will see two files, a MIS file and a TSR file. Very briefly, the MIS has the mission definition and the TSR has the mission text.
8. At this point, things may get complicated so I will stick with the Stock conditions.
9. Open both of those files with a plain text editor.
10. Normally, in the MIS file, Objective 1 is your Primary Objective. The Primary Objective name will appear as the first line. For example, ObjName=CO56. The name must appear in the TSR file spelled exactly the same as it is in the MIS file or else you will get the <null> error. In this example, the MIS contained CO56 and the TSR contained C056. The latter is a zero and the former is an oh, which yields the error.
11. The fix is to have the two values exactly the same. Change one, save the file and then close the other file without saving.
12. Relaunch SH4, load your save, check your orders and you should no longer see Objective: <null>.