aivlasoft

a) As soon as a "Direct-To" has been selected, all waypoints along the route until the direct-to waypoint will immediately be marked as passed. If the option "Create Garmin flight plans" is activated the Garmin flight plan is also recreated considering this latest change. c) Several items in the flight information system must be recalculated too. Currently there is no "undo" function for all this.

Hi Brad, you're right, if we were only looking at the vertical profile view . Plan view is depicting and naming the correct FAF "MILTT" whereas the profile view only shows the name of the collocated outer marker "BO" (NDB). This is due to the fact that I had to make some compromises because of too less space when drawing the profile view. So I decided to only show the name of the navaid. [attachment=0]KBOS_04R.png[/attachment]

Hi Don, thanks for your information. It's a sad story that neither the developers of FSInn nor the developers of SquawkBox are maintaining their software. An option that would stop this automatic reflection of all changes would make sense.

Hi Don, I don't know the internals of FSInn so I can only talk about EFB. Whenever you activate or change a route in EFB the following items will happen: a) IF on the DataProvider's side the option "Create FSX flight plans" is activated, a flight plan will be written into the folder: "C:\Users\[username]\Documents\Flight Simulator X Files". The filename is as follows (e.g. a flight plan from Zurich to Geneva): "EFB Zurich (LSZH) to Geneva (LSGG).pln". It always has a prefix of "EFB". IF on the DisplayUnit's side the option "Create Garmin GPS flight plans" is activated, an additionally flight plan will be written into the same folder but its unique name is as follows: "EFB_current_garmin.pln". This is the flight plan that is loaded into FSX. At the moment of its loading into FSX it is visible in the Garmin GPS system. As I already mentioned I don't know much about the behavior of FSInn but I guess that it observes the FSX flight plan folder for any changes. As soon as it detects a change it loads the latest flight plan? I'm not sure whether it happens this way, it's only a guess ... Hope this helps to find a solution.

Björn, what means "doesn't work anymore". - is the button "grayed out" which means unavailable - does the button get a yellow border when clicking on it The colors have not changed with the upgrade. Did you change the color scheme of your computer? Maybe to "Classic mode" or anything else?

Hi Brad, EFB always takes that one with the highest layer number. E.g. if the scenery.cfg lists the airport KBOS in layer 34, 110 and 115, then EFB takes the files from layer 115.

Brad, when I had a look into the scenery.cfg file that you sent to me, I got the impression of a say strange sequence of the different layers. Maybe this could be the problem? If you apply some changes to the scenery.cfg don't forget to run the "FSX Scenery data update" from the DataProviders menu.

Leif, today I finally found the time to fly the route you provided. The answer from my last post seems to be wrong (one should not give an answer without having a look into the source code ). I used a default 737 for this flight. Cruise level has been set to FL210 and initially I didn't add neither a STAR nor an approach. Above 10'000 feet I set a speed (IAS) of 290 kts on the MCP. This gave me a groundspeed of 385 kts when I reached T/C. At this point the T/D was calculated to be just at "ROSBI". While on cruise level I added the STAR (ROSB3C) and the approach. The T/C has then been recalculated to be approx. 8 NM from TNO towards to my position and also on the chart it was clearly evident that the T/C has been moved. 20 NM before T/D the FIP showed a descent rate of -2400 ft/min to be at FL120 at TNO. I reached TNO exactly at FL120 with a groundspeed of 340 knots only followed the instructions given by the FIP. In my opinion there was nothing wrong nor was anything missing nor is it a bug (maybe I didn't understand exactly what the problem on your flight was?)

Hi Nolan, this is currently not possible, sorry. I will put it on the "to-do-list" for the next version.

Leif, thanks for the route and the explanation. The difference between the two arrival routes is that ROSB3C ends with "vectors" (which is an "unknown" position) whereas ROSB3N ends at a known position (LAMOX). EFB cannot determine the distance that must be flown if the end point is not defined and therefore it cannot adjust the T/D.

Leif, do you mean that the current position of the T/D has not been changed when adding the STAR? Can you provide the route please (ATS description and altitude)? Can you describe what you expect to be happened when adding the STAR?

Brad, I still don't see where's the reason for the problem. Is there any chance that I can download this scenery for testing? Are there other users that run this scenery without problems? Or do they have the same problem?

Brad, I'm not 100% sure but it seems to me that the scenery.cfg on your FSX computer is not free of conflicts. Could you send me the file to support@aivlasoft.com? The file must be available as follows: C:\ProgramData\Microsoft\Fsx\scenery.cfg Thanks.

Hi Brad, the plan you sent to me just loaded fine into EFB. It is a FSX plan which must be loaded using the FSX flight plan reader. Please proceed as follows: - Open "Route Setup" - Press "Select" - Open drop down menu "saved routes (select type)" - Select "Flight Simulator FSX" - Now navigate to the folder where the flight plan is saved and select this plan Now it should be read. On my computer I then got the following warning box:[attachment=0]KBOS_RwyAssignments.jpg[/attachment] Is this the same that appeared on your computer or was it a different warning? Maybe you can provide a screenshot?

Brad, could you send me this .pln file which you mentioned in your first post? And could you describe which Flightplan Handler (FSX or FS2004) did you select when you tried to load that plan?

Hi Franck, it seems that I needed a strong coffee first but now I see it ... You referenced the files from IvAp (pilot client) instead of IvAe ("The Eye") which is a different program. Please install IvAe (latest version) and then reference these files.

Hi Franck, thanks for the logfiles. It seems that somehow the data files could not have been read. Would it be possible to send me the following 4 files in a zip file: E:\Program Files (x86)\IVAO\IvAp v2\data\countries.dat E:\Program Files (x86)\IVAO\IvAp v2\data\firs.dat E:\Program Files (x86)\IVAO\IvAp v2\data\airports.dat E:\Program Files (x86)\IVAO\IvAp v2\data\fir.dat From the files path I can see "IvAp v2". Is "v2" a new program version?

Hi Franck, today I released a service pack SP1 for 1.3.1. Did you already apply this SP1? After applying this service pack your EFB will write logfiles again . Could you then try again to do what I suggested in my first answer? Thanks!

William, I can only say that this exception has been raised by FSX. SimConnect forwards it to EFB and EFB shows it. Unfortunately this is out of my responsibility and I can't help. Please read also here: viewtopic.php?f=3&t=145

Hi Franck, thanks for your reply. It seems that the current installer for version 1.3.1 doesn't allow logfiles to be created I'm just testing a service pack which should be released asap. Sorry for the inconvenience.

Hi Vic, as far as I know the PMDG MD11 cannot read the rt2-file format. Unfortunately only the 747-400 FMC is capable of reading such files. Re "virtual temperature": http://amsglossary.allenpress.com/gloss ... mperature1 AFAIK the virtual temperature is used as an input value in certain FMCs

Hi Franck, Please do the following: - If a route is already activated, open RouteSetup, press "Clear" - Restart DisplayUnit - Go to "System - Settings - Online" - Check "Log data requests", then press OK - goto "Route Setup" - press "online network - check button", select IVAO and then "Start" - after the connection has been established, even if you don't see any controller, press "Close" - Shutdown the DisplayUnit Please send me all the logfiles which can be found as follows: Open "Windows Start Menu" > All Programs > AivlaSoft > EFB > Logfiles - Restart the DisplayUnit and goto the Online-Settings - Uncheck the Log Requests checkbox

Hi William, The following sections and pages have been slightly changed: S7: Page 11, Chart details and legend > Ground chart S9: Page 3, METAR Data Sources S9: Page 4, Derived data S10: Page 5, Digital ATIS S10: Page 6, Chart Details S10: Page 8, Flying along the boundary ...

As per today (April 2nd, 2011) a new installation package version 1.3.1 is available from the download area. For all new installations please use this package. Installations made prior to April 2nd, 2011 based on binaries with versions equal to or lower than 1.3.0.* can be upgraded to 1.3.1 using the Update 1.3.1, which is also available from the download area. Quick link to the download area: http://www.aivlasoft.com/download/index.html It is recommended to upgrade to this version 1.3.1. For all questions concerning this update feel free to contact us either by postings in this forum or by e-mail to support@aivlasoft.com

Hi William good to know that all is running now. Thanks for purchasing! In a future version 2.0 the DataProvider is planned to run in the system tray.