Captain45

Thanks Urs, I suspected something like this. I'll inform Hervé Sors about this. Thanks for sorting it out. Cheers, Dirk

OK. I checked it out. Under Aiport Information after the double click it comes with: D:\P3Dv4\Scenery\0601\scenery\APX50100.bgl This is exactly the same file that Sors's ILS Inspector uses. On the Landing Aids Tab it shows the wrong info that I posted about before. I'll attach the file. This is really a weird thing. Dirk APX50100.bgl

Sorry. A typical RTFM issue on my side. I'll get back to you after dinner.

Hi Urs, Well..., I checked the manual and in there is tells me what file is used. But when I check my DisplayUnit's Airport Information it is blank on that spot. I checked it with another airport and that gives the same story: nothing! Could this have sometimg to do with the fact that my DisplayUnit is on a networked PC? Dirk

Yes I did. Several times after each Navigraph and Sors's updates. My guess is, that the DataProvider somehow reads the old file with the P3D default NavData. For restoring purposes Sors's programs rename the APX50100.bgl that contains the default stuff into APX50100.bgl.p3dini with a new active file APX50100.bgl (as I can see on the file date/time stamp). But that happens with a great number of files in the ..\Scenery directories. Maybe it is just an index thing. But since I have no clue on how the DataProvider gathers data I'm just guessing. I'll put the question also on Hervé Sors's forum.See what comes up. Dirk

When I load Stock airport (P3Dv4) ENTO in the Display Unit 1.16.15942 for an Approach RWY18 it shows: Loc. SFJ 110,95 358 (RWY 178) and that is the frequency and course (BC) of ILS/DME 36. And...., when I check an Approach RWY36 there is no ILS approach, just a VOR/DME and a RNAV. I used the ILS/Runway Inspector (Hervé Sors) and found in the default APX50100.bgl: ILS/DME 36 SFJ 110.95 ILS/DME 18 TRP 108.30 The same info is stored exactly the same in the AIRAC Data files I wonder how AivlaSoft EFB can come up with the wrong info. It looks as if AivlaSoftEFB is using very old default data. Ignoring what's in AIRAC and what has been updated to Navigraph 1802 (by Hervé Sors' World NavAids package. Dirk

Sorry folks. Found the solution myself for the reported problem. Could not delete this post. Have a nice day. Dirk

After installing FSDreamTeam's LSGG I found out that after a Simulator scenery update in the DataProvider, the ground layout of LSGG is still the default one. I found out (the hard way) that this is because new P3D scenery is no longer stored in the scenery.cfg but elsewhere. You can see that in P3D/World/Scenery Library by the fact, that the newly installed airport is greyed out. You can't click on it or move it up or down. Since I use MakeRwys.exe (by Pete Dowson) for other reasons (PF3 ATC) I knew how to solve this problem for AivlaSoft EFB updates as well. Here is how it goes: - Download and Install the AddonOrganizer_P3D_V4 software here - Run this program and click on Backup/Restore and then 'Export library for external tool' and follow the instructions exactly as in the popup. Step 2 is to run the Simulator scenery data update in the DataProvider. Keep in mind that you have to do this after every new Navigraph or Aerosoft update of the navigation data and after installing new P3D scenery that is not in the scenery.cfg. Of course it would be nice if future development of AivlaSoft EFB can handle this 'hidden' installs, but for the time being this will solve your problem. Dirk

Thanks for the reply Urs. I stupidly searched for 'Q400' only and found nothing. My guess was already that it must have something to do with that flight engine outside FSX/P3D. Well... I have to make notes of block-on and block-off time only, because the FMS of the Q400 gives the other two after a flight. Greetings, Dirk

Hi, I installed a new aircraft, the Majestic Q400 in P3Dv3. With this aircraft I get in the display unit a "flight log not yet available". Other aircraft I flew before did not have this problem. I remember I had this years ago with another aircraft, but I can't remember what the solution was. Probably something simple. Can you refresh my memory? Thanks Dirk

Thanks Urs.

Hi, Is there a way to influence the calculated TOC/TOD in the charts in any way? It would be nice if I can adjust those independently in ft/min values, so it would be nice if it's possible. Thanks Dirk BTW: 1.5 on my FSX:SE on 64 bit W10 works perfectly well. I must be one of those lucky ones.

HI Carlioian, I have followed the switch to FSX-SE also. I had to clean the registry before installing FSX-SE, and every other appearence that had something to do with the old FSX-MS environment. Indeed, Steam works better in frame rates and is most certainly more stable. Installation of my add-ons worked fine as long as I downloaded the most recent versions. When installing the EFB (new install, I thought) I ran into the same kind of problems. I did not log what I did, so I can't mention all the details. But for sure I cleaned out every appearance of the EFB software, files, directories, registry, the works on both, the PC and the client (my notebook). After that I just installed the EFB on both machines and that went like a charm. No problems whatsoever. New Navigraph install (had to change the directories of course) and the datamanager did it's job like it should. So my rough guess is, that you have some cleaning to do to get the EFB working. Good luck, Dirk