macwino

My Aivlasoft remote machine setup using the latest 1506 AIRAC database shows an ILS for Runway 17 at KPBG when the real world charts indicate that the only ILS for this airport is for Runway 35. Aivlasoft shows no ILS for Rwy 35. I contacted Navigraph about this discrepancy and they assured me that the Aivlasoft AIRAC data for this ILS at this airport is correctly entered as Rwy 35. Specifically, they tested it on their copy of EFB and also had me check the KPBG.txt file in the SIDSTARS folder in the Aivlasoft folder in the main P3D v2 folder. Indeed, this data file correctly shows that the ILS is for Rwy 35. Yet when I use the EFB on my remote machine, it shows only an ILS for Rwy 17. I get no runway error message when I enter this airport in EFB. I have checked my path in the Navigation Data settings tab and it is directed to the folder described above. The installed AIRAC cycle is 1506 v2. I updated the scenery database but that made no difference. Can you let me know what might be wrong with my setup. Thanks, Robert

Now I understand how to do it. Thanks so much for the detailed explanation. This will revolutionize my use of EFB. Robert

Hi Urs, I thought I"d piggyback on this post and ask a follow-up question that's been on my mind for some time now. I follow the procedure you've shown. I then make my selections after viewing the data. Then I go back to the Route Setup tab and implement my selections using the pull down menus. My question is whether I can activate my selections from within the Select SID tab or the Select STAR tab. If there is a way to do this, I've not been able to figure out how it works. Your assistance will be appreciated. Thanks, Robert

The flightplan will be in the mail shortly. I'm using the 1106 AIRAC cycle. To be clear, the "route only" box was checked on opening the Direct To window, so that's not the problem. It was only by cycling it on and off and selecting random waypoints that I was able to get the OK button to activate. You stress that it's designed for the "Garmin GPS." That may be the problem, but I'm not sure. Here are the details. The plane was the Flight 1 Cessna Mustang, which has its proprietary version of the G1000. It imports, displays, and follows the EFB flightplan designed for the Garmin GPS without any apparent problem. The strange behavior I encountered seems to have been entirely within EFB, as far as I can tell. But I will try the plan with another plane using the default FSX Garmin GPS and let you know how that goes. In the meantime, let me note again for clarification - now that I've thrown this monkey wrench into the mix - the G1000 mirrored whatever was displayed in EFB. In other words, the first Direct To, even though not the waypoint I selected, was incorrectly displayed in EFB and was incorrectly but identically displayed in the G1000. Similarly, the inability to change the Direct To to the correct waypoint was reflected in both EFB and the G1000. Thanks for looking into this. Robert

I tried to use the Direct To function and it did not operate the way I expected it to. I had programmed a Departure that took me on an extremely circuitous route to my first Enroute waypoint. After takeoff, I decided to try and circumvent the Departure route by entering a Direct To to the first Enroute waypoint. This is where I encountered my first problem. I selected the first waypoint for the Enroute portion of my flightplan but I could not get the OK button in the Direct To window to activate. It remained grayed out. Eventually, I was able to get the OK button to activate by unchecking and rechecking the ""Route Only" box and perhaps also selecting different waypoints. I was clicking lots of things. Once the OK button was highlighted, I then checked and made sure my waypoint selection was the one I wanted - the first waypoint on the Enroute segment - and then pressed OK. This is where I encountered my second problem. The waypoint entered in the flightplan was not the waypoint I had selected, but the waypoint before it - the last waypoint in the Departure. And the plane flew to that waypoint, not the one I had wanted. I then tried to do another Direct To, this time selecting the waypoint after the one that I really wanted to fly to, in other words the second waypoint on the Enroute segment, thinking that if the program would default to the immediately previous waypoint I needed to select the next one beyond it. I again had problems getting the OK button to activate. Eventually, it did, but I was never able to get a new Direct To routing to take effect. I was locked into the earlier erroneous waypoint which could not be changed. Selecting a new Direct To waypoint and pressing OK had no effect on the route. Can anyone tell me what's going on here? Are my expectations skewed, did I forget to do something that I should have, or is there something wrong with what I experienced? Three questions seem appropriate: 1. Why do I have trouble activating the OK button? 2. Why did the program select the waypoint before the one I wanted? 3. Why can't I enter a second Direct To when the first one needs to be altered? Thanks, Robert

Travis, your post prompted me to check out all the runways at CYYC, as I couldn't remember the particular one that I was using. All the data was there within EFB. Must have been a one off glitch last night. It sure was a pain to have to locate a chart over the web at the last minute. Sure made me appreciate EFB. Thanks for your thoughts. Robert

I flew to CYYC last night and the airport data page was essentially devoid of data regarding the ILS approach I"d selected. There was no vertical profile, no ILS frequency and course, etc. There's no mention of this airport being a problem on the Navigraph board. Before posting there, I thought I'd check and see if this might be a problem with EFB's processing of the data. Any ideas where the problem lies? Thanks, Robert

I just installed the demo version of the program. I installed both v1.3.1 and the SP1. I am using a client machine for the Display Unit and have installed the DataProvider app on the FSX machine. When I launch the DataProvider app it begins a scan of the drive. It generates several errors during the folder scan, and when it shifts to the building of the index the app says the index can't be created and shuts down. There doesn't appear to be any log of the process. If I relaunch the app the exact same thing happens. What might be the problem? Thanks, Robert