aivlasoft

Joe, please verify the settings whether you have selected to show online traffic (System > Settings > Charts > Traffic).

Mark, Frans, thanks for your replies and the "how-to-do's". Although it seems to work for now, keep in mind that there might be some Prepar3d software updates in the future which will no longer be compatible with the today's binaries.

Indeed, it's strange. EFB is listening for traffic information which is provided by SimConnect. SimConnect is not providing any information about the source of this traffic information so EFB cannot distinguish between aircraft "X" and aircraft "Y". Maybe there is an option in FSInn which allows to set an "exclusive" option? I don't know the programming interface which is used to set traffic to SimConnect from outside. Did you already test what happens if you set all the traffic sliders in the FSX options to the left side? Does it also happen if SquawkBox is used as a pilot client software?

Hi Jack, thanks for the link. I did a test with the renaming of "Prepar3d.exe" into "Fsx.exe" but I could not get it to work. Although EFB states "Connection established ..." it does only mean that it could connect to "Microsoft.FlightSimulator.SimConnect.dll". I especially mention the so called "fully qualified" name of the dll since the one that is used by Prepar3D is different: "LockheedMartin.Prepar3d.SimConnect.dll". EFB has a built in reference to the MS-FSX SimConnect and it will not call the LM-SimConnect.dll and therefore it will not "talk" to Prepar3d.exe (regardless whether it is renamed or not).

Paul, could you please send me all the logfiles from both computers to support@aivlasoft.com. Thx. The logfiles can be located as follows: Open "Windows Start Menu" > All Programs > AivlaSoft > EFB > Logfiles

Hi, question marks are depicted when a certain information is missing. When flying online, the questions marks on the first line mean that EFB cannot determine the destination airport for this flight. This is due to the fact that EFB uses two different sources for aircraft information. The first one is the direct feed from FSInn/SquawkBox into FSX, which doesn't provide the aircraft type and also not the destination airport. These two fields are taken from the 2-minutes update of the VATSIM servers (the same as ServInfo and VATSpy are using). Source #1 (direct feed) is updated very often, I guess several times per second, whereas the VATSIM server data is updated only every 2 minutes. Therefore it is possible that the aircraft tag is not yet showing the destination airport and the aircraft type (question marks on line 3 of the tag). When AI traffic is generated by UT2 it seems that the origin and destination airport are not provided by UT2, or at least this information is not set to the appropriate data fields in SimConnect.

Hi Petr, thanks for your reply. I see, ELY395 seems to be the online aircraft (the data for destination airport and the aircraft type is taken from the VATSIM server data feed). Although the other aircraft (generated by UT2) are providing destination airport, EFB will not read that because EFB is set to "online" and therefore it takes that data from another source. I still cannot understand why the traffic generated by UT2 is forwarded to EFB (by SimConnect). Maybe FSInn doesn't reset this? It makes absolutely no sense to me to have AI-traffic generated by any third party tool when I'm flying online.

Petr, thanks for the screenshots (nice head-/cross-wind component ). From the frequency ribbon I can see that you must have selected "online traffic" at the RouteSetup page. From the screenshot of the "AI aircraft monitor" I can see that AI traffic is generated by UT2 (?) and FSX. So my question is which pilot client software are you using to connect to the online network? For me it seems that there is no FSInn or Squawkbox running at the time when the screenshot has been taken. Am I right? Online traffic (either from VATSIM or IVAO) is only depicted if a pilot client software is running, just selecting "online traffic" from the RouteSetup page does not provide online traffic to EFB.

Hi, please have a look at the download page (you must scroll down to the "checklists" section): http://www.aivlasoft.com/download/index.html

Petr, this feature (sort of) will be available in version 2. I don't know yet whether it will be possible to play individual sound files per each trigger or only one certain file when the flightphase changes. Too early to make promises .

John, That means that either the DisplayUnit or the DataProvider did not respond within a certain time limit. Often this is the case when the performance of the network is very poor. Maybe a slow wireless network? I'm not sure whether I understand what you've described.

Thanks for clarifying.

Hi, AI-traffic, WIND and TRFC is only available when FSX is running and the moving map is active. To activate the moving map press the small aircraft symbol on the chart options menu bar. BTW, according to the forum rules, please sign your posts with your real first name. Thanks.

Hi, according to the forum rules, please sign your posts with your real first name. Thanks. No, this is not necessary. No, just make sure that the DataProvider is updated to the latest version 1.3.2 SP1. If not, please use the latest update from the download page to do so. If the DataProvider is already updated, just use the latest installer from the download site (http://www.aivlasoft.com/download/Aivla ... P1.exe.zip) to install a DisplayUnit on your Vista computer. Then adjust the TCP/IP settings according to the "Installation manual". The folders on the DataProvider's computer must be shared before you attempt to connect a DisplayUnit to the DataProvider. Please read this: viewtopic.php?f=3&t=217 I don't think so .

Kosta, That is really new to me. I didn't know that it's a matter of the pilot client software. Will do some tests in the next few days. Thanks for the analysis. EFB can only show what FSX (SimConnect) provides to EFB. According to the description of the SDK (software development kit) the maximum distance at which AI-/Online traffic is provided by SimConnect is around 200 km (~ 108 NM). That is what EFB internally is using as a distance when requesting AI-/Online traffic data from FSX. If one is reducing the range in the pilot client software, this will result in less traffic that is sent towards to FSX. If one is reducing the range in EFB it will result in less traffic that is shown on the DisplayUnit's screen (although all traffic is read from SimConnect). But in no way EFB can show more traffic than FSX provides.

Robert, on my system I could solve the problem. It was due to the fact that I changed the position of my second monitor from previously right side to the left side of the main monitor. When I opened the touchscreen keyboard it still has been shown at the position of the right monitor (which no longer is at this position) and therefore I couldn't see the keyboard. Try to do the following: - Press the button "Keyboard" in EFB, the keyboard is shown but you can't see it - Now open Windows Start Menu > "Control Panel\Appearance and Personalization\Display\Screen Resolution" - Select the second monitor ("2") with your mouse and move it to the other side of the main monitor ("1") - Press "Apply", the monitor logically changes to the other side (mouse handling is now quite confusing ) - Do you see the keyboard now? - After moving the keyboard to the main monitor, revert back to the original screen settings. Hope this helps.

Adan, from the source code of the Navigraph data reader in EFB I can see that colocated fixes should be supported. I suggest that you search other SIDSTARS files to find an example on how to describe colocated fixes.

Petr, from the DataProvider's "Data" menu you can open the "AI aircraft monitor". Could you open this monitor when the above described situation occurs and then please send me a screenshot from the monitor to support@aivlasoft.com. Thanks.

Petr, as far as I know, there is no mix of VATSIM and FSX traffic at the same time? Do you really have VATSIM online traffic and FSX offline (AI) traffic on your display at the same time?

Hi Adan, could you please describe your question a bit more in detail? What do you understand with colocated waypoints. Which functionality do you expect. I cannot give an answer as long as I don't understand your question.

Hi Robert, I'm fine, thanks. That's funny somehow, I just tried to do the same like you described and ... you're right, the keyboard appears only in the taskbar but not as a visible window. Hmmmh, seems that nobody else is using this feature ... I will have a closer look into this issue tomorrow and will let you know about my findings.

@Robert, Did you experience this stuttering from the very beginning or only since some time. If only since some time then my question is "what has changed on that system since then"? Any new software installed? Any configuration changed? Any hardware changed? SimConnect is used by the DataProvider to connect to FSX locally on that machine where FSX is installed. The data transport to the DisplayUnit(s) works on an EFB internal communication layer based on TCP/IP. Therefore EFB doesn't request any further tools than what is installed on the harddisk through the EFB installer.

Hi Petr, Unfortunately no. We are not allowed to change the refresh time at our own. Vatsim allowed a refresh rate of every 2 minutes, whereas IVAO gave us only permit for a refresh every 5 minutes. I sent them an inquiry already asking for shorter intervals but they denied (Most probably due to the fact that EFB is commercial software).

Henk, When you're flying along a route EFB checks whether the next waypoint has been passed or not yet. As long as the next waypoint is not yet passed the distance shown is taken from the aircraft to this "next" waypoint and then along the remaining route until the destination airport. If the next waypoint remains as "not yet passed" the distance increases since the aircraft is flying away from this "next" waypoint instead of flying towards this "next" waypoint. Typically this can happen at a "fly by" waypoint when you don't fly by close enough (if I recall correct the limit is around 2 NM). How to avoid the increasing distance? Use the direct-to function and select the "next" waypoint manually. As soon as you've selected the next waypoint, the calculation of the distance will be correct again.

Jack, this is a feature which is planned for version 2. The current version 1.x doesn't have this ability.