aivlasoft

SP4 is under way but due to some bugs we could not release it before easter, although we would like to have ... Please be patient. BTW: Because the next version has a lot of new functions and improvements (beside of some bug fixes) I think that it will no longer be called "ServicePack" but just version 1.0.4.

In 1.0.4 / Airac-cycle 1003 / FSX default scenery the following data is available: 05R: VOR DME, ILS DME 23L: VOR DME, RNAV 05L: VOR DME, CAT III ILS DME 23R: VOR DME, CAT III ILS DME

Hi, Select the requested airport from the Airports Database (Menu "Airports" > "All Airports", then select the requested airport). This will open an "Off-route" airport viewer where you may select all the procedures you need.

is fixed with 1.0.4

Tom, disconnecting could be due to an elapsed time-out. If the DisplayUnit didn't send a response to the DataProvider within a certain time the DataProvider assumes that the DisplayUnit has been terminated. Therefore it will no longer send data to the DisplayUnit. You may try to increase the time-out value in the DisplayUnit settings and the DataProvider settings too. Please see the Installation manual "TCP settings". Stuttering sounds to me more like a problem with FSX. Please try to reduce the workload of FSX by moving some of the sliders slightly towards left and then try again.

sorry, I'm not sure what you mean with "being opened in a separate window manually" that you mentioned in one of your last posts. I'm still trying to find out why the EFB menu is not displayed in FSX even if you press the corresponding shortcut.

Could you explain this in other words? I'm not sure if I understand what you mean.

abax2000, The shortcuts are only used if the DisplayUnit is on the same computer than FSX. If the DisplayUnit is running on a separate computer the shortcuts are not being considered.

Hi, with version 1.0.4 this warning will no longer be listed because the value -464 seems to be a private value from AFX and does not have an impact on EFB.

abax2000, there are some known bugs with 1.0.3 which have been solved with 1.0.4. I just had a quick look into LGIR (Iraklion) with airac cycle 1002 and EFB 1.0.4 and there are two VOR DME approaches available, one for runway 09 and one for 27 (FSX default scenery). This new version 1.0.4 should be available in a few days.

Michael, I don't think that the publisher will know what this warning means because this is an EFB internal message. This warning message occurs when an unexpected value has been recognized. I'm just analyzing what the problem can be since this warning is often read. Your current database should not be affected by this warning.

gigabyte, and to all other readers of this post. I'm really sorry but it seems that the server is down. Investigations are running. Hopefully the server is up and running again in a short time. Edit: 2010-03-26 / 06:00z Server is up and running again. Edit: 2010-03-26 / 08:30z Server is down for approx. 2 hrs. Edit: 2010-03-26 / 11:30z Network interface card replaced. Server should now be accessible again. In any doubt don't hesitate to write me an email. I apologize for any inconveniences.

Tom, It is meant to use either the term "SID" or "DCT". SID doesn't mean the name of the SID. EFB is currently not able to analyze SIDs and STARs when parsing ATS descriptions. Will be available in version 1.0.4. FSX flight plans doesn't differ between SID, enroute, STAR or Approach whereas an EFB flight plan does. All waypoints in a FSX flight plan are enroute waypoints and therefore they are all shown on the enroute chart.

Daz, I don't know much about the rt2-format but I can imagine that the problem is due to the NAT waypoints. Probably they can't be read from the rt2-parser but from the rte-parser.

Tom, open the "Route Setup", then "Select". You will see a text box where you can paste the ATS description. NOBLY3 seems to be a departure route name. EFB doesn't recognize SIDs, STARs and Approaches. If you use the following ATS description it should work (at least on my computer it does): KDFW DCT LIT J131 PXV J29 JHW J82 ALB GDM3 DCT KBOS Please read also the manual on this topic.

Yes, SP4 will analyze it correct, just fixed this afternoon . SP4, or version 1.0.4 should be released within the next 2 weeks (if there is no unexpected road-blocker).

Joachim, it seems that the server was down. I just came back to my office and could reach 'em. Please try again now. Thanks for your patience.

Daz, I just realized that EFB is not properly analyze the RouteFinder plan if you set the option "NATs enabled". The route itself is read correctly but the ATS description uses NATC which is unknown to the FMC of PMDGs 744. I guess that this is the known bug which will be fixed in 1.0.4.

Dazzlercee, EFB doesn't know NAT tracks. The waypoint NATC seems to be the name of one of the NAT tracks of that day when the flight plan was created. I wonder how this waypoint came into the rt2-file? Runway 999: I don't know why but the rt2-file requests that the runway of the origin and the runway of the destination airport must be inserted in such a plan. Because most of the time when creating and saving a flightplan these two identifiers are not yet known. Therefore I decided to always write 999 as the runway number which results in two errors whenever the flightplan is loaded into the PMDG 744 FMC. I'm also not really happy with this but I couldn't find a way to save a plan without the runways. Do you miss them in the rt2-file or in EFB at all? To explain such a situation in general: If the ILS facility is not present in the FSX-data (bgl-files) then EFB also doesn't show the ILS procedure although it might be available from the Navigraph data. Hope this helps.

Oliver, kannst du bitte alle Logfiles an folgende Adresse senden: support@aivlasoft.com Die Logfiles sind wie folgt zu finden: Windows-Start-Menu > Alle Programme > AivlaSoft > EFB > Logfiles (Bitte alle Dateien zusenden, welche sich in diesem Verzeichnis befinden).

Joachim, I'm sorry but this is currently not possible.

Martin, can you send such a flight plan to support@aivlasoft.com? Maybe I can say which format it is.

Michael, with SP4 (which will come soon) it is possible to enter either a 4-letter or a 3-letter airport code as a waypoint. You may also enter such airport codes as origin or destination, what means that a flight plan created by FSX containing 3-letter codes will no longer crash.

Jack, just as an additional information: EFB takes the information about the decision height from the ILS name found in FSX. If the name contains "ILS CAT III" then it's 50 feet, "ILS CAT II" is 100 feet and "ILS CAT I" ,or "ILS" with no category given, is 200 feet. Navigraph data doesn't provide any information about decision heights (unfortunately).

Martin, I'm really sorry that I cant help in this situation because I don't know Vroute. Does it have different flightplan formats which can be downloaded? Maybe you should try another format? Maybe there's another user of this forum who can help you?