tmeacham

I use multiplicity, it does share sound. It's a great appplication for managing an extra PC. The sound has a slight delay, but it is not noticable, works very well with P2ATC trev

Hi Bruce, Dave is right I'm afraid. Your proposal will not work. Inputs to PC's are called "mixer inputs" on the PC, but do not work like real studio mixers. You can set up an optimal setup like mine though: PC 1 Works p2atc, has headset and microphone (USB or hard wired) PC 2 is X-plane, Has boosted 500 watt surround speakers, with a big sub-woofer (base speaker). The PA system is 4000 watts in here! Talk to P2atc on your headset and experience the airplane sound and vibration in the room! My room is a soundproof studio (I'm a professional musician) and winding up a jet turbine will shake the walls! With headsets on, me and my passenger can experience very realistic sound. You can buy a bluetooth of other sound system for your PC very cheaply these days. Pilot2ATC is still the very best add on for any flight sim, professionally supported by Dynamic Dave! Have fun trev PS I have two headsets/mikes connected together through a small mixer unit that allows not only individual volume adjustment, but we have an intercom between us.It feeds output to the PC1/p2atc unit.

Thnk you Phillipe! They work well!

Agree completely, Dynamic Dave is exceptional in his responses, imagination for coming up with this great product, and last, but not least, the quality of his work. Thanks Dave!

Thanks for the quick reply Dave! I had tried installing ACT Chatter on the P2A machine, heard nothing at all. So I installed the updated version - works perfectly! It's an awesome add on to P2A, completely confused my friends watching (and listening) because the chat is so real. Add the superb AI in P2A and it is as real as it gets - Great! trev

I'm not sure if this is just a feature request. It is certainly not a bug in this outstanding software. While enroute, ATC will often direct contacting the next control area by name, as in "Diamond Romeo Zulu, contact Munich center on 123.45" This is extremely explicit and very realistic. My copilot, however, drops the region name and will respond with "contact center on 123.45" and then contacts the controller with "center, diamond Romeo Zulu is at flight level eight zero", always omitting the name. In IFR Radio, whilst not always policy, it is helpful to use controller region names. Some instructors will coach that you should always use the controlling centre name. This helps avoid confusion when incorrect frequencies are dialled in. In RL, we use: "Munich center, Diamond Romeo Zulu is with you at flight level eight zero", or similar. This is not only used for initial contact, but is often used after a delay in communication. It sounds like a viariable inserted into the TTS, as ATC is often able to pick this up, very cleverly, adding a regional immersion factor that absolutely blows me away. I can see no harm in adding the ATC center name to all dialogue. When things are very busy, this is a great help. Great product, anyone who doesn't have it MUST get it! kind regards, trev

I love P2ATC, I use it every day. The product is amzing in the intelligence of its ATC control - I have never seen, or heard, anything like it! I bought ATC chatter too, but I am running P2ATC on a networked PC. ATC Chatter does not work in this configuration - no sound at all. I can load it on my XP PC, but then P2ATC has no control and it is bedlam. Any idea how to make this work over a network? kind regards, trev

BTW SDK version 3 is released, available for download. So is the LR G1000 (Which is great!). On Beta 11.1 Meach

I have just completed setting up two Windows 10 PC's, one running x-plane 11, the other running pilot2atc 2.3.0.0. It's a great setup, I love it. There are a few challenges to overcome. I'll write them up here to help everyone else.There are several sections in this post. First is XUIPC, downloadable from: http://www.tosi-online.de/XPUIPC/XPUIPC.html This Zip file contains both XPUIPC and XPWideClient described below. The software is "DonationWare", so you can download it free and make a donation if you want to, but it's not mandatory. As Dynamo Dave said, Wideclient is required on the P2A PC. XPUIPC on the XP PC. Both are very simple to set up and documented in this forum. To save you searching, here's their setup: Step One XP to P2A comms X-plane PC - unzip the XPUIPC file into (Your Drive Letter):\X-Plane 11\Resources\plugins edit the XPUIPC.ini file with notepad and put your PC's IP address in as Server Address = P2A PCUNzip and copy the XPWideClient folder onto the desktop (for easy access) You can test this by running x-plane and checking that XPUIPC is in the plugins drop down. No other setup required for XPUIPC. Then open the XPWideClient folder and edit XPwideclient config with notepad. In [Network Settings] put the server as the x-plane PC's IP address and THIS PC as the P2ATC PC. (If you don't know the IP addresses of your Windows 10 PC's, do this: Hold the WINDOWS key and press R In the box type CMD Press enter A black box opens with a DOS command prompt Type ipconfig press enter There will be a bit of guff floated up the screen. Your IP address is near the top and probably starts with 192.168 and some other digits. Write this down for each PC. Note: Most routers will allocate IP addresses to devices on the network for a period of time known as a "lease". This means that they can change from time to time. If, after a few days of working properly, your PC's don't communicate, check out their IP addresses again. This can be permanently fixed by allocating fixed IP addresses, but I will stick to x-plane in this post. Step Two Setting up Pilot2ATC The main process is exactly the same as on a standalone PC. The "gotcha" is exporting a Flight Plan to x-plane. For some reason known only to Microsoft, Pilot2ATC is unable to see a networked drive. Even mapping a folder on the x-plane PC to a drive does not show up in P2ATC when you try to select the flight plan folder on the other PC. What does work, is a networked share. Although there are many methods of achieving shared folders, this one is the safest and most reliable: On your X-plane PC, navigate to your main xplane directory and double click Output In this folder is FMS plans Right click this folder and scroll down to Properties Click the Sharing TAB at the top Then click the Share... button The next window has the cursor in an empty box. (Assuming your network is private) Type Everyone Make sure you select Read/Write to give P2ATC full access. Now move to the Pilot2ATC PC You will have to manually edit the config files to put the network share in them. We users are not supposed to edit these files (Dave smacks trev on the head!) so make a backup first! The file is (usually) located in C:\users\YOURNAME\AppData\Roaming\P2A_200\Settings It is called Settings.xml Use notepad (you DID make a backup, didn't you?) to open it. Use CTRL-F to seatch for XPlaneFltPlanPath Between the two <Value> enter your share file name. It will be something like: \\MYPC\fms plans Where MYPC is the network name of your x-plane PC (It can be found in Control Panel System). Your entry should look like this: <Value>\MYPC\fms plans<Value> Do exactly the same with FlightPlanFolder, which should be close by. You can test this setup by running pilot2atc (while the x-plane PC is switched on, you don't need x-plane running for this). Go into P2ATC's Config, choose the Flt Pln tab and you should see your two entries. Now create and save a flight plan. Go to the x-plane pc's xplane\resources\output\fms plans folder and the plan should be there. Now you can export a flight plan over the network to x-plane's GPS :) Conclusion Where you go to next is a matter of personal taste. I use the second PC right mouse button as PTT, some use a remote method. It's up to you. The networked setup is great as my x-plane PC is dedicated to the sim, while my other PC runs P2ATC without hindrance. A postnote on sound. Again this is personal preference and there are a dozen combinations. You can use a 3.5 mm jacked cable to connect output of one(P2A) PC to the input of the (x-plane) other, mess with the levels a bit and you have all the sound coming out together. You mike stays in the P2A PC, of course. I'm a musician for a living, so I have dozens of sound systems. I am using a rather "tinny" set of speakers for the radio (From the P2A PC), while my x-plane PC thumps out through a HUGE professional PA. No ButtKickers needed here, the walls shake! I hope this is helpful to someone. I recognize that other people will have different methods than mine (So don't Flame me!), I just wanted to share my solution so that it might help someone. And.... many thanks to Dynamo Dave for his instant help when anyone asks - what a pro -he really makes a great product outstanding! He must have 36 hours in his days.... (Dave - if this is to long, or you want to change it - go ahead!) trev

Another throught occurs to me.... I have the Garmin 750 trainer on my iPad (Along with R/W garmin stuff that connects to the systems in the a/c). Besides in the a/c, I can also use many apps on the iPad to connect to x-plane. Might it be possible to connect the Garmin iPad trainer to x-plane? This would not only solve the pop-up screen issue, but would turn the ipad into a touch-screen 650/750. You have the expertise between the trainer and x-plane/P3D/FSX through their interfaces. Maybe you can use the same know-how to talk from the iPad based trainer? I admit to being pilot, not programmer, so if this idea is rubbish I willingly accept I am wrong. It's a neat thought though? BTW, the backup problem at LR is solved and beta 11.05 is released. I assume this means that resources are now freed up for the SDK work. Kind regards, meach

It seems there are some delays at LR after a disk-backup issue with 11.05. I ams sure they will get the V3 SDK out as soon as it is stabilised. Moving to another monitor is certainly a key topic. I won't mention my desperate need for the G1000 here :) Moving the 750 to a second monitor will make it useable for many of us. I have disabled it for the moment, in spite of its beauty and functionality, it's in the way... meach

Hi Dan,You need to edit your FSX.CFG file, normally located in C:\users\"PC username"\AppData\Roaming\Microsoft\FSX(Substitute your username)look for the section called [DynamicHeadMovement] and change all the numbers to zero, as below:[DynamicHeadMovement]LonAccelOnHeadLon=-0.000000LonAccelOnHeadPitch=-0.000000RollAccelOnHeadLat=0.000000YawAccelOnHeadLat=-0.000000RollAccelOnHeadRoll=0.000000MaxHeadAngle=0.000000MaxHeadOffset=0.000000HeadMoveTimeConstant=0.000000If you can't find fsx.cfg, you might have to search your PC for it. It is a hidden file and the exact location depends on your OS version. I'm on Win7, which is teh example above.Kope this helps,Kind regards,Trev Meacham,Sydney, Australia

I built a full size cockpit and used a whole go-flight console (I think it was the "Commercial captain", or similar). It is outstanding, on FSX and Vista. I also used the PF yoke, matrox triplehead2go and lots of other stuff, building the cockpit and seating by hand. The go-flight gear is fully programmable and makes operating all the systems in the cockpit just like a real aircraft (IMHO). The only thing I didn't like was the go-flight throttle console, which seems to have cheap potentiometers, these gave spikes and failed calibrations. I also used the Saitek rudder pedals, which was a big mistake - should have used the higher-quality PF gear - which had the same cheap and nasty feel. The Saitek pedals have already been replaced, having been broken by a heavy-footed learner. The best go-flight gear is the radios, autopilot, FMS and various switch panels, all high quality with the right look and feel.BTW, the software does run fine in FSX, you can autoload it if you use the new version.Have fun!Trev

WARNING! The Triplehead2go now comes in 2 versions, digital and analogue. I bought the analogue verson for my cockpit and was extremely frustrated by the bezel misalignment. Basically, when you put several screens together, there is a physical gap between the edges (bezel) of each screen. Windows, and the TH2G see this all as one logical screen, without a gap for the bezel. When you bank, the horizons do not line up, giving an awful jagged edge. This has been fixed in the digital version, which includes "bezel management". Be warned!Kind regards,Trev

Sorry about the delay, some long flights... :-)No difference changing GA/USGA/Airline. In Airline, I still get the message "airline callsigns must be letters followed by numbers..". I even looked in the aircrafttypename XML file, where the abbreviatiation "hv" is changed to "heavy", so I tried adding hv. No joy. I tried all combinations, having to restart FSX each time (hence the delay). qantas427 correctly reads as "Quantas four two seven" but nothing else is accepted after the numbers.Incidentally... when in European airspace, Qantas is correctly pronounced "kwantas", but in Australia (Where Qantas comes from!) it's pronounced "Kantas". Any idea on this one?Also, ATCAircraft Type Name Editor crashes with the dreaded MS Message "ATCAircraftTypeNameEditor.exe has encountered a problem and needs to close. We are sorry for the inconvenience."I'm not trying to be painful, I really like this product!Any help would be appreciatedTrevor