TszChun

I am sure I have done everything required for the data link function. I have checked "Auto load simulator flight plan" in AS16, and selected "CREATE AND LOAD TO P3D" in FMC. The problem is just affecting the STAR waypoints. My procedure is... 1. In pre-flight stage, select and enter dep rwy, SID, and route into FMC WITHOUT selecting STAR. Then proceed WIND DATA REQUEST and DES FORECAST UPLINK 2. When approaching T/D, select STAR in FMC and confirm STAR waypoints are inserted in LEGS page, then proceed WIND DATA REQUEST and DES FORECAST UPLINK 3. The data link function is not adding wind data to those newly activated STAR waypoints, but just updating the data for non-STAR waypoints, as well as data in DES FORECAST UPLINK page My procedure should not be problematic since I don't have any issue when using FSX version of PMDG 777...

In response to your answer #3, I found that the waypoints after TOD cannot receive any wind data on request. They doesn't show up in AS16 flight plan page as well. That's why I suspect that there may be bugs in either AS16 or PMDG making data link function not completed.

That's exactly what I think! But last time I flied the 777, the STAR waypoints could not get wind data when I requested, while the others are OK...

Hello all, What do you guys think of the principle of data link function in PMDG 777. When I flied FSX, I used to use it with Active Sky in my every flight to get wind data and descent forecast. Here is my understanding of how the function works: I selected departure runway and SID, MANUALLY entered the route WITHOUT selecting STAR. When I clicked WIND DATA REQUEST in RTE DATA page, it seemed that a RTE file was automatically generated in documents/P3D v3 files/ by the 777 which was then read by AS16. After that, AS16 acknowledged my route by reading that RTE file, and created a WX file containing wind data of waypoints in PMDG/WX folder. The FMC loaded that WX file and display wind data in RTE DATA page. I would like to ask you guys two questions: 1. Do I still need to manually load the route into AS16 flight plan page? Or it will be automatically loaded into AS16 after I activate the route in FMC? 2. How come AS16 knows my attitude to reach waypoints when the RTE file generated does not contain expected FL? 3. If I modify the route in cruising stage, let's say adding a STAR at the end of the activated route, will I be able to REQUEST WIND DATA again for the STAR waypoints newly inserted? Anson

Thanks a lot Ben! My biggest concern is the VAS Management of P3D. How is your sim? Have you ever experienced memory leak, maybe when recording the videos and flying into complex sceneries for the cadet programme? Since the switching costs me a lot of money so I would like ensure that there won't be unreasonable OOM with REASONABLE settings in P3D which I experienced in FSX unfortunately:( I understand that P3D doesn't get OOM totally eliminated, but do you think P3D has a significant lower risk? I remember that you compared P3D with FSX flying into JFK(?), and you had got OOM in the latter...

Hi Ben, Just purchased 777 Cadet and nice to see you and Captain sparing no effort to make those informative videos. Having watched episode #2, I have decided to switch from FSX to P3D for better graphics, and most importantly better memory management as you told. However I have some questions about P3D that I would be grateful if you can help answer. In the video, you mentioned you could approach complex airports without getting OOM issue. I am very much interested in the settings you have applied to the sim since the memory issue drove me mad when I used FSX even though with low settings :( You also recommend FTX Global Vector in the video which is well-known as memory-hog, may I also know its settings as well so that I could active prevent OOM? I also notice that the graphics are very stunning! May I know how you configure anti-aliasing? Is Nvidia Inspector used? Nice to know you are going to upload resources in the next couple of weeks. Since your system should be very stable for producing this programme with the graphic settings somehow "approved" by Myron, I would be grateful if you could focus more on the simulator settings which will definitely help us to configure our simulator properly and resonably. Thanks very much Ben and Myron! Your hard work is much appreciated. Anson

Thanks for your reply! I would be thankful if you could upload your P3D settings as well. The settings are somehow "approved" by real world pilot Captain Myron Ashcraft therefore should be most realistic, don't they? Also, may I know whether you only got Predrag Drobac's preset imported to PTA without using its texture? Today he just released a newest preset in which sky textures and preset for something called "reshade" are also included. Thanks a lot! Anson

In the second video, a PTA Tool preset from a facebook group is introduced. Today I went there and tried to use it with the latest version of PTA Tool. Unfortunately the new version of the tool does not support the old presets including the one being used in the video. Also I can't find the version used in the video. I like the visual effects showed in video so much, so is it possible to upload that version of PTA Tool and the preset as well? Anson

To make it more accurate, the navdata contains head-to-radial-intercept missed approach at certain airports which causes memory leak. Anyway, I found that the memory does not leak anymore after I got Aerosoft MA EDDF v2 uninstalled. The sim just leaked vas along the flight from LOWW to EGLL even though EDDF was not orgin nor destination...

I am using FSX :wink: So strange is that after I did those four things, OOM suddenly came back at the route that I have never experienced any issue before Normally the VAS will be released a few hundreds MB while departing the airport with complex scenery, but now my sim doesn't do this...

Thanks for your reply. I would be grateful if you could read my words patiently :wink: I totally understand that the sceneries I was using were memory-demanding. The main point is that I have never experienced OOM, nor memory leak in cruising stage, at the same airports with the same settings and addons except the four I have mentioned: (1) Upgrading ASN to AS16 to ASCA; (2) Setting both Min and Max Cloud Draw Distance to 60; (3) Updating AIRAC Cycle to 1613; (4) Updating Orbx Libraries. To make it more accurate, the navigation data containing "head-to-radial-intercept" missed approach procedure, according to PMDG, may cause memory leak.

I have been flying PMDG 777 for almost 2 year, but never experienced such a huge memory leak. At the beginning of this year, I noticed that certain kind of missed approach was the culprit of memory leak in crusing stage, which was thankfully addressed by PMDG. Selecting STAR JUST before descent was one of the temporary solution mitigating the risk of OOM. Since then, I have successfully completed every flight without memory issue. However, after a long rest leaving flight sim behind, the memory leak issue occurs again! When I flew the 777 from LOWW to EGLL last week, I saw the VAS stably leaking around 400-500MB/hour when cruising. When the aircraft approached UK airspace, the sim got the Aerosoft's EGLL scenery loaded in hence the memory bounced suddenly to 3.8-3.9GB. The first thing I tried to do after the OOM was to lower both REX setting and TEXTURE_MAX_LOAD to 1024, then test the same flight. Unfortunately this did not do the trick, the VAS was still leaking at the similar rate. That's why I believe that the leak WAS NOT caused by graphic settings. Yesterday I tested another flight from EGLL to EDDF. 3GB VAS was used once I loaded the scenery which was normal, but I noticed that the memory was not released as soon as I climbed and left the scenery behind. Plus, the VAS leaked 400-500MB/hour as well. I could not completed such the short flight even though I disabled Aerosoft Zurich near EDDF by Scenery Config Editor. What I have done after I take the long rest were (1) Upgrading ASN to AS16 to ASCA; (2) Setting both Min and Max Cloud Draw Distance to 60; (3) Updating AIRAC cycle to 1613; (4) Updating Orbx Libraries. I have no idea why the OOM came back. The most suspicious culprit I guess was AIRAC cycle because it has been the cause of memory leak before. In addition, when I flew the 777 from EGLL to LOWW, the VAS stayed almost constant when cruising. But while flying from LOWW to EGLL, and from EGLL to EDDF, the memory leak stably even though nothing big got loaded in in crusing stage! Is it possible that entering certain airports into FMC as DEST or ORIGIN was anither cause of memory leak? I would be grateful if you guys could help testing the aforementioned airports to see whether memory leak was observable? Anson I have FlyTampa Toronto but never successfully completed a flight to there...

Hello all, I have been flying PMDG 777 for almost 2 year, but never experienced such a huge memory leak. At the beginning of this year, I noticed that certain kind of missed approach was the culprit of memory leak in crusing stage, which was thankfully addressed by PMDG. Selecting STAR JUST before descent was one of the temporary solution mitigating the risk of OOM. Since then, I have successfully completed every flight without memory issue. However, after a long rest leaving flight sim behind, the memory leak issue occurs again! When I flew the 777 from LOWW to EGLL last week, I saw the VAS stably leaking around 400-500MB/hour when cruising. When the aircraft approached UK airspace, the sim got the Aerosoft's EGLL scenery loaded in hence the memory bounced suddenly to 3.8-3.9GB. The first thing I tried to do after the OOM was to lower both REX setting and TEXTURE_MAX_LOAD to 1024, then test the same flight. Unfortunately this did not do the trick, the VAS was still leaking at the similar rate. That's why I believe that the leak WAS NOT caused by graphic settings. Yesterday I tested another flight from EGLL to EDDF. 3GB VAS was used once I loaded the scenery which was normal, but I noticed that the memory was not released as soon as I climbed and left the scenery behind. Plus, the VAS leaked 400-500MB/hour as well. I could not completed such the short flight even though I disabled Aerosoft Zurich near EDDF by Scenery Config Editor. What I have done after I take the long rest were (1) Upgrading ASN to AS16 to ASCA; (2) Setting both Min and Max Cloud Draw Distance to 60; (3) Updating AIRAC cycle to 1613; (4) Updating Orbx Libraries. I have no idea why the OOM came back. The most suspicious culprit I guess was AIRAC cycle because it has been the cause of memory leak before. In addition, when I flew the 777 from EGLL to LOWW, the VAS stayed almost constant when cruising. But while flying from LOWW to EGLL, and from EGLL to EDDF, the memory leak stably even though nothing big got loaded in in crusing stage! Is it possible that entering certain airports into FMC as DEST or ORIGIN was anither cause of memory leak? I would be grateful if you guys could help testing the aforementioned airports to see whether memory leak was observable? Anson

I just completed a flight from LOWW to EGLL after installing AS16 + ASCA without OOM. I still saw VAS leaking during the flight, but I noticed a dramatic loss of VAS when flying through airspace above Frankfurt where I had got Aerosoft's scenery installed. I wlll now try to use scenery configurator to disable that and see whether the VAS loss will disppear. To those who are using FTX Global Vector with Scenery Configurator, may I know if I should run Airport Elevation Correction Tool everytime I disable a scenery? I am used to run the tool once I install a new scenery to ensure it works without elevation issue, but I wonder if I should do so after activating or deactivating the sceneries I have already installed...

I just completed a flight from LOWW to EGLL after installing AS16 + ASCA without OOM. I still saw VAS leaking during the flight, but I noticed a dramatic loss of VAS when flying through airspace above Frankfurt where I had got Aerosoft's scenery installed. I wlll now try to use scenery configurator to disable that and see whether the VAS loss will disppear. To those who are using FTX Global Vector with Scenery Configurator, may I know if I should run Airport Elevation Correction Tool everytime I disable a scenery? I am used to run the tool once I install a new scenery to ensure it works without elevation issue, but I wonder if I should do so after activating or deactivating the sceneries I have already installed...