• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS MSFS Localization Manager

Well, that's a big disappointment. I don't know what I was expecting from the MSFS Localization Manager but whatever we got wasn't it.

I was kind of hoping that it would use Bing to automatically fill in translations but no such luck. Maybe I was too optimistic with that.

As far as I can see neither of the export options (XML or Excel) work. The XML export generates files with only a couple of lines. The Excel export generates nothing.

The editor itself seems to be no quicker than copy and pasting in the .loc file directly. I suppose the only advantage is that the editor generates the GUID for you.

I have already written a spreadsheet which allows me to easily copy and paste a bunch of Google translations into it and then export a text file which, with a bit of find and replace in notepad++ produces a localisation file. I think I'll keep using that method.