aivlasoft

Hi Michel, as far as I know from my experience an upgrade to a higher version of the .net framework should always be downward compatible. What do you mean with "Version 1.2.0 doesn't allow demo mode"?

Hi Terry, currently there is no way to enter the gate number as part of the flight plan. And please do not try to enter "Gate 123" or anything else into the DepartureProcedureInfo in the efbr-file. This will definitely get some problems. But please allow me to ask for the reason why you want to have the gate information added to your flight plan?

Hi Vittoria, as far as I can see from the program code there must be something wrong while EFB tries to read the runways.txt file. The screenshot with the procedure selector from the arrival chart shows the runway identifiers "06" and "24". This is an indicator that the runways.txt file couldn't be read (otherwise the identifiers must be "06R" and "24L"). Can you check that the runways.txt file is located in the following folder and not anywhere else: C:\Users\[username]\Documents\AivlaSoft\EFB\UserData BTW: the entries for the runways.txt must be as follows: RJBB 24 24L RJBB 06 06R Edit: Can you also check whether there is probably more than one runways.txt file? And please can you send me the entire runways.txt file and also all the logfiles to support@aivlasoft.com

Hi banshee, According to the forum rules, please sign your posts with your real life first name. Thanks. Could you please post a screenshot where I can see the greyed out runways.

Hi banshee, I did the same as you described and it works fine here. So if you don't mind, could you please send me your runways.txt file and - as Travis already asked - can you tell us which Airac cycle is installed on your computer? And - according to the forum rules (see at the top of each page) - please sign your postings with your real first name. Thanks.

Andy, thanks for the flowers . AFAIK FSC writes both flightplan types (FS2004 and FSX) in the same data format. Since FSX is capable of reading "old" FS2004 files, there is no problem so far. The file format for pure FSX plans is XML and not plain text files. EFB makes a distinction between these two different file formats and this is the reason why EFB cannot read "FSX-plans" written by FSC.

Andy, did you also try with a "real" FS2004 flight plan. As far as I know FSC doesn't write "real" FS2004 plans. They have some more information in their files. You might have seen that the technique to read flightplans has changed since version 1.1.0 of EFB. Now the flightplan readers are implemented as "plugins" and this way I will be able to release some more flightplan readers in the future without the need of a new program release. The next plugins that will be developed are the readers for FlightSim Commander 8.x and 9.x.

Ian, yes, that's correct! Entries in the runways.txt file are only needed if there's a mismatch between the Navigraph runway identifiers and the FSX runway identifiers.

Salut Jean-Louis, it's like Travis already said: the runway length is too short to be accepted as a "real" runway.

Jean-Louis, sorry for the late answer ... we're very busy due to the release of the upcoming version 1.2.0. After installing the airport LFHU you did a "FSX scenery data update", didn't you? Maybe you still have the logfiles of that session from the DataProvider? Can you see something strange in it?

Hi Peter, I just checked the registry on a 64-bit system and indeed it's quite different than on a 32-bit machine. I think that my first advice to manually add this key was not very good, and it is not necessary. As it seems to be on a 64-bit machine, the registry path is available but not at the same place than on a 32-bit system. I found the requested key as follows: HKEY_CLASSES_ROOT\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Microsoft\microsoft games\flight simulator\10.0 I wrote a test installer which shows the values that are checked as prerequisites. Could you run this file? I sent you a PM because of your mail address.

Peter, in your first post you mention that the solid state disk is "H" whereas in your latest post you mention that FSX is installed on "F" (at least the path in the registry points to that location). Maybe this is the problem? Some more information about the installer: After getting the installation path it searches for the "fsx.exe" file and then it checks the file versions: 10.0.61472 (SP2) 10.0.61637 (Acceleration Package) Can you confirm that "F:\Microsoft Flight Simulator X\fsx.exe" has a one of the versions above ?

Hi Peter, the installer checks whether the installation path from FSX is available in the registry. The key is "HKLM\SOFTWARE\Microsoft\Microsoft Games\flight simulator\10.0\". At this location a value called "SetupPath" should be available. It this path is not available the installer stops. Hope this helps?

Björn, it's quite a long time that you've waited to tell me that ... Why didn't you yell earlier? Since I don't have the German Airport scenery anymore I can't verify it now. But I'm quite sure that it works with 1.1.0 (which has been released May 2010). But anyway, next Friday version 1.2.0 is coming and I can send you a screenshot which I just took some minutes ago.

Laurant, I'm sorry but this is a bug in version 1.1 but no longer in 1.2 The procedures for LFBH runway 27 are not available in the Route Modify dialog but they should be available from the approach chart dialog (at least on my old 1.1 system). From the progress module select "Approach chart" and then click on the "blue" button called "LFBH Approach" -> "Select Approach" -> "27".

Hi Jack, planned release date is November 12th. Let's hold the fingers crossed .

Hi, yes, it is available from within EFB. You may there select from several sources: - FSX, - ActiveSky weather file, - REX weather file, - or online from NOAA, whereas the files from ASx and REX obviously are the sources for FSX, but sometimes it takes time until FSX is showing you the weather which has been set by either ASx or REX. Best regards Urs BTW: As per the forum rules, please sign your posts with your real first name.

Hi Grzegorz, I'm really puzzled with the situation you described. Also when having a look into the program code I don't get the clue how this can happen. Does it also happen if you switch the chart manually? Does it also happen if you run another aircraft? Did you ensure that NO shortcut is assigned twice across the several products?

Hi David, from which parking position did you start the taxiway routing?

Hi David, just a question: did you get this error once, twice or more often during the trial period? I know that this exception is not good and therefore we got in touch with Microsoft some weeks ago ... but unfortunately they cannot help. It's a sad story I know. If you keep away from EFB because of the fact that EFB is using SimConnect, then I strongly recommend you to also keep away from all other add-on's that are using SimConnect. But I assume that this must be quite a lot of add-ons. Just my two cents.

Hi, 1) currently this add-on is only for FSX, but not limited to default aircraft. I suggest to download the operation manual and the installation manual as well, both of them are available at the download section: http://www.aivlasoft.com/download/index.html 2) It's only possible to run the trial period once. We think that 30 days should be enough time to figure out whether one likes the program or not. In certain circumstances like heavy technical problems during the trial period we already prolonged a trial license. This requires the problems to be documented. Hope this helps to clarify the questions. Best regards, Urs BTW: According to the forum rules, please sign your posts with your real-life first name. Thanks!

Hi Andy, good to hear that parts of the problem could have been solved. Does that mean that the rebuild is now without any problem? Is there a runway assignment error in the DataProviders window (it should also appear a message box in this situation)? Maybe try read this topic: http://www.aivlasoft.com/support/viewtopic.php?f=5&t=167. Does it help?

Salut Jean-Louis, the position of the horizontal splitbar that you mention should be saved when the program terminates. Try the following: Open each chart type (Arrival, Approach, Ground, Departure, Enroute), re-position the splitbar to the desired position and then close the application by using "System" -> "Switch off". After restart of the DisplayUnit the splitbar should appear at the last saved position.

Hi Andy, I just had a look into cycle 1010 using version 1.1.0 and everything seems to be OK. All approaches for EGCC are available. Did you install a new scenery or is there another reason for the rebuild? Could you please send me the logfiles to support@aivlasoft.com. The logfiles can be found as follows: Windows-Start -> All programs -> AivlaSoft -> EFB -> Logfiles. Please send all the files you can found within this folder. Thanks.

Salut Jean-Louis, I think that the problem is due to a simultaneously try to write the "same" file (flight log) into the same folder. I assume that both settings for the flight log's folder are pointing to the same physical location? Try to change the flight log's path from one DisplayUnit to another folder.