Quote:
Originally Posted by blueduck
Hello rudewarrior,
I have got some new information about your problem.
MissionEditor accepts a = for input but changes it in the briefing automatically to a -
If I change the - to a = the MissionBriefing-text will not be shown!
I think the reason ist that in the .MIS the parameter Briefing= can not have a second = in the text!
Could you send me the text in your screenshot in a simple .TXT-file to blueduck@lsh3.com
Regards
Blueduck |
@blueduck
Sent you the file as requested. Thanx for the help.
Ok, I just did a series of experiments. I was checking it against the radio log messages as well. All of the characters work for the radio log, so that's a non-issue. For the Captain's Log, these two characters we are working on, = and ", are the only issues. Curiously, the semi-colon works in the same way that it does when acting as a comment character, i.e. it blanks out whatever is after it. Why they had it function like a comment character in the Captain's Log makes no sense, but it is what it is, so I can just work around that.