Captain's Log Font

[rudewarrior]

What is the entry in menu.ini to determine the Captain's Log font that is actually displayed in game?

Thanx in advance.

[blueduck]

Hello rudewarrior,

for stock-sh3 it is in [G35 I5], "Font=5" which should be "FPHunt15".

Regards
Blueduck

[rudewarrior]

Originally Posted by blueduck

Hello rudewarrior,

for stock-sh3 it is in [G35 I5], "Font=5" which should be "FPHunt15".

Regards
Blueduck

Excellent, thank you. So it looks like the entry is for Name=LogText. It has the same entry in GWX, [G35 I5]. I use MaGui Final, which changes the entry to [G35 I6], but for all intents and purposes they both use Font=5, which is still FPHunt15.

FPHunt15.tga has not been modified in my set up. And if I open it and examine it, it has characters represented for the equals sign, =, and double quotes, ". However if I use either one of those characters in my log entries it has trouble in the game. For the double-quotes, it comes up with this weird inverted U that is more toward the bottom of the text line (see circles in pic). If I use an equals sign the whole entry will not even appear (the red box indicates where I would have used the equals sign).

Could anyone explain to me what is going on here?

[reaper7]

Maybe this might help.

http://www.subsim.com/radioroom/show...86&postcount=3

[rudewarrior]

Originally Posted by reaper7

Maybe this might help.

http://www.subsim.com/radioroom/show...86&postcount=3

Hi reaper7,

Thanx for the info, but unfortunately I don't think that is the problem. Or I may just be looking at it improperly.

When I open the .off file using Silent 3ditor, I just get an all black screen, so it doesn't actually show anything. However, if I verify the character positions and dimensions noted in the .off file by physically checking them using GIMP in the .tga file, they are correct.

From my understanding, according to this, the way it works is that SH3 looks at the .off file to determine where to look in the .tga file. Then it prints what it sees in the .tga file. If this is correct then there is nothing wrong here that I can find.

Now, if it renders it directly from the .off file, then it could be there since it only comes up with a completely black screen in the editor.

If anyone could clarify or has any other ideas, that would be great.

[blueduck]

Hello rudewarrior,

as far as I understand the fonts, you are right!
The .OFF tells SH3 where to cut out the characters from the .TGA!

I tested your characters in a German SH3 and the double quotes do work fine but the equals sign is also changed to a minus sign.

I guess there is a problem with the keyboard settings or the key codes.

Regards
Blueduck

[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

[rudewarrior]

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.