I've pointed the program to my install of FS-ATC Chatter/controllers yet the checkbox to enable chatter does not engage. I also tried copying the contents of the folder and placing it in Pilot2atc/sounds.
Thanks in advance.

Edited October 6, 20241 yr by Zatoichi

Try connecting to the sim. I found that the enable chatter option didn't activate until I was connected. Also, the configuration options around a default region don't ever seem to populate.

Bingo!
Thank you.

Silly second question.
Is pointing to the FS-ATC/sounds folder sufficient (to be input at the bottom of the window in Pilot2ATC) or must I copy the sounds folder itself into Pilot2ATC?
If pointing works I'll save a bit of disk space. I saw a youtube in which the instructions specified copying. But I think it was "V2 on X-Plane."

5 hours ago, Zatoichi said:

Silly second question.
Is pointing to the FS-ATC/sounds folder sufficient (to be input at the bottom of the window in Pilot2ATC) or must I copy the sounds folder itself into Pilot2ATC?
If pointing works I'll save a bit of disk space. I saw a youtube in which the instructions specified copying. But I think it was "V2 on X-Plane."

You'll need to copy to the v3 location.

In the Chttr tab of Settings in P2A, you should be able to point to the folder that Contains the Regions folder of your Chatter file structure.  

Dave

Hi,

 

I followed the directions to set up Chatter under the Sounds folder in V.3 with the pointer to Regions—still no joy. I also have a version in Xplane under the resource/plugins to use when not using V.3. Is this perhaps the reason Chatter is not recognized in P2ATC

23 minutes ago, Jayf901 said:

Hi,

 

I followed the directions to set up Chatter under the Sounds folder in V.3 with the pointer to Regions—still no joy. I also have a version in Xplane under the resource/plugins to use when not using V.3. Is this perhaps the reason Chatter is not recognized in P2ATC

Pointing didn't work for me, however copying did.

Currently testing, same problem. Found a solution that seem to work now for me:
Opened command prompt (I call it "DOS-Window 🤪) as "Administrator" (mklink needs admin privilege).

> mklink /D C:\Games\Pilot2ATC_3_x64\Sounds\ATC_Chatter\Regions C:\Games\FS-ATC-Chatter\Region

That creates a symlink - not to be confused with a "normal" Windows shortcut.
Now in V3 the regions are selectable for me and chatter happens.

My findings::

• The V3 folder C:\Games\Pilot2ATC_3_x64\Sounds\ATC_Chatter was empty
• Whereas V2 (where chatter works) has a Regions folder with ClipTags.csv and empty (!) subfolders for each region.
• But the chatter folder setting in V2 points directly to my FS-ATC-Chatter-Folder C:\Games\FS-ATC-Chatter.

Maybe P2A wants to have a (even empty) Regions folder structure in its own folder,
or maybe related to the folder's security settings: different for normal users vs. administrators,
so different access rights running P2A with or without admin rights.

Assuming the security permissions are set appropriately, you can just point P2A V3 to the Chatter folder that contains the "Regions" folder from FS-ATC-Chatter or X-ATC-Chatter program.  In your case, you should be able to point it to the same folder that V2 points to.

I suspect if that didn't work, it does have to do with folder security settings as you suggest.

Dave

The last hour I've tested - P2A V2 works but as I've written: it contains an empty folder structure below Sounds -> ATC_Chatter :
Regions ->  Africa / Asia / ... (don't contain any files).
In Regions I find an older file "ClipTags.csv".
In V2 Config -> Sounds, "Root Folder " is C:\Games\FS-ATC-Chatter and "Default Region" is selectable.

In V3 after installation, Sounds -> ATC_Chatter was empty and ATC Chatter Folder pointed to C:\Games\FS-ATC-Chatter  as in V2.

My FS-ATC-Chatter Regions folder's security properties are different for administrators, "authenticated users" and users.
While the first two groups have all allowances, users may only Read & Execute, List folder contents, Read, but not Full control, Modify or Write.
As I didn't use a password on my flying rig, that may be the reason for chatter not working in V3.

Maybe it doesn't work in V2 either if I simply start P3D & P2A by clicking on it (as "user") - I do this mostly for testing and development reasons (airport modification tests a.s.o).
So maybe even in V2 it worked only when I start a full flight: setup by a .BAT file that runs as administrator, all addons and P3D run as "administrator" too.
I didn't know until now that Windows (or the Windows installer) differentiates between users with and without password.
That may explain some of the problems.

I will test it further but it needs some time and at the moment I'm testing other aspects of V3 as the trial license ends sunday.
And with my symlink, the problem seems to be solved for me.
 

Definitely sounds like a security/user permissions issue.  Glad you found a solution that works in your environment.

Dave

Sorry, my fault, as a former mainframe/unix gui, I'm not deep in Windows security mechanism - and it's no security problem.
Now, what happens ?

It made me wonder, why I had setup a folder structure in P2A V2 ...\Sounds\ATC_Chatter\Regions with empty folders below: Africa, Asia, Canada, Custom, Europe, ...
although in P2A V2 config, the "Root Folder" entry points to ...\FS_ATC-Chatter (with the real sound files below Regions\Africa Regions\Asia ...).

It seems, P2A V2 uses the "Root Folder" entry (...\FS_ATC-Chatter\Regions\...) to get the sound files for each region but uses its own folder
...\Sounds\ATC_Chatter\Regions to get the default region.

And it seems, P2A V3 has taken over this mechanism in Settings -> Chttr:

• In block "ATC Chatter", the "Default Chatter Region" is only selectable if there are these (empty) region folders below ...\Sounds\ATC_Chatter\Regions in the P2A installation directory
• But it plays the chatter (correctly) from the entry in block "ATC Chatter Folder".

On 12/7/2024 at 12:50 AM, Zatoichi said:

Pointing didn't work for me, however copying did.

That's the reason why it only works for this guy as he copied the FS_ATC-Chatter folder "Regions" into the P2A installation directory.
He hadn't to copy the files, the empty region folders are sufficient (as in my case).
Or route the P2A ...\Sounds\ATC_Chatter\Regions with a symlink to the FS_ATC-Chatter "Regions" folder as I did before and now, after my tests, again until this behaviour would be changed.

So in my opinion - and maybe I'm wrong, but did some intensive testing the last hour, this P2A behaviour should be corrected so that the P2A settings -> Chttr : "Default Chatter Region" field checks against the subdirectory "Regions" in the folder specified in block "ATC Chatter Folder" below, but not - as it seems for me - hard coded against the P2A installation folder ...\Sounds\ATC_Chatter\Regions.

Thanks for the further investigation and detailed report.  I agree and will see what's going on with the populating of the Default Region options drop-down.

Dave