lonewulf47

Hmm, you a re reporting a few issues within one sentence... GW & FOB field need not to be "populated". This will be done by EFB v2 reading the values from the loeded aircraft. Please provide a screenshot of the sidebar and state the following: Simulator running? if yes, which aircraft loaded? Which profile (automatically) applied?

Please do not cross-post. You have posted this question already in another thread.

No, but now I know....? Thanks Victor, I'll have a look at it and publish then.

Thanks Victor, for posting! I'll give it a brief check and then publish it !

What name did you use to save the new profile? Did you fill in ALL mandatory fields? Can you check whether the profile is saved in "C:\Users\<Username>\Documents\AivlaSoft\EFB2\Client\Profiles"?

EFB v2 can solely and exclusively depict standard ARINC data. Tailoring in the mentioned respect is unfortunately not possible. Anyway no filtering in any way is done for EFB v2.

No, this is a wrong piece of information. A future expansion of EFB v2 for X-Plane is PLANNED, but no betatesting yet at all.

No, in any case you need to execute a DCT TO operation inorder to get the proper waypoint sequencing working again. Just deleting a waypoint does not help in any way.

Ther is no such display in EFB v2 on purpose. We should not forget that this is an Add-On to a Flight Simulator. AFAIK a Simulator SIMULATES AN A/C. In the Cockpit you have all parameters of your A/C.. For the same reason we do not display IAS...?

I must leave this to Urs, as he has dealt once with a fsAerodata installation and double entries. At first glace I would presume that this is exactly the case what he told me about those double entries. Anyway not too dangerous as operation of EFB v2 is normally not hampered by this. Just looking a bit odd with twice the same navaid ?

No, there is no block time logging anymore for apparent reasons: there is no specific action within the simulator that can be RELIABLY used as Block-off/Block on trigger. We therefore decided to drop this.

Whatever you like. RouteFinder is not always correct. You can edit the route to your liking or use alternative route planners. I personally mainly use PFPX which comes up with the following routing for this airport pair: REXAM UN864 WAL M146 ERDUV

The worlwide database lists 1 navaid with the identifier RDS: RDS, Rodos, VORDME, 115.800, LG (VOR & DME colocated) and 4 navaids with the identifier DAL: DAL, Dalaman, NDB, 346.000, LT DAL, Dalaman, VORDME, 114.700, LT (VOR & DME colocated) DAL, Aateibe, NDB, 342.000, OS DAL, Dali, VORDME, 112.600, ZP (VOR & DME colocated)

Ah ok, I see now that the installer of Navigraph obviously produces a wrong (doubled) installation path. This of course will lead to the effect you described.

Yes, fsAerodata is known to produce double entries. I use Hervé Sors' Navigation Updates. This works without porblems. And with EFB v2 we don't need any default procedures being updated...

I doubt that. The screenshot clearly shows that the proper database files for the 1807 cycle are installed. To be honest, I have no clue why this happens. I have also never seen this before. I have installed several Navdata updates without any problems. Urs will have to step in here. Just one hint that comes into my mind. Have you ever rebooted your computer after having installed the database? Don't get me wrong, there is no requirement to do so, but sometimes computers are like human beings: they need to be set back on firm grounds...?

When reading through this and similar threads, I feel that there is a mixup between the initial problem on opening Port 13 and a subsequent problem of getting in contact with the timeserver. Many of you describe that once they were able to connect and thereafter ran into problems reconnecting. I would like to point to the following: If you were ONCE able to make contact with the Timeserver and therefore could login as a Demo User, each subsequent (failed) login attempt has usually not to do with the Port 13 access problem, but ONLY with the accessibility of the Timeserver. If the latter cannot be reached, the Login Screen will be presented. There is NO REASON to try to login again! Just cancel the login window and start the Server again. My experience shows that usually after 3-4 attempts the login will be successful. I have tried this several times on different computers and it worked all the time. Reaching the timeserver is obviously something that is not possible all the time every second and unrestricted. Given the fact that a few billion computers do this daily more than once, it is pretty understandable that there might be problems.

Yes, whenever it is showing up instead of being replaced by [AirlineShort] you need to insert it into the list exactly whe way it is used by the respective tool.

Well, there is a rough estimate of EET/ETA in the route summary, but only when airborne and in the Enroute Segment, based on actual speed. The accuracy is of course best if on Cruise Level and on Cruise Speed.

No, I guess you're not doing anything wrong. I had the very same issue also showing up. After deactivating/activating the OTS on the Client Settings however the OTS came back and show now normally. Nevertheless I also see something else on the OTS "behaviour" that seems a bit off. We have to investigate what has happened. Thank for reporting.

Yes, you have to start the Simulator once to allow the Server connecting to the Simulator. After second start of the Server you will see the entry for the flightplan folder there.

What airports exactly are concerned and where are they installed?

You are using an outdated version of the Server (#51 iso #53). Were there no updates offered upon starting the server? I would suggest that you re-downlaod the Server and Client Installers an go for a complete re-install.

My guess is that you zoomed out for enroute flying. A few of these Options/Functions will be disabled automatically because they don't make any sense to be displayed if zoomed out too far. Just zoom in a bit and they will come back. To resume the previous zoom setting use the RSB button "Auto".

Just use the numeric keypad. That works all the time or use the respective RSB button inflight after reaching the cruise altitude.