aivlasoft

Chris, and please tell us which AIRAC cycle you've installed on your computer. Thanks.

Hi Sebastian, did you check the option "Show 'online' traffic ..." (-> Settings, Charts, Traffic)?

Guy, I don't know why but there is a file "s4.bin" missing on your computer which should be there ... please run the full installer in this case and you will have this file back again. http://www.aivlasoft.com/download/Aivla ... p_v130.zip Hope this helps.

Hi Dave, there is a simple "TURN RIGHT" missing in the Navigraph data for the transition "L". Since the difference between current track and next track is 180° EFB cannot determine to which side the turn goes. In such a situation EFB takes the "left side" turn as a default which is unfortunately wrong in this situation. Before: " ... HDG 113 INTERCEPT RADIAL 158 TO FIX DME09" After: " ... TURN RIGHT HDG 113 INTERCEPT RADIAL 158 TO FIX DME09" See the result below.[attachment=0]EFKT_LLZ16_L.jpg[/attachment]

Kevin, a closer look into the file "firs.dat" shows that e.g. no positions like "_E_" or "_W_" are defined for EHAA: EHAA::NL:Amsterdam:Radar:52.8:4.6 Whereas other FIRs/ARTCCs like EDGG (Langen Radar) have explicitly defined their sub-positions like "_W_" or "_N_" etc: EDGG:N:DE:Langen:Radar:51.30:7.4:EDGG NORTH EDGG:W:DE:Langen:Radar:49.8:7.28:EDGG WEST EDGG:S:DE:Langen:Radar:49:8.91:EDGG SOUTH EDGG:E:DE:Langen:Radar:50.35:9.44:EDGG EAST EDGG:NW:DE:Langen:Radar:50.7:6.76:EDGG NORTH-WEST EDGG:SE:DE:Langen:Radar:49.6:8.9:EDGG SOUTH-EAST EDGG::DE:Langen:Radar Therefore EFB cannot recognize the active services from a sector if the controllers are logged in with an ID that is not known due to the definitions in the file "firs.dat". For the airports it seems to be a bug that they are not show correctly. Should be fixed with 1.3.1.

Kevin, could you please also provide a screenshot of EFB which has been taken at the same time? Just to your information: EFB only shows the relevant services along your route. Could you also provide an ATS route description?

Hi Jack, thanks for pointing at the "NY_" situation. From the information given in the two files "fir.dat" and "servinfo.dat" it is not possible to exactly determine whether the oceanic area is staffed or not. I will try to explain how. Let's assume that the following two controllers ("callsigns") are logged in: NY_KND_CTR NY_JBC_FSS The two letters "NY" are the key for the area. I assume that "KND" means "Kennedy", I don't know what "JBC" means. "CTR" means "Center", "FSS" is somehow similar to a "Center". Because the endings of two callsigns are CTR/FSS, the service must be a control area (not an airport). In the file "servinfo.dat" we must now look for a "control area" with a key "NY" or an alias "NY". There is one area in the [Controls] section which has an "NY" alias and "KZNY" as a 4-letter ICAO key: [Controls] KZNY/New York/NY/ It seems that this is the area that we searched for. Now the 4-letter ICAO code points to the FIR/ARTCC boundaries which are listed in the file "fir.dat". Unfortunately there are two boundaries and each of them has "KZNY" as a key: [FIRs] KZNY,32,18.000000,-77.000000,45.000000,-40.000000,K+ oo,31.500000,-58.500000 KZNY,72,37.227500,-78.127778,42.941667,-67.000000,KZ255dd,41.000000,-75.500000 If it were clearly defined in some papers I could "hard-code" that "NY_JBC_FSS" means the oceanic sector whereas "NY_KND_CTR" means the New York area, but as always "hard coded" items are dangerous and not really flexible . Any other ideas? Are there other "secret" definitions that we must be aware of?

There are two places where one can define whether and how much traffic should be displayed: - Pilot client software (FSInn, SB3/4, IvAp): Most of them have a slider or a similar control where the range around your current position can be selected. This value is somehow the "master" value. - EFB settings: "Charts" - "Traffic": Herein you select a) whether you generally want to have the traffic depicted (checkboxes at the upper area of the dialog), and you may set a horizontal range (which obviously cannot be higher than the "master" value set in the "pilot client software") or a vertical range in feet, or both of them. - If the values a) and are set then you can switch between "traffic visible" and "traffic not visible" using the chart option for traffic "TRFC". Independent from the "pilot client software" value the biggest range is approx. 100 nautical miles, which is a limit that is defined by the AI/Multiplayer-traffic system from FSX.

Hi Haris, I used this export function very often in the past (when I had the time to fly the 744 ). Meanwhile I'm only programming ... but I don't want to complain ... I like this job very much, really! I don't want to make a secret about the source where I finally found the information that helped me. Especially not if it's a website that provides in-depth and professional information. It also provides a flight plan converter into the rt2-format. http://www.bleedair.de/company-route-generator.html

merci beaucoup pour la louange! Salutations Urs

Hi Haris, Seems that no one of us has been using this feature in the past After a "many-hours-of-googling-Sunday-afternoon", I finally found a description which explains how to implement these waypoints. I will fix this in EFB so you will be able to use this feature as soon as possible.

Hi Sam, could you please provide a screenshot so I can see what you mean? Thanks.

Hi Jack, thanks again. The issue with London Control I could reproduce and I could also fix it. Do you still have this flight plan LFPG-KEWR?

Hi Jack, thanks for this screenshot. You're right, there must be something wrong here. I will have to do some investigation on that.

Hi, I just uploaded the files to our server. They are available from the download page. http://www.aivlasoft.com/download/index.html

Dave, thanks for this info. I always thought that the update of these files is well organized and regular. Isn't it?

Hi, it seems that this link is somehow broken and others at VATSIM are also waiting for an answer ... Read here (page 3): http://forums.vatsim.net/viewtopic.php?f=72&t=53274&start=30

The 1103 cycle should be up and available again in a few hours. http://www.navigraph.com/www/fmsdata.asp

As per today (March 11th, 2011) a new installation package version 1.3.0 is available from the download area. For all new installations please use this package. Installations made prior to March 11th, 2011 based on binaries with versions equal to or lower than 1.2.1.* can be upgraded to 1.3.0 using the Update 1.3.0, 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.0. 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

Navigraph AIRAC cycle 1103 Due to some misunderstanding between Navigraph and AivlaSoft, today the 1103 AIRAC cycle has been released in a new data format. This new data format can only be read by the new EFB version 1.3.0. The current version 1.2.1 will crash if it is used with the 1103 cycle. We are working flat out to release this new version as fast as possible. To prevent further problems with the 1103 cycle, Navigraph has temporarily removed the 1103 cycle from their download page. As soon as EFB 1.3.0 has been released, the 1103 cycle will be available again. Sorry for the inconvenience and thanks a lot for your understanding. For "more" information please also read here: http://forum.navigraph.com/forum/default.aspx?g=posts&t=2472

Freddy, EFB is currently not designed to be able to reset a current route automatically after a new start of the DU while the flight is still in progress. Although there is a possibility (*1) to "reset" after such a situation, in my opinion we should concentrate on the network problem to avoid the described situation. a) Are you running a wireless connection or with network cables? What are the specs of the XP machine? c) What are the values for the timeout settings? You can read these values from the DU and DP settings ("TCP/IP" tab). (*1) - After restart/reconnect of the DU, use the "Direct-To" function and select the next waypoint towards the destination.

Hi Ben, I try to write down the facts we know: A) on your XP computer ... - the DataProvider is running, or it has been running at least once. - the folder "C:\Documents and Settings\[user Name]\Local Settings\Application Data\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider" contains 13 files (named "a" to "m") - if you run "Windows Explorer" you can navigate to this folder and can see all these 13 files - this folder is shared for "everybody" (permission "read") on your Vista computer ... - If you run the Windows Explorer you can navigate to that shared folder on the XP computer (via Network). - if you have a look into that shared folder (using Windows Explorer) you don't see these 13 files Is that correct?

Hi, According to the forum rules, please sign your post with your real first name. I like to know to whom I talk . Thanks. What you describe sounds to me as the DataProvider was not yet running and therefore it could not create the necessary files. Did you run the DataProvider before you tried to connect the DisplayUnit? The folder that must be shared on your XP machine is: C:\Documents and Settings\[user Name]\Local Settings\Application Data\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider

Jean-Louis, please send the log files to support@aivlasoft.com. SP1: Everything is possible . Seriously, I can't say whether it is due to SP1, I don't know all the details about SP1.

Guillaume, I'm sorry to tell you, but the minimum requirements say: "Screen resolution: minimum 1024 x 768, recommended is 1280 x 1024". This can be read on the EFB website at http://www.aivlasoft.com/products/index.html#footer).