lonewulf47

Hello Ray! Thanks for your comment.

Yes, this is a very rare event that shows up from time to time. Unfortunately we were not (yet) able to trace it properly as it ismost probably connected to other software using .NET and running on the same computer. The only remedy to-date is rebooting the computer.

I guess you are speaking for me too ?

Hi Daniel, I think this has been mentioned repeated times that the A/C in EFB v2 MUST BE ON GROUND (not that the Simulator must be running for that, but the last saved state must be ON GROUND). Inflight you can only manually create a Flightplan (Zulu-Plan). All othr Tabs are of course greyed out.

I just checked with LZIB on VATSIM. No anomalities showing up.

Great to hear that you could sort it out! Could you plese indicate the name of the iFly *.air file? We could add it to out default profiles as well for further use.

Not sure what you are referring to. A company route will show up in the "Company Routes" list regardless of whether the Simulator is running or not, Radios however can only be active if the Simulator is running, as this piece of information is derived from the Simulator. More important is that the last A/C position (as stored in EFB v2) is ON GROUND. You can also load a routing but you cannot ADD any SIDs or STARs as long as the Sim is not running with the A/C being at the Start Position of the Routing.

Yes, I can confirm the same issue here. I have however run Server Build #52 already yesterday and no such warning appeared. We have to wait until investigating further. It has happened in the past already a few times that the NAT track server had a "hickup" delivering wrong data for some period. The last valid NAT track download I received with Build #52 was 5th of July, at 00:55.

Set EFB to the airport in question and press the (i) button. This will provide all information on the used BGL for Ground Mapping.

Thanks Steve, for your kind words. We had one of our Betatesters almost exclusively flying the Concorde. Maybe he will step in here at some stage and share his experience.

EBF only interpretes the BGL's. The BGL with the topmost priority will be drawn.

Hi Marc, In fact you don't need to add a new profile as there is already one for a B737-800. You just need to insert the proper name for the iFly B737. See User Guide "Client" Chapter 12.2.1 "General". Open the profile for the B737-800 and add the airfile name for your iFly B737-800, confirm with "Apply" and restart the Client. From then on the profile will automatically be activated when you use the iFly.

Could this be an issue with VATSIM Vienna? ATM I dont' see any active region with VATSIM while IVAO shows Brussels and some more active. Frequency display is normal. On VATSIM only UNICOM is shown, but properly depicted 122.80.

All these information are derived from the respective BGLs. If nothing is in the BGLs, nothing can be drawn. Even Add-On Dsigners do not always include in their BGLs. If those lines e.g. are only "drawn" on the grpahic surface (bitmap), EFB v2 cannot see them of course.

Well, to be honest, that's a bit strange. I can see it depicted from default data of P3D v4.3. Can you please check with the (i) button (just right of the "Airports" button) what it says under add-on and File Furthermore press Ctrl + Alt + A and look whether the ARINC Database shows both runways? To me it looks as if there were any kind of add-on which has not all runways included.

Think of possibly using BOTH exporters at the same time. So you can save the flightplan also for later use from the Company Routes directory.

Thanks for the update. Great to hear that you could sort the problems. Enjoy EFB v2 ?

This function is not yet implemented. ATM there is no timeframe.

EFB v2 knows the installation path of Topcat if it's on the same computer as the Client ?

yes, of course they do, they also offer (as well as NavDataPro) an AIRAC cycle for the basic installation of EFB v2. But as you might have heard many simmers are nowadays using the most recent AIRAC cycle (as in real world aviation), thus you need to activate the most recent AIRAC cycle (e.g. the actual cycle being 1807, whereas the free Cycle in SimBrief is 1703 or so) also in SimBrief, and this is only possible by a subscription from Navigraph, and ONLY from Navigraph. Hence the restriction for us referring to single source.

A network address (IP address) consists of 4 numerical groups. The first three should be identical while the last group will address the individual PCs (indicated by "nnn", a 3-digit number ranging from 0 to 255), thus allowing 256 computers to be connected to your network. That should be sufficient ? In other words: IP adresses can range from (in this example) 192.168.100.0 to 192.168.100.255 The only thing you need to know is the IP address of your server's computer. you don't have to care for the rest. This is cared for by your router, otherwise the network would not work either. Most probably the IP address of your Server's computer starts with 192.168... Just find the IP address of your server's computer and enter it into the address window in the Client's setup. That's all.

While I agree that SimBrief is a comfortable means of flightplanning, we will not integrate it into EFB v2, as SimBrief requires a valid subscription for Navigraph to get the actual AIRAC cycle. Otherwise only planning on outdated AIRAC cycles is possible. We do not support single source solutions. That's also why EFB v2 offers both Navigraph AND NavDataPro as AIRAC source.

According to User Guide "Client", para 5.4 "Performance" TOPCAT must be installed on the same PC as the Client.

Thank you vey much, Tony, for your kind words.

Andreas, There is no need to address any network folders in EFB v2. One single IP address will serve the connection. It sounds a bit strange to me that you are talking about all PC's in a network should have the same IP address. This is certainly and definitely NOT the case. To connect the Client it is only necessary to point the client to the Server's PC (IP address of the Server's PC). As you correctly mentioned networking within Win10 became kind of a PITA with the Spring Update 1803, this however does not affect EFB v2's function over the LAN. The correct IP adress will do. Communication is done over TCP/IP. Due to these issues with the 1803 build it may become necessary to use the IP address rather than the PC name, as even proper promulgation of PC names is sometimes hampered by this new 1803 build. With the IP address we have never seen any connection problems so far.