jfmitch1716

I have removed Navgraph FMS Data and am running only Nav Dta Pro now and the warning is no longer there. All is now OK. Thank you very much , you have been a great help. Jim

I have updated Navdata for the 2210 cycle and yet the same screen warning appears. I have attached the cycle_info.text and the D Base Builder. I also have attached the DB Manager.

Here you go.

Yes I did

Yes. I must now add that I just started P3D. and EFB is now working. I got the same warning as before that the server, it is telling me that a new version is available (build 1.22).

I had both the server and the Client on drive D. When I updated I forgot this and they ended up in C drive. How can I get rid of the files on D drive plus the registry key would be pointing at the wrong set of folders. Sorry for being such a complete ass but it's the stroke I had a few years ago. My FSUIPC is version 6. JIm

I seem to have the same problem with P3DV5.3 Every time I start EFB server, it tells me that a new version is available (build 1.22). but when I start another instance of EFB server, it tells me again that a new version is available. AS-2210/R1 is now loaded but it opens at Zurich every time and does not connect P3D and the EFB Client. I did have two instances of each (the server and the client) but changed that. Should I dump all the files and start anew? Client_202210302303.txt.zip Server_202210302303.txt.zip

I had to re-click on ACFT button to get it to appear.

Right now I am helping test the building of P3DV5 airports and also have P3DV4 loaded for flying. How do I go about switching the database for each version of P3D? Does this happen automatically after one turns on V4 or V5? Do I have to open EFB2 Database Builder every time to select?

Thanks much. Maybe a chance o add a warning next time. A lot were vfr routes

Had to reload EFBV2 and was surprised that all (approximately 500) my flight plans are now missing. Where are they?

OK I changed the add-on cfg as you stated. I cleared EFB from my computer and ran the Server installed OK.. Client installed OK Everything is working well. Vielen dank fuer all ihre hilfe bei diesem problem. I was with NATO and lived in Baden Soellingen from 1972 to 1976. Loved Germany.

You will note that two Simaddons packages are number 0 and 1 as you mentioned above and suggested they be moved to C:\ProgramData add-ons.cfg.bkp.txt Both the scenery.cfg folder and P3D5 are on my computer

Here is the add-ons.cfg. Simaddons assures me " It has nothing to do with Simaddons. For a test delete all inside the file add-ons.cfg and run the EFB stuff new. " I did as suggested and wen I tried to create a new database Next was greyed out add-ons.cfg

Here's the scenery.cfg scenery.cfg

OK same original error but got the two files you requested. Also added serverSettings.txt and noted missing hash codes Server_202004281533.txt.zip Client_202004281533.txt.zip serverSettings.txt

Got another error running Supportfiles.exe https://www.dropbox.com/s/rb1mjgm1d9tfuor/ERROR%20EFB2%20LogFiles.JPG?dl=0

I just updated to #117 after uninstalling the Aviva soft Server no problem Ran the DB for P3DV4 - no problem Ran the DB for P3DV5 - problem? Got an error: https://www.dropbox.com/s/yyznz0pis0mcx94/DBV5error.jpj.JPG?dl=0

Well I updated for Version 4 this morning (Version2.1 build #116) and ran it. It has now been loading data bases for 5 minutes and hasn't gotten by airports 0%. Retried ands server reports "Waiting for Server (local) …" Looks like I have to download build #117.

I presently am running both V4 and V5 on the same computer. I believe that I will only be allowed to use my EFB on one or the other because of the differences in Data Bases, is that correct? Thank you James MItchell

Wilco (will comply). Jim

Worked here after picking up FSUIPC6. Regarding the database, what if one wants to keep both PVD4.5 and PVD5? Afraid to update at this point.

As soon as I got FSUIPC6 it worked.

Does Aiviasoft support P3DV5?

Not meant to criticize, just inquiring why it was here. Now that I know, am quite satisfied to ignore it in the future Jim