BCS Map inspection shows errors because of unsupported characters

Elate · January 31, 2026 at 11:34 PM

Hi,

I'm using the map inspection tool in BCS and it finds errors for maps that I have in fact successfully installed, but it seems to be caused by unsupported characters in the file path (probably German characters like ß or similar characters). As you can see in the screenshot I attached, it shows a bunch of missing splines because the path has unsupported characters in the pathname. Is there any way to fix this? So the unsupported characters do show up correctly in BCS? My Windows language is set to English. I don't know what other reason could cause such an error; the only thing I can think of is unsupported characters.

Thanks

Enid Sinclair · February 2, 2026 at 12:21 AM

you can ignore this. OMSI load the Objekt

Elate · February 3, 2026 at 4:58 PM

Ok, thank you. Is there any way I can see the full file path of the missing file like as seen in the attachment: it doesnt show the full file path and so I cannot solve the problem manually by checking the files. I want to see the full file name

mrbeans04 · February 5, 2026 at 5:23 AM

Quote from Elate

Ok, thank you. Is there any way I can see the full file path of the missing file like as seen in the attachment

Morning! U could try to move the table a bit by using a small slider that appears between colums on the first row of the table. For example between columns "missing object" and "help". But would be great if developers could also check and improve. Hope it helps you further.

Elate · February 5, 2026 at 4:35 PM

Thanks, that worked. I didnt knew there where sliders in between.

Mayconrib808 · April 13, 2026 at 8:53 AM

I had a similar issue before.

In some cases, this can also be related to special characters in the file path (like ä, ö, ü or other non-English characters). BCS/OMSI sometimes has trouble reading them correctly, especially if Windows is set to a different language.

What helped me was:
- moving the OMSI folder to a simpler path (for example: C:\OMSI2)
- avoiding special characters in folder names
- making sure everything is installed in a clean directory

The slider solution definitely helps to see more of the path, but I think the main issue is that the full file path is not properly displayed or handled.

It would be really useful if BCS could:
- always show the full path (no cut-off)
- or handle special characters correctly

That would make troubleshooting much easier for everyone.

Has anyone else experienced issues with non-English paths or missing file names in the inspection tool?

Users Online