bobsk8

OK, thanks, will check the status.

Since the last update, and I updated both, I get a really loud buzzer sound when the Client starts and sever is already running. Is something wrong ?

I had made some changes recently. After I posted this, it started working normally again, so that must have been the issue, ' Thanks,

"simulator configuration has been changed would you like to rebuild data base," is the message I get every time I start sever. I rebuild the data base, everything seems normal. And next time I start server, I get the same message, P3D version 3.4 EFB works perfectly other than that. If I check the "no"box, that I don't want to rebuild data base, the sever loads, and it seems as if everything is normal. This just started a week or two ago ,

I think I found the problem. I had wind lock on in AS 16 for ATC arrival. I turned it off, and now wind is correct.

Still having problem with weather at landing airport. wind only. Using AS 16. Just landed at KSJC, EFB said the wind was 170 at 4 knots. The baro pressure is correct, temp OK, but the wind is not correct. AS 16 has the wind at 360 at knots, alng with two other programs that I use that report the wind, like landing rate monitor. . I have tried hitting the refresh button, but the wind is stuck under the arrival airport on the right side of screen. By the way , The AC ambient wind is correct at 000 at 6 knots. This happened yesterday to, on another flight where landing airport wind was reported incorrectly. clientLogfile.txt clientLogfile-1.txt

Working fine, only did that once.

Will keep you posted, probably a hiccup.

Not sure if this is relevant, but I ran latest EFB ( server and client) update this morning. Shooting approach to KMSY, MY ATC program ( PFE) had the correct wind 070 at 9mph, and so did AS 16. The wind indicated in EFB was showing 270 at 12 knots. I have never had this happen before. Any ideas ?

You are a genius ( applause) That was the problem. Even though I disabled the add on scenery for KMSP, which is problematic apparently, it was still being read by EFB, whbich was listed on the "info" page ( took me awhile to find that) I removed the add on scenery from the folder, totally, reran the DB builder, and now everything is working. Thanks. Great support for EFB.

Only this airport has this problem. I always use the Q400. I have scan all sceneries checked. I disabled add on scenery by deselecting it in P3D scenery menu. I disabled My Traffic scenery with that airport by naming the bgl. passive. So the only scenery that should be active now is P3D default for KMSP. Only thing that has me confused is I can't locate the default bgl for KMSP.

I had an add on scenery for KMSP. I disabled it, ran DB builder again, and now have just stock P3D v 3.4 KMSP scenery. Prfl filter on/off no difference. P3D sees all the airline Gates, A though G. PF3 assigns correct Gates when landing. Moving map shows all gates, with AI aircraft parked at some. It is just the Taxi list, that only shows general Aviation Ramp numbers. Client_201902101604.txt.zipServer_201902101604.txt.zip

At KSMP airport, the moving map shows all the parking places and gates from A to G. When I go to the Taxi menu and check Taxi in, all I see is GA ramp parking places. Any solution. I have rebuilt the data base in P3D .

I fixed it. Turned out that something must have happened to my default KPIT Afcad. When I launched KPIT from the P3D menu, it was using My Traffic 6 KPIT BGL. I guess that EFB doesn't like that, so the airport and all teh taxiways etc. never showed up in EFB, just the aircraft and the AI . I downloaded a new version of KPIT, and now everything works.

Fly EFB all the time with P3D version 3.4. Tried a flight from KDCA to KPIT, and EFB says it cannot find the destination airport. I rebuilt database, and still no luck. I can go to KPIT in P3D with no problem, so the KPIT scenery is correct. I can also load up Plan G3 moving map, and it shows KPIT and my aircraft at the proper place. I just updated Navigraph to the latest version, and I am wondering, could this problem of EFB not seeing KPIT, even if I search for it in the EFB airport menu, be caused by a Airac issue? Not sure how to troubleshoot this problem. Just seems like EFB cannot see this airport.

Took me 0.3 seconds to find this using Google. https://www.windowscentral.com/how-exclude-files-and-folders-windows-defender-antivirus-scans https://www.technipages.com/bypass-download-failed-virus-detected-messages

Just to see, I downloaded server with Windows 7 and Webroot total protection and scanned the file after. Comes up clean, and Webroot is an excellent Antivirus.

Get Simbrief. It is a flight planner, free, and exports to just about any addon including EFB V2 https://www.simbrief.com/home/index.php

If you use Simbrief for your flight plan, you can export the plan with one click into both EFB V2 and PMDG as well as a couple of dozen other aircraft using the simbrief downloader . https://www.simbrief.com/home/index.php

Yes, I m going to test this for a couple of days to make sure it works. What I added in the file exclude section is these two lines, since all the My Traffic BGL files share these two prefixes. If my logic is correct, this will allow EFB to use the updated Afcads from Herve Sorves without being overwritten by the non updated MT6 bgls. file:AF2_* file:BR2_*

Yes, AF2_ and BR2_ Now I can figure it out . Thanks.

Great idea. I will do that. The My Traffic Bgls are located in C:\My Traffic Professional\My Traffic\scenery Not clear on how I should enter that in the exclude file.

Yes MT6 does provide it's own BGLs, and the problem occurs because the bgls for My Traffic are higher in the scenery priority listing than all the default airports, so the things like ILS freq are then controlled by the My Traffic BGL, and are not updated, when running the Sors ILS updates, because Sors doesn't update the MT6 bgls are any other add on scenery bgls. . So anything other than the default is stuck on the old frequency. So if the initial default for an airport in the sim for ILS rwy 10 is 110.0, then MT6 will be 110.0 , If you run Sors Navaid update and it updates the ILS freq for that airport runway 10 to 120.2, only the default is changed to 120.2, but the MT6 is not updated, it is still on 110.0, and 110.0 is what EFB reads as the ILS freq. because MT6 BGL has priority. Since the default has been changed to 120.2, by Sors, if you tune your Nav receiver, to 110.0, ( the old freq listed in MT6) you don't get the ILS. Hope that makes sense. Two solutions, edit the MT6 BGL and change ILS freq to the new freq, or disable the MT6 BGL for that airport, and the updated new ILS will take over. You have to update the EFB database when you do that so it reads the new ILS freq.

Yes don't normally disable BGL's, but My Traffic 6 since it is mainly for AI tgraffic on the specific airport, really doesn't cause any problems. When I have time I will fix the MT6 ngl for the airport and enable it.

Just discovered something today, when flying into EETN airport. The ILS frequency was incorrect on both end of runway, even showed up on the P3D map as incorrect. I then found out that the frequency had been updated to 108.3 and 109.3, but the frequency listed in EFB was the old frequency. Since I use Herve Sors ILS update, I couldn't figure out why P3D and EFB was listing the old frequency which no longer functioned. Then I found a post, regarding someone that had a similar problem about a year ago and it turned out that the Sors update only updates default Frequencies. If you have any add on airports or programs like My Traffic 6 ( which I have), these will not be updated. I looked at the My Traffic 6 BGL for EETN, and sure enough, the old frequencies were listed. Since MT6 is higher in the scenery listings, than the default airports, when running Make Runways and the EFB DB rebuilder, it took the MT6 ILS frequency for EETN rather than the new updated one which is the one that worked. You can either edit the MT6 BGL for EETN, changing the ILS Freq to the new ones, or what I did, was just mark the MT6 EETN as passive to disable it. Then I ran make runways, and then the EFB DB rebuilder, and now the correct ILS frequencies are listed in EFB for EETN. Just thought this might help anyone running into this issue.