Which language are you using? I'd be surprised if it were the English language, as you'd be hard pressed to find a font that doesn't support it!

Assuming that's the case, the config file listed above is not the one that's currently being used. The behaviour for reading config & content directories was tweaked slightly in 1.11, see https://github.com/OpenTTD/OpenTTD/blob/master/docs/directory_structure.md for more details about where to look for the active config file. You can also use -dmisc=4 commandline flag to get (a lot of) extra output about where OTTD is searching.

This is probably the reason why some sound/music sets have disappeared for you as well - they're in directories that are no longer being searched.

Well I'm using English, that is also what suprise me as prior to 1.11 with the same config there are no issue at all even with 1.11-RC1. I not sure what change for 1.11 release but something must have been gone wrong.

Would you be able to start the game with a debug window open? Via powershell, navigate to the folder OpenTTD is installed in, and run:

openttd -dsprite=1 -dfreetype=1

And can you tell us what the black window also opening next to OpenTTD is telling you? Specifically, it should tell the exact character it is missing. That would greatly help us, tnx :)

Here's screenshot of both windows, text in the terminal shown as:

dbg: [misc] String too long for destination buffer
dbg: [misc] String too long for destination buffer
dbg: [sprite] 1263 extra sprites, 1263 from baseset, 0 from fallback
dbg: [sprite] 1263 extra sprites, 1263 from baseset, 0 from fallback
dbg: [freetype] Font is missing glyphs to display char 0x5C in medium font size
dbg: [freetype] Trying fallback fonts
dbg: [freetype] Fallback font: Arial (Arial)
dbg: [freetype] Font is missing glyphs to display char 0x5C in medium font size
dbg: [freetype] Trying fallback fonts
dbg: [freetype] Fallback font: Arial (Arial)
dbg: [sprite] 1263 extra sprites, 1263 from baseset, 0 from fallback
dbg: [freetype] Font is missing glyphs to display char 0x5C in medium font size
dbg: [freetype] Trying fallback fonts
dbg: [freetype] Fallback font: Arial (Arial)

Lookup in the search seem like 0x5C is the backslash character, might have something to do with the system locale as my system locale is Japanese.

Thank you very much!

What is a bit odd to me, that we don't have any string with a \ in it that we didn't have before :P So I wonder what is causing that .. but at least this gives some clues where to look. Tnx!

I tried to reproduce this issue on my own system, so I could debug the problem. But when I use that exact same openttd.cfg, it doesn't error out for me.

There are two things weird to me:

1. nothing changes in the use of \ between 1.11.0-RC1 and 1.11.0.
2. why would a default font not have \ in its set for your system, while it does work for my system.

I am not sure how to proceed. Hopefully another dev has an idea :)

I am wrong about that 1.11.0-RC1 had no such issue, cause I redownload that version and found out that it too have this problem.
Out of the version I redownload, seem like the issue had started all the way from 1.11.0-beta1 and none at all for 1.10.3. I might have been ignore that message when I test 1.11.0.

c6fd6cf

Ah, yes, of course! The error was always hiding, but still there. We now only tell that the font is bad, instead of silently falling back to another :D How could I have forgotten about that.

So that brings us to the core issue .. the font doesn't know how to render \ which is really odd :(

Just manage to trace down the change in between 1.10.3 and 1.11.0-beta1. If the debug message is correct then which string is the faulty one?

Also the locale maybe to be blame, as stated my system locale is set to Japanese, Shift JIS which is by default will render the character 0x5C as "￥" instead of the regular character "\". In which most English font are unable to render the "￥" character.

So that might be the core of this issue.

If I remember correctly, 1.10 already failed to load the font you selected (but didn't tell you about it). You can see this if you start 1.10.3 with -dsprite=1 -dfreetype=1. It properly also says it is falling back to Arial in your case.

If that is correct, it means that 1.11 tells you about this happening.

There is not much we can do about this. We validate fonts to contain all the letters we expect them to, and if they do not, it means it cannot render all our strings. So we find the next best font that can. As it most likely already was falling back to Arial for you, properly the best solution is to change that in your configuration file too.

But this relies a bit on my memory that 1.10 already sneaky did this, so that might be good to confirm first :D

What a journey this :D Fonts are really really hard ... and why most games just embed a single one and lets you deal with that :)

Perhaps the debug message could be improved by printing the string where the character is missing?

Well setting the font to Arial does eliminate the message.

Okay, in that case, if you don't mind, I am going to close this ticket. As it is not so much a bug, but more that we finally show that something wasn't working before :) Which is a bonus .. too bad it took us a while to remember we added that. Sorry about that :D

Happy gaming!

Thanks for the help anyway.