Osirith

👍👍👍

Ok, thanks Dave. I will try my "Country/Regional" setup for my next flight between 2 or 3 countries. For transoceanic ATC : I think it would be a nice feature to have for a future version of Pilot2ATC. It involves adding a "zone" feature in the sim, allowing to define a geometric zone related to a chat folder. Other ATC softwares (for example, Pro-ATC-X) are doing that. Pilot2ATC is far more complete on several aspects, this feature would be nice to have. And for version after, an implementation of NAT routes 🙂 (ok, maybe I am asking a bit too much)

Thanks Dave for your reply 🙂 I think I will use the Country structure, and duplicate the Regions Controllers folder from ATC-X-Chatter in each country where I do not have enough country sound files. That way, all "generic" countries will use the Region sound files provides by X-ATC-Chatter. Will involve many files duplication but using Windows symbolic/junction links, will avoid real duplication. Another question : do you have an advice on how to use oceanic chatter (Gander, Shanwick, ...) used when crossing Oceans ?

Hi all, I own and use Pilot2ATC and X-ATC-Chatter with Flight Simulator (2020) and really enjoy it with all my IFR flights. God job and expecting new versions :) I would like to add more mp3 files in the chatter. I have a lot of those MP3 files and would like to add them for use. Now the combination P2ATC/XATCChatter uses regions folder, with Controllers folders inside each regions. I would like to add specific Countries and Aiports folders for some countries and some airports. Is it possible to do that in a way that Pilot2ATC understand and use ? For example : - ATC_Chatter |__ Regions |__ United States |__ Europe |__ Controllers |__ (...) |__ France |__ Controllers |__ (...) |__ LFPG |__ (...) |__ Africa |__ Asia Is it possible ? or with some other structure ? which Sound Source option should I use in Pilot2ATC ? (Country Folder -> no Regions ?? Aiport Folders ? Controller Folders ?) Thanks for your help Chris

Hello, I am using ProATC-X on all my flights since years. I am using P3Dv4.1 and never had a single P3D CTD. However, I sometimes have a ProATC-X CTD but the function "resume from last crash" works like a dream and allows me to continue the flight without problem with ATC. Regards Chris (just realized that I need to update my sig)

Also, changing registry entries will not be enough... You also need to modify every line in every parameter files used by FSX or add-ons where the drive letter is written. Exemple : inside fsx.cfg (for modules path), inside planes config files, etc... Could be a very time-consuming, trial and error work in order to not forget anything...

Short update to my previous message about successful migration to Win10 ; Did a long range flight this week-end : 11 hours without acceleration or pause, from Rio de Janeiro to Paris Charles de Gaulle, in Pmdg 777/200, with following configuration : - FSX , DX10 Scenery Fixer + NVidia Inspector + EZDok - Orbix FTX Global + FTX Vectors + FTX Global OpenLC Europe + REX4 Texture Direct - Active Sky Next - Pro ATC-X - Professional Flight Planner X - Paris Photo HD scenery, Paris LFPG Mega Airport scenery Absolutely no problem.

If you fly offline (ie not with VATSIM or IVAO) and don't mind having an outdated navigation data, you can just buy a one time update. You will have up to date/accurate nav data for this month, and the data will just slowly become a bit inaccurate every month, but at least all you add-ons (FMC from PMDG, flight planners, ATC, ...) will use the same data, based upon your month of subscription/update. You only need a yearly subscription if : 1) you want to fly online because online ATC will use freshly updated nav data or 2) you want to fly the most recently updated sid/stars/routes. I just bought a 1-time (1 month) suscription in August, allowing me to update my nav data for : Pmdg 737 and 777, Aerosoft Airbus, PRO ATC-X, and PFPX. All those add-ons now share the same nav-data. Chris

Hello all, A recap of my own experience about Windows 10 migration. Installed Win 10 Pro from Win 8.1 Pro on July, 29. Install went with no problem and system is working fine. My hardware config : - CPU : Intel I7 4790K - GPU : Asus STRIX GTX980 - RAM : 16 Gb - Disk Drives : - Win 10 on 1st SSD - FSX on 2nd SSD - Add-ons that does not need to be inside FSX folder are on a Hard Disk Drive (3 Tb 7200) - Screen : 27" / 2560*1440 - HOTAS Warthog + Saitek Pro Flight Rudder pedals I did have a few problems with my FSX install : all was working fine at start but I had multiples crashes to desktop after 10-30 minutes flying, that never occured before. As the settings were untouched (exemple : HIGHMEMFIX=1 in fsx.cfg, an UIAutomation Core.dll in install dir), I had no clues about what was the problem. I decided to completely uninstall and reinstall FSX and all add-ons from scratch on my new Win 10 system. Took me a while. The main add-ons that I am using are : - FSX Gold - DX10 Scenery Fixer + NVidia Inspector - Orbix FTX Global + FTX Vectors + FTX Global OpenLC Europe - REX4 Texture Direct - Active Sky Next - Pro ATC-X - Professional Flight Planner X - FSCaptain - EZDok - Aerosoft Airbus - PMDG 737, 777/200 & /300 - several payware and freeware large airports As said, the full reinstall was a lenghty process... Most/all of the tricks of a good install on others systems were used (HIGHMEMFIX, UIAutomationCore, DX10 SceneryFixer for DX10 Preview, changing several parameters inside fsx.cfg, installing with admin rights and setting FSX.exe with Admin Privileges, ...) but the result was worth it. I now have a fully functionnal FSX with all add-ons reinstalled and working nicely. I blocked framerate at 30 with high-end AA settings in FSX/DX10Fixer/NVI, and result is very smooth (probably not different from what I had previously on Win 8.1). Only problem remaining so far : Mouse Wheel zoom is not working correctly or not working at all, depending on which setting I use inside FSX, EZDok, FSUIPC. Still need to work on that, I am not totally sure it is Win 10-related, maybe I fumbled with the settings... In summary, I am quite happy with FSX on Win 10 so far, no compatibility problem for me. Chris

Bought, downloaded and installed this morning just before leaving home to work... As a long time DX10-only user, I already use Steve's free patch and know which add-ons I own that have problems. Just made a very quick test before shutting down home PC. - MegaAirport Munich EDDM is working (no more grey buildings at dusk/night/dawn, and no more grey airport vehicles). - FTXGlobal vector lights are working (I renamed back the disabled texture file) - Skiathos X (Aerosoft 29Palms) is working (no more black boxes for night lights, same as FTXG problem I guess). So far it's a big thumb up, I still need to test a lot of other add-ons... A bit disappointed if FT/Dubai is not totally working, hope for a fix from FlyTampa side... Chris

Hi, seems that Lufthansa is still quite Airbus-oriented if you look at the current fleet : http://www.airfleets.fr/flottecie/Lufthansa.htm (column "active") Besides 32 B737 and 31 B747 (+18 MD 11), the remaining of the 313 airplanes fleet is only Airbus (including 10 A380). The B777-9 delivery will increases a bit Boeing share but if you add the 25 A350-9, balance is still heavily on Airbus side... Chris

Can't wait also Flying with DX10 exclusively since many months, but the Fixer should solve my last gripes with this mode : many airport add-ons "grey buildings or vehicles" and light fixing, FTX Global black boxes lights, ... I will at least be able to use night flying without most (or any) problems still arising today...

Thanks guys for your comments ! Well... In fact I had a crash just a few seconds before landing... I just did a short flight Seattle to CYVR to take the last pictures of the flight. When the crash occured I did not research the cause and I am not sure it was an OOM. I almost never have crashes with FSX since months, and never had since this flight (but I did not do long flights (no more than 2 hours) since this LFPG-CYVR flight). Since then I have read many posts about possible OOM problems with 777 and I will investigate that. My next long range flight is scheduled for this week-end. For my next mid/long range flight tomorrow (probably a Vienna-Dubaï, I own both airport add-ons), I will use Process Explorer to survey the VAS value. Chris

A few more pics borrowed from the hard disk, from the same flight : Overflying EGGL (Heathrow) among scattered cloud layer : Greenland snow everywhere : Northern Canada :

Thanks for your link to this map :rolleyes: I was parked at gate 2 if I remember well... Chris

Hello You could be right. I am not familiar with this airport and the definition of différent gates is not given in my FSDreamteam CYVR manual... When I activated GSX after landing and chose a gate, I did it at random :blush:

Thanks for your comments ^_^ Talek, FPS vary a lot depending on several factors, of course. I am using a quite high screen definition (2560x1440) with mostly hign end settings for FSX, and Paris CDG is not very framerate-friendly (compared to some other large airports). But i also use Ulitmate Traffic 2 with 50% traffic load, and it means a lot of planes in or around CDG. You can see the FPS counter on most of the pics (large yellow number on top right corner). Near LFPG, numbers are ranging from 26 to 10 FPS (10 inside cockpit at entry of runway, looking towards the busy airport area). Most of the time, I have between 15 to 25 FPS around CDG...

Ground control asks us to park at a Terminal A gate on the other side of the airport. Being not very familiar with the area, we ask for a Follow Me car. After some minutes of taxi around the aiport, we eventually reach Terminal A and our parking gate. Ground crew and vehicles are ready to take care of the plane. After last turn, we slowly get close to the parking signal, trying both to not overrun the stop line and to be as much aligned as possible. 5:17 PM French time, 8:17 AM Vancouver time. Cabin crew is managing the exit of passengers towards the arrival area of the airport. Passengers will be a bit tired today, they arrived more or less at the same time they departed France (-9 hours shift between time zones) ! While the pilot and FO are busy shutting down the main systems, catering ground crew handle the cargo and passengers luggage. This concludes our Paris - Vancouver flight. I hope you enjoyed the ride on Air France (PMDG)777-200 and will be happy to welcome you on a next travel B) Chris

Our plane is now ready for landing, approaching minimums with full flaps. I will do a manual landing, so I disconnect auto-pilot while leaving auto-throttle enabled. Mount Baker can be seen behind the plane. The tail view below allow us to see Richmond suburbs below the plane, the northern arm of Frazer river above the right wing, and Vancouver Intl airport and 26R directly in front. Nice view on the bay behind. View from the cockpit on short final. doing a last correction to the path towards the runway. Altitude is a bit higher than optimal glide path but nothing serious. Almost there... Passengers can spot the different airport areas, parking lots, and the traffic of other aircraft on parking and taxiways. The cockpit crew is still busy landing the plane but with a near perfect attitude and glide slope and low (9 knots) frontal wind, this is quite easy. Touchdown ! After 9 hours and 31 minutes, we land at Vancouver International airport. Spoilers and brakes are used automatically and pilot commands the reversers, as seen from the cabin. Post 8 : Vancouver

We have contact with CYVR approach and we will be vectored towards runway 26R (funny, same exact runway heading as the one we departed from at Paris Charles de Gaulle) Runway, flaps setting and ILS are entered on the CDU. Encountered a bug (I think) with an error message on the screen about incorrect rwy/ils frequency. Found the solution on PMDG forum (thanks to Pause function during the flight) : need to erase the frequency M line on the CDU RAD/NAV page and all went well afterwards. Starting turn towards the runway under guidance of ATC. First levels of flaps are already down and speed is rapidly decreasing. Now on the ILS glide, speed is low enough to lower the landing gear as we pass nearby a golf course in a residential suburb (FTX Global). Post 7 : Landing Post 8 : Vancouver

Still 40 minutes to go before reaching Vancouver. ATC gives clearance to start the descent phase, so after checklist and approach briefing, we lower the altitude value on the MCP and start the descent. We fly over one of the numerous lakes on this part of Western Canada. Air traffic and radio calls becomes more heavy now as we reach more civilized areas. The descent part is done without any interesting event and we are now near Vancouver area. Approach phase is near and we wait for the local ATC message to enter the arrival runway and choose a STAR or a vectored approach. Vancouver could be seen behind the plane. Post 6 : Approach Post 7 : Landing Post 8 : Vancouver

Uneventfull first part of the flight, we cross the largest part of England, overflying Heathrow airport and center of London. After leaving northern england shores, clouds are becoming more numerous below us, and so it is difficult to spot Iceland shores just below the right wing. Crossing the huge and icy land mass of Greenland takes some time as we also try to hear the distorted radio messages from long distance calls of ATC. Some snowy peaks emerge from the cloud layer. Almost 5 hours after take-off we reach the northernmost shores of Canada (Baffin island), then we fly above the northwestern passages and near the north edge of Hudson Bay. Landscape view is fantastic albeit very bare and wild. Post 5 : Descent Post 6 : Approach Post 7 : Landing Post 8 : Vancouver

Hello Rick, thanks for your comment. Never flown in a 777 myself (many other Boeing and Airbus). About PFPX display ; curious, this is a quite standard display of the flight plan, not sure what you are doing incorrectly. __________________________________________________ After a few minutes, we reach the first turning waypoint of the flight plan and we start a right turn towards OPALE. The sun reflects on the Seine river and people accustomed to French geography will be able to spot Le Bourget airport under the aircraft (LFPG being further away below right wing near middle of screen), and Paris on the right part of the pic. The weather is quite good with just some scattered clouds. Area traffic control allows us to climb quite quickly and we soon cross FL200 and upwards. In this area between Paris and London the air traffic is very dense and we spot a lot of nearby flights both on TCAS and visually. This looks like a very nice trip so far ! Post 4 : Cruise Post 5 : Descent Post 6 : Approach Post 7 : Landing Post 8 : Vancouver Chris

Tower gives clearance to enter and hold at start of 26R. Last check list is done and we line up on the runway. Note a Caution light I have been unable to erase for the whole duration of the flight (maybe my lack of knowledge of something, not sure, as there is no warning messages on the screens). The beginning of the flight route can be seen on the map display, using OPA2BE SID towards OPALE, with a sharp right turn after take-off. We then get the take-off approval from tower, push the levers and arm the auto-throttles. The Triple Seven quickly reach the V1/VR speed (amazing power even with quite heavy TOW) and after rotation the main landing gear leaves the ground for a planned flight of nine hours and 30 minutes... Note another Air France flight (A319) that just landed on parallel runway 26L. We gain altitude quite fast abd soon have a good view of the Terminal 2 area of the airport. We can notice that our parking gate is already taken by another flight (above the right wing, bottom terminal is 2B and just above is 2D where we entered the aircraft 40 mns ago). Post 3 : Climb Post 4 : Cruise Post 5 : Descent Post 6 : Approach Post 7 : Landing Post 8 : Vancouver

Hi all, this is my first long range flight with the new PMDG 777, after practicing the tutorial flight and a few short range training flights. I did choose a Paris Charles-de-Gaulle (LFPG) to Vancouver International (CYVR) direct flight with Air France. This is a fictitious flight, Air France network does not serve Vancouver (the sister compagny, KLM, do it with 777-200ER from Amsterdam however). Planning The flight has been planned with PFPX. Here is the overall flight path shown under PFPX. Flight path will overfly England, touch the south coast of Iceland, cross southern part of Greenland then enter Canada North of Hudson Bay before reaching Pacific Coast and Vancouver. Weather should be good to average most of the time, some scattered cloud coverage on take-off and landing (AS2012), and mild overcast enroute, mostly on the middle part of the flight (above Greenland). As I am quite new both to PFPX and PMDG 777, I barely touched the ETOPS planning part. I will not set any failure probability for this first try so I know I will not need to land on an alternate airport. Parking at Roissy Charles-de-Gaulle (LFPG) : 7:55 AM local time. The plane is parked at Aerogare 2 (Terminal 2D) nearby other Air France planes. Setting is Cold & Dark, low sunlight is touching the planes coming from the horizon. Time to power up the bird. Following standard start-up sequence, the doors are also opened to allow catering crew to replenish food, drinks and other stuff to be spent during the cruise (GSX). 30 minutes are well spent to power up all the systems, enter the flight plan and plane parameters for the flight, while the cabin crew manages the passengers boarding. Fuel loading is 68,223 Kgs, 220 passengers are aboard as well as 10,000 Kgs of cargo. TOW will be 254,789 Kgs. Flight duration should be roughly 09h26 (depending on traffic at start and arrival, ATC guidance and possible weather change). Cruise FL will be initially FL360, with two subsequent step climbs to FL380 and FL400. 08h22. Time to start the push-back procedure and to start engines. Clearance has been given by the ground control (Radar Contact v4). Take-off runway will be the 26R, and given the large size of LFPG perimeter, this will take some time to reach it. No time to lose. All doors are armed and the ground crew start the push back sequence. Ground traffic is quite heavy at Charles-de-Gaulle and more than average at this time of the day. Taxiing The Triple Seven is slowly pushed on the taxiway. On the rear of the plane can be seen the main offices of Air France , among several hotels. While push-back continue, both engines are started and the push-back crew and vehicle return to park area after removing the safety pins. Ground control gives clearance to start the taxi trip towards 26R. We are crossing a large pack of EasyJet (low cost) A320 as we leave the Terminal 2D area. We then turn around the Terminal 2 and pass by the whole length of it towards 26R. Preparation check-lists are done during the taxi phase and we reach the runway perimeter after 10 minutes and some ground traffic. Take-off will use derated parameters (weather and runway length allow it). We have some time to watch landing and departing traffic using both south runways near our plane (here an A319 landing on 26L, while two aircrafts are in front of us preparing for take-off on 26R. (Next steps will be posted very soon). Post 2 : Take-off Post 3 : Climb Post 4 : Cruise Post 5 : Descent Post 6 : Approach Post 7 : Landing Post 8 : Vancouver Happy reading ! I hope you enjoy the travel. Chris