flytriman

Thanks Mark, I see they are all in Oceania, so I'll just delete that folder from P2A and copy and paste from the Chatter folder. Garry

Mark, Just downloaded the latest collection and noticed that there were 35 deleted files due to being "obsolete". Since I also use Chatter in P2ATC I normally just copy the updated Chatter regions to my P2ATC Chatter region's location and let it overwrite the new entries. Obviously, I can't do that with the deleted files as I don't know what they are. Could you tell me what the 35 deleted files were so I can delete them from my P2ATC Chatter file? Thanks, Garry

Okay thanks. Good luck. Garry

I noticed with the new DC-3 I rarely (almost never) get any climb performance numbers from the "Current Performance" tab of the Flight Planning page. I always get Taxi Fuel...about 50% of the time I get Cruise numbers and rarely get descent numbers. Yet the page always knows what the aircraft is doing and reports Aircraft status as Climbing or whatever it is doing. If I use the "Simulator Aircraft" report from the Window tab it will always report all performance numbers. I tried a couple of other aircraft, and they work normally. I also tried using the vanilla version and the several mods...no difference. Any ideas? Thanks, Garry

Okay…got it…thanks. Garry

Hi Alex, Thank you for this update and for the program...could not fly in the sim without it. Noticed a couple of issues with the new MSFS2020 DC-3. It has to do with the IOCA model identification. I've attached 3 screen shots that show what is happening: As you can see from the shot titled "Aircraft Performance", LNM does not like the aircraft type I have in the "Aircraft Performance" file. I looked up the IOCA designation (DC3) and tried that but then the Flight Planner says it does not match what is in the sim. I then went into the aircraft file and found that it's IOCA Type is shown as "DC-3"...so tried that and got what you see in the shot titled "Error Report". Any ideas? One other thing...under the "Current Performance" tab in the flight plan it shows as an "Example Performance Profile - C172" even though the data is correct for the DC-3. Used to be this had the aircraft flying identification. Thanks for any help. Garry

I think your right…it was FS9. Talk about this “classic” technology…flying the B247 with the “Radio Ranges” took awhile to master, but great fun once I did. Garry

Hi Alex, Thanks for the reply. I do see now that I can set the "T" vs "M" as I want so that is clarified. The KNS-80 is not a GPS unit. It was a very early unit (referred to as an RNAV...although by todays use of that term it's not exactly accurate) that allowed pilots to virtually move a VOR to somewhere else and then the unit would provide a signal to the HSI so that it acted just as if there was a regular VOR at that virtual location. I'll go ahead and post the question on the MSFS forum for the Analog C208B to see how others are handling. Again thanks, Garry

Hi Alex, I have started to make more use of the "Measure Distance from Here" feature since flying the new C208 Analog and using the KNS-80 RNAV. However, I can't seem to get the accuracy I need. So, after some investigation, including reading the appropriate sections of the LNM manual again...and reading this post, I have some questions. I am using version 2.6.19 of LNM. The manual clearly states that the bearings shown with "Measure Distance from Here" feature are "True"...however the flag clearly says "M". Please clarify. Since I get two bearings do I want to put into the KNS-80 the 1st number or the 2nd number...or do I use an average of the two? Thanks, Garry

Understand...I'll just "solder" on as I've been doing then. Thanks, Garry

Thanks all for the replies...however I obviously was not clear on what I'm trying to do. I do have my current setup as Dave described and it works fine. However, I also have the FS-ATC-Chatter program, so I end up having the Region files in two places on my PC. One set within the FS-ATC-Chatter Program folder and a 2nd set within the Pilot2ATC program folder (just as Dave outlined). What I trying to do is only have one set of the region files that both programs can use. So, I went to the manual, page 79, "Alternate Root Folder" to use that to point P2ATC to the FS-ATC-Chatter program folder where the regions are located. Can't seem to make it work. As I said on my original post (and included a screen shot of the folder structure), I have tried using every folder within the FS-ATC-Chatter program folders as the "Root" folder...none work. Hope this is clearer. Thanks, Garry

On a Windows 11 PC using MSFS. Used P2ATC for years and have previously tried to point my chatter use to the files within ATC Chatter itself instead of having to duplicate the sound files within the default P2ATC folder...never any luck. So thought I would give it another try...no luck. ATC Chatter works by itself and the Chatter files work within P2ATC, as long as I copy the Chatter Regions into the default location of P2ATC per the manual. However, if I try and point the P2ATC Chatter to the Root Folder of ATC Chatter...nothing. I have included a screen shot of my file structure of ATC Chatter and tried to use each and every one of the folders you see as the Root Folder... i.e.: F; then tried MSFS 2020, then tried Add On's, etc...all the way down to FS ATC Chatter folder...no luck. So, what am I doing wrong...and what do I need to do to make it work? Thanks, Garry

Got it...thanks. Garry

Apologize if this is a "dumb" question...I see several references to the "MSFS AP" folders...don't find anything named that. Where would I find it on a PC Store version? Thanks Garry