Jump to content

aivlasoft

Administrators
  • Posts

    5,929
  • Joined

  • Last visited

Everything posted by aivlasoft

  1. Hi all, thanks for helping to narrow down the issue. Will do some tests today and report my findings.
  2. Jean-Louis, it's just a matter of the runway assignments in the "Runways.txt" file. Didn't you get a "runway assignment warning" when you selected LFRB for the first time? Please check the "Runways.txt" file on your computer for the following entries: LFRB 08R 07R LFRB 08L 07L LFRB 26R 25R LFRB 26L 25L
  3. Jean-Louis, William the route description that you both provided herein work perfectly here (Airac cycle 1104, Rev 2). Although I'm aware of this issue, until today nobody (including me) could describe how to reproduce it. If you can describe in more detail how do you get this exception would be very helpful. Thanks.
  4. Ed, yes, please send me the logfiles to support@aivlasoft.com. Maybe there is an important information in the files. Better to check them .
  5. Hi Thomas, it seems that the EFB installer cannot find the FSX installation path in the registry. You may download the TweakFS Registry Utility which can repair it for you. http://www.tweakfs.com/store/free_tools.php Hope this helps.
  6. Ed, the last line on the DataProvider's window does not say anything about the connections. It means that the DataProvider is now ready and is listening to incoming connection attempts. Re "sharenames": If you open the Windows Explorer on the DisplayUnit's computer, can you see a node called "Network"? If "yes", can you navigate from this node to the DataProvider's computer and there to the folder "AivlaSoft.Efb.DataProvider"?
  7. William, did you already checked the "runways.txt" file. IIRC there are some lines in for EDDP as a default value. It can be that with the use of the Aerosoft's EDDP scenery these entries are no longer needed? Can you please verify whether my "idea" is wrong or not?
  8. Ed, please also read this topic from the FAQ's: viewtopic.php?f=3&t=217
  9. Bernd, I forgot to describe how you can uninstall it "manually": 1) Delete the folder: C:\Program Files\AivlaSoft 2) Delete the folder: C:\Users\[username]\Documents\AivlaSoft 3) If available, make a backup copy of the following file (it's your keyfile): C:\Users\[username]\AppData\Local\AivlaSoft\EFB\AivlaSoft_Efb_V1.dlsc 4) Delete the folder: C:\Users\[username]\AppData\Local\AivlaSoft\EFB 5) If you are familiar with the "regedit" then you can also remove the following key: "HKCU\Software\AivlaSoft" That's all what the installer is doing. Hope this helps
  10. Hi Bernd, did you already try to first uninstall EFB before you started a new attempt to install it? Open "Windows Start Menu" > Control Panel > Uninstall a program
  11. Hi Guy, would it be possible that you send me this new file, so I can "see" what's maybe the problem? support@aivlasoft.com Thanks.
  12. Guy, in which directory did you copy the new file? Did you add this directory to the "scenery.cfg" file before you ran the update?
  13. Hi Franck, could you please verify the following: - From the DataProvider's settings, select the "Folders" tab - Navigate to the folder which is shown in the field "Navigraph data" (use Windows Explorer) - There should be a subfolder called "NavData" - Within this folder (NavData) you find a file named "cycle_info.txt" If you open this file the first 3 lines tell you the version of the cycle that is used by the DataProvider. On my system currently this is as follows: AIRAC cycle : 1104 Revision : 2 Valid (from/to): 07/APR/2011 - 04/MAY/2011 What is shown on your computer?
  14. Hi William I copied the route description from your posting and pasted it into EFB. Here you can see what't the outcome ...[attachment=0]NTGI_NTAA.png[/attachment] AIRAC cycle is 1104. Do you have another result?
  15. 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.
  16. 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]
  17. 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.
  18. 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.
  19. 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?
  20. 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.
  21. 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.
  22. 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?)
  23. Hi Nolan, this is currently not possible, sorry. I will put it on the "to-do-list" for the next version.
  24. 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.
  25. 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?
×
×
  • Create New...