On 10/17/2020 at 10:04 AM, jabloomf1230 said:

Has anybody tried to alter pronunciations by creating a new version of en-US.locPak in the Community folder? It seems stupid to make these changes over and over again just to have the file overwritten with each MSFS update?

Totally agree that it would be nice to have a version we can put in our community folder so that we don't have to do this every time a new update or patch is released.

I'm so glad someone has figured this out, I was an "Air Traffic Controller" for many years, and still work for the FAA, we never used "Daher" it was always "TBM."

This mod is unnecessary and causes conflicts for those who use the working title g3000 mod. You can just simply go to ATC menu and set your Callsign to "TBM" instead. No need for this.

On 10/19/2020 at 12:13 PM, captain420 said:

This mod is unnecessary and causes conflicts for those who use the working title g3000 mod. You can just simply go to ATC menu and set your Callsign to "TBM" instead. No need for this.

Was going to post the same in terms of rendering the G3000 mod unusable.

On 10/19/2020 at 3:13 AM, captain420 said:

This mod is unnecessary and causes conflicts for those who use the working title g3000 mod. You can just simply go to ATC menu and set your Callsign to "TBM" instead. No need for this.

what is conflict it causes?

On 10/19/2020 at 3:13 AM, captain420 said:

This mod is unnecessary and causes conflicts for those who use the working title g3000 mod. You can just simply go to ATC menu and set your Callsign to "TBM" instead. No need for this

Thanks for the info regarding the G3000, I looked into it and know why this is happening. I can't go back end edit the original post, but if you update the ATC lines aircraft.cfg, the G3000 will work.  Updated lines should be:

atc_type = "TT:ATCCOM.ATC_NAME TBM.0.text"
atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"

 

Re: Simply changing your callsign in the ATC menu is something you have to remember to do every single time - I kept forgetting so I found these edits. So whether this modification is necessary or not - personal preference, don't like it - don't do it.

 

 

18 minutes ago, Flyfaster_MTN002 said:

what is conflict it causes?

Not sure what exactly the conflict is, but when i use the ATC tweak above the whole G3000 mods stops working. All setup functions become inop, the is set to north up and you can't set anything. So basically everything goes inop.

Looks like is has to do with the entry done in the aircraft.cfg. Everything went back to normal after turning it back to the vanilla settings.

Edited October 20, 20205 yr by ThomseN_inc
Disregard my post as Uwajimaya was 10 seconds faster at replying :P

15 minutes ago, ThomseN_inc said:

Not sure what exactly the conflict is, but when i use the ATC tweak above the whole G3000 mods stops working. All setup functions become inop, the is set to north up and you can't set anything. So basically everything goes inop.

Looks like is has to do with the entry done in the aircraft.cfg. Everything went back to normal after turning it back to the vanilla settings.

Now this is interesting - had similar issue. Made these entries/mods and after installing the new G3000 was unable to pan view at all. The upper rosen visor was also totally pixelated. Uninstalled it.

After you reverted to original TBM entries did the G3000 work normally?  Wondering if this was causing my issue as well?

9 minutes ago, Flyfaster_MTN002 said:

Now this is interesting - had similar issue. Made these entries/mods and after installing the new G3000 was unable to pan view at all. The upper rosen visor was also totally pixelated. Uninstalled it.

After you reverted to original TBM entries did the G3000 work normally?  Wondering if this was causing my issue as well?

Affirmative! After reverting the mod went back to normal operations.

26 minutes ago, ThomseN_inc said:

Affirmative! After reverting the mod went back to normal operations.

It gets weirder - just checked the entries and found they had somehow reverted to the original. Use the MS Store version if that makes any difference.

The TBM aircraft CFG file shows:

atc_type = "TT:ATCCOM.ATC_NAME_DAHER.0.text"
atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"

Those appear to be the original entries correct?

3 minutes ago, Flyfaster_MTN002 said:

It gets weirder - just checked the entries and found they had somehow reverted to the original. Use the MS Store version if that makes any difference.

The TBM aircraft CFG file shows:

atc_type = "TT:ATCCOM.ATC_NAME_DAHER.0.text"
atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"

Those appear to be the original entries correct?

I think they are....cant tell for sure because i don't have the file at hand atm.

Did you see my post above? If you are making the full TBM ATC edits (including the locpak edit), the aircraft.cfg file needs to be updated to read:

atc_type = "TT:ATCCOM.ATC_NAME TBM.0.text"
atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"

Originally, I had the second line as "atc_model = “TT:ATCCOM.AC_MODEL TBM.0.text” and it that second line that's causing the conflict. The G3000 mod calls the atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"  string twice, and breaks if it's not there.

4 hours ago, Uwajimaya said:

Did you see my post above? If you are making the full TBM ATC edits (including the locpak edit), the aircraft.cfg file needs to be updated to read:

atc_type = "TT:ATCCOM.ATC_NAME TBM.0.text"
atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"

Originally, I had the second line as "atc_model = “TT:ATCCOM.AC_MODEL TBM.0.text” and it that second line that's causing the conflict. The G3000 mod calls the atc_model = "TT:ATCCOM.AC_MODEL_TBM9.0.text"  string twice, and breaks if it's not there.

Likely not! 🙂 Strangely the original edits don't appear in the files. Not sure if they got over written or reverted somehow?

Sure enough that did the trick - made the edits (again) and re-installed the G3000 mod now working properly!

Thanks for the heads up and apologies for missing your update post...

Edited October 20, 20205 yr by Flyfaster_MTN002

4 hours ago, ThomseN_inc said:

I think they are....cant tell for sure because i don't have the file at hand atm.

I just made the requisite edit(s) from his updated post (see above) and re-installed the G3000 mod.  TBM is now working properly!  Give it a shot see if that helps?

5 hours ago, Uwajimaya said:

Simply changing your callsign in the ATC menu is something you have to remember to do every single time

In the 1.9.5.0 update. Asobo fixed the ATC options, and whatever changes you make there such as Callsign, Tail Number, etc. They all get saved. I just set the callsign to TBM and never had to change it again.