Out of Range

[pads103 37]

Love the product.  It adds so much realism.  However, I noticed quite a few frequencies do not play and indicate out of range.  During any flight there are usually one or two.  So far, the two most important are KSFO and KIAH tower frequencies.  Are you planning a fix or is there some way that we can fix these on our own, such as a config file?.  Thanks

[rcarlson1971 2]

Do you see the KSFO tower frequency in the list of in-range facilities when you are near KSFO?

[pads103 37]

Yes, I did select it in order to get the chatter, but lost it again when I selected the tower in the sim ATC

[rcarlson1971 2]

I'm not sure I understand the problem. Can you describe it in more detail?

[markcellis 133]

On 6/1/2021 at 9:54 AM, pads103 said:

Love the product.  It adds so much realism.  However, I noticed quite a few frequencies do not play and indicate out of range.  During any flight there are usually one or two.  So far, the two most important are KSFO and KIAH tower frequencies.  Are you planning a fix or is there some way that we can fix these on our own, such as a config file?.  Thanks

Did you try updating the COM database to match the SIM using the free Navdata Reader Tool? The tutorial for it is here:

https://www.stickandrudderstudios.com/fs-atc-chatter-tutorials/

Mark

[pads103 37]

Thanks.  I'll give it a shot

[pads103 37]

Hmmm...something is amiss.  I ran the Navdata Reader Tool and updated FS ATC Chatter according to the instructions, but I actually lost quite a few facilities for some reason.  Below is the log file:

2021-06-03 09:19:59.057 -07:00 [INF] FS ATC Chatter version 1.0.0 starting up
2021-06-03 09:19:59.773 -07:00 [INF] Fetching latest version information
2021-06-03 09:20:01.249 -07:00 [INF] Latest version is 1.0.0 Final (build 17), executing version is 1.0.0 (build 17)
2021-06-03 09:20:01.257 -07:00 [INF] Loading facilities from C:\Program Files\Lockheed Martin\Prepar3D v5\FS-ATC-Chatter\navdata-default.sqlite
2021-06-03 09:20:01.508 -07:00 [INF] 34396 facilities found
2021-06-03 09:20:01.658 -07:00 [INF] Found 14455 clips total
2021-06-03 09:20:01.695 -07:00 [INF] Selected controller type is 'None', clearing clip list
2021-06-03 09:20:01.726 -07:00 [INF] Connected to simulator: Lockheed Martin® Prepar3D® v5 (5.1.12.26829)
2021-06-03 09:20:01.727 -07:00 [INF] Loading facilities from C:\Program Files\Lockheed Martin\Prepar3D v5\FS-ATC-Chatter\navdata-Prepar3dV5.sqlite
2021-06-03 09:20:01.795 -07:00 [INF] Setting origin point
2021-06-03 09:20:01.884 -07:00 [INF] 33213 facilities found
2021-06-03 09:21:02.190 -07:00 [INF] Pausing chatter due to simulator pausing
2021-06-03 09:22:42.435 -07:00 [INF] Setting origin point
2021-06-03 09:22:43.060 -07:00 [INF] Clip list rebuilt with 2668 clips for controller type "Center" in region(s): "UnitedStates"
2021-06-03 09:23:13.799 -07:00 [INF] Selected controller type is 'None', clearing clip list
 

From the above, it looks like there is actually less facilities found by about 1K

Edited June 3, 2021 by pads103
Fixed

[pads103 37]

Got it sorted out.  I forgot that I had deactivated several of the default airport files and as a result, they were not picked up by the tool.  Everything is working great now.  Thanks for your help

[markcellis 133]

@pads103

Great news.

Mark

[Alvega 2,119]

@markcellis It took half an hour on my system to build this 657MB file (that will take lots of space on the HD)  to just update a couple of frequencies. Isn't there an easy way to deal with this?

Like perhaps if you make it available on your site (already edited with db browser to take less space) or including it on the FS ATC Chatter download? 

Thanks.

Edited August 17, 2021 by Alvega

[markcellis 133]

@Alvega

I think most of the people using FS-ATC-Chatter are likely using it with MSFS 2020 rather than FSX or P3D. For that reason I think it makes sense to make the default database match the standard FS2020 scenery. That said. if you install PayWare scenery there is always the chance that it might not match the default COM database but I think that may very well be an exception. I'll add this to the list for the next release of FS-ATC-Chatter.

Mark

[Alvega 2,119]

1 hour ago, markcellis said:

@Alvega

I think most of the people using FS-ATC-Chatter are likely using it with MSFS 2020 rather than FSX or P3D. For that reason I think it makes sense to make the default database match the standard FS2020 scenery. That said. if you install PayWare scenery there is always the chance that it might not match the default COM database but I think that may very well be an exception. I'll add this to the list for the next release of FS-ATC-Chatter.

Mark

I'm using MSFS 2020 and just had the lack of comms 2 or 3 times, always with CENTER. One was coming out of MYNN to MUCU. Couldn't hear any chatter from MIAMI CENTER because the frequency was wrong by 0.5 it seems. That's why I looked for a solution. I now updated the database but 657MB for that I think is too much. 

Regards.

[markcellis 133]

When I update the default one it won't be that big. The Navdata reader tool adds a lot of other data the database besides just the COM frequencies that is why it is as big as it is.

Mark

[Beardyman 604]

Hi, I use P3D5.3 and whole flight from OMDB to LGAV i am out of range. ATC Chatter is connected to sim. Navdata base was created as instructed in video tutorial - any help?

 

 

[markcellis 133]

Can you attach the log file? I'd like to make sure it is picking up the navreader database you collected?

Mark