lonewulf47

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.

Great to hear that it works now. No, it was not the update. EFB v2 is running on numerous systems without a glitch. Even here in my office on two different systems. Dont' worry, the coders of EFB v2 are professionals...

Yes, see User Guide "Client", Chapter 6, "Map Functions"

What do you mean with "different profile"? A profile is "attached" to an A/C type, i.e. the name of its *.air file (without the *.air suffix). There can only be one profile for one specific aircraft. You can do two things: Change the existing profile or make a new one. See User Guide "Client", chapter 12.2 Profiles editor. Do not use the same A/C name (*.air filename) in two different profiles.

Sorry, I still don't get what you are doing - especially not the order you do things. The way you describe it is very confusing e.g.: "after that it runs fine and sees FSUIPC"... The Server does not see FSUIPC in any way as long as the Simulator is not running. According to your description the Simulator is NOT running at that time. Another one: " The clients after a few DB re-builds because the DB does not agree with the simulator then seems to work"... The Clients do in no way any check against the Simulator's database. This is purely the Server's task. And so on, and so on .... It is almost impossible to find out, how and what things are happening on your computer. So let's start from scratch again: Please do me a favour and do the things exactly in the order I describe now: 1. Start the Simulator. Place a default A/C at a suitable airpport (no matter which) 2. Make sure the Simulator has fully loaded and the A/C is at the desired position 3. Start the Server 4. Start the Client (please ATM only use one Client, best would be the one on your Simulator machine 5. When everything has loaded, wait a few minutes and then proceed to Shutdown EFB v2 and finally the Simulator 6. When everythin has properly closed down got to Windows Start Menu and select "AivlaSoft/EFB2 Create Support files" This will open a command window. When the tasks are done, close the task window You will find now two zipped files on your dektop, one beginning with "Server_" and one Beginning with "Client_", both having the ending ".txt.zip" Copy those two files into your next contribution to this thread. We will then have a closerand better look into the what's and whereabouts of your connection problems.

Sorry, you shouldn't post in two different threads. You obviously have no valid setup of your EFB v2. Please stick to the other thread and and try to answer the questions I have asked there.

OK, that's all going a bit criss-cross. I think we should clear things up before going into troubleshooting. The Client NEVER connects to the Simulator, neither directly nor through FSUIPC. Let's start with the SERVER. It must be on the same machine as the Simulator and FSUIPC (correct version according User Guide) must be installed on the Simulator. When the SERVER is started it tries to connect to the SIMULATOR through FSUIPC and at the same time is listening on the TCP/IP for any CLIENT asking for connection. I do assume at this point that your installation went well and you have built the database. When the CLIENT is started, it tries to connect to the SERVER via TCP/IP, no matter whether it is on the same computer as the SIMULATOR or not. If it is on a remote Computer (of course in a local network), it will ask for the IP Address of the Computer with the SIMULATOR and the SERVER. If it is on the same computer as the Simulator and the SERVER, you will just tell him in the connection menu and he will find his connection. The starting order of of the various components (SERVER, CLIENT, SIMULATOR) is free. Whenever all components are running, they will connect automatically, if the setup is correct. To be honest, I have no idea how the state of your installation is and where all components are installed. This needs to be clarified first. So here are the first two questions: 1. Where is each of the components installed? 2. Is the initial setup completed (building of the database)?

The flight plan is reset after landing. After a touch and go my guess is that you are ariborne again. You can't open a stored routing inflight. Actually I'm still trying to understand what you want to tell us. Do you load a flightplan, then go for a touch-and-go and then go enroute? EFB v2 is made to work in a normal pilot's environment, and that's what it does. You will however always find a way to make it collapse.Anyway the behaviour you describe is absolutely following the way EFB v2 is designed. So - no bug at all.

I see. Thanks for info!

Simply, NO! We do not match procedures to "wrong" runways, even if this seems so terribly important for the reality of your simulation. Procedures are from Real World, thus they need real world runways. It's as simple as that. I think Urs has explained it to the extents. Please do not compare to EFB v1. Things are completely different and partially outdated there.

Sorry for asking a bit stupid: Why don't you just taxi around and check the proper connection? There is no reason to start a flight if the connection is not ok. It won't improve even if you fly to New York! if the connection is not ok, the A/C will not move on the map, no matter what map you have selected. And don't forget to always start the Server as Admin! BTW what do you mean by " The side panel indicates it sees the sim"?? If there's a yellow "Simulator" written, it means that it DOESN'T see the Simulator!

...because the DatabaseBuilder has corrected the Runway Layout according to the ARINC file! Remember, ARINC is the OFFICIAL source for all aviation issues. To check this, there's a simple thing to do: While in Ground Mode press Ctrl+Alt+A and the overlay of the official ARINC runways will depicted in RED. At the same time the Runway labels of the initial runway layout will change to what was initially read from the Simulator. In this case the "old" 05/23 layout. We have decided to show the official runway designators, as far as possible.

No, there is no alternate definition possible anymore. The reason why we dropped this is that you can't define a second flight plan while still in an active flightplan (routing). A second thought is that - according to my pretty rich experience in real world flying AND simming, the cases where you would actually divert (and this is valid especially for Simming too...) are extremely rare. And in addition to that the decision, to which alternate you are finally proceeding is a short term decision, done just prior to starting the diversion, and this is not necessarily the initially planned diversion airport. Nevertheless we might rethink the whole process in conjunction with other enhancements planned for future versions (v2.1 or further).

Yes, most probably the Add-On scenery does not provide the necessary information on its ground polygon information in the respective BGL. Can you provide more information on the used Add-On scenery?

We currently have no plans to use Pete Dowson's makeRwys. Why? 1. It uses the very same source as we do 2. We are also able to completely decode BGLs 3. MakeRwys need a third party software to "find" all airports when installed with P3D's new package system 4. EFB v2 analyzes the package system using its own resources 5. The filtering method of suppressing "fake runways" is not applicable as it suppresses short runways that actually exist So you see, quite few reasons why there is no need to use a third party tool which gives no benefit at all ?

LUMVAV ?? newest 6-letter coding???

Sounds great! Thanks for info. Hope you enjoy EFB v2 as much as we do ?

That's correct. the moment when you hit the "Finish" button on the FPL windown it will be transferred into the GPS and consecutively after every change, be it when adding procedures or when using the "Dir TO" function inflight.

Yes, I believe you, thats exactly what EFB v2 does also. In contrary to EFB v1 which used Simconnect as a "linking feature" to the Simulator, EFB v2 uses FSUIPC. However you didn't answer my question about any warnings appearing on the Client pointing to connections problems.

The reason for not closing the procedure window with "Set FPL" was dropped with the introduction of the RSB. Hit ARR and it closes the DEP window and v.v. Hit AUTO and it closes ALL windows. The way EFB v2 presents the procedures is just different to v1 but more straightforward when it comes to visualising each single procedure. It is comparable to thumbing through a pile of charts. You might look around in different countries where selecting appropriate procedures is not necessarily leading to a continuous routing but possibly has gaps between segments. That's why we introduced this method of drawing each procedure in its real details to always provide the real depiction of the selected sements. Overall directions can still be derived from the procedure list. It's a different philosophy, but believe me, once you get the hang of it, you will find your way through. I fully understand your desire to keep the old beloved way of selecting procedures. Nobody is forcing you into something that you don't feel comfortable with. As a general rule the devs do usually not participate in such discussions. I did this only because I was addressed by Jonas (Mr. ATC). Apart from this contribution I will stay out here and leave you to your proposals and ideas.

No, it was a bug and it has been corrected with the latest Client Update Build #70.

Open the Flightplan window and press "Clear FPL"...

Is EFB v2 ever connected to your Simulator? Do you see any yellow or red message on the right top corner of your Client? Zurich is the FIRST defaut location for EFB v2, if no connection to the Simulator has ever been made. Do You have the proper version of FSUIPC installed?