lonewulf47

Ok, first close Server and Client then goto the Settings path of the Server: C:\Users\<Username>\Documents\AivlaSoft\EFB2\Server\Settings in standard installation and look for "serverSettings.txt" Open this file and look in the [Network] section for the follwing line: TcpIpAddress = xxxxxxxxxxxx Whatever it says, replace it by TcpIpAddress = 0.0.0.0 Save and close the file. Be sure you do not change anything else. Start the Server. On the Settings/System tab the IP address should now read "any" Now you can start the Client and connect it to the Server. If you work with a remote Client on a network (still my guess) enter the IP address of the Server Computer rather than it's Name (which would also be a possibility). With Win10 Build #1803 ff names are sometimes not properly published within the network, so the IP address is the better solution. Hope that helps.

No, not at all... Default airport in P3D is correct. So... What Simulator? What airport (add-on)? A bit more information would be extremely helpful....

Thank you, Jerry, for your contribution! We will add it to our collection ASAP !

Hi Dani, no, this is not possible. Please observe that the minimum resolution for EFB Client display of 1280 x 960 is also required if operating in Windowed Mode.

Jürgen, You have changed the IP address in the Server/Settings/System tab. You should have left it to "any" as proposed by default and even mentioned in the User Guide that it should not be changed. The problem is that you can't go back to the default "any" setting without manually changing a settings file. I take it that you are using the Client on a networked computer? Are you familiar with manually editing a text file?

Just as a sidenote, the "add-ons.cfg" file can be on two different locations in the P3D v4.xx installation. On path is as mentioned here in the documents roaming path, the other is in C:\ProgramData\Lockheed Martin\Prepar3D v4. The add-ons.cfg file is the location where add-ons are enteres as so called "packages". This is a new system for adding add-ons introduced by LM with version 3.XX, however only used by add-on developers since V4.xx.

Just to add on this subject: the present solution was chosen to allow ANY aiport to be properly depicted, regardless of the nature of it's non-compliant BGL. There are airports where NO ground layout is present at all or where it is swiched off when using sloped RWYs (e.g. EGPB Sumburgh Airport by ORBX). So to have a solution which can cope with all possible deficiencies, we have decided to go this way. And just to add one more thing: it is not our primary goal to let the users do the changes in the BGL. We have created this AFCAD thread in the contributions section to establish a collection of BGLs to be downloadable for every user. The procedure to get a proper airport depiction is as follows: First check the AFCAD thread in the Contributions Section whether the airport in question is already published. Then download the corresponding file and use it as described in this section. If the airport is not yet isted, start a thread in the General Discussion stating which airport is affected (possibly with a screenshot) and we (or maybe at a later stage someone from the community) will create a BGL and we will then make it available for download. We are of course fully aware that not everyone is able to create/adapt a BGL with ADE

Sorry, Ray I'm just trying to find out what you are sayinge here ? So you are landed at an airport, you see that (hopefully) in your Simulator and (hopefully again) in EFB v2. So my (simple, I admit) guess is that you might well be aware of your status, uhm... of course I mean the status of your A/C by two means, the Simulator and EFB v2. And now you really do ask for a THIRD means to check the status of your A/C? Forgive me, but I'm simply overstrained by that....?

I'm afraid we are talking of two different Flightplan/routing files. The file you create and save with PFPX is of the *.efbr format stored at the path mentioned above ( C:\Users\<username>\Documents\AivlaSoft\EFB2\Client\Routes). It will remain available unless you manually delete it. A flightplan for FSX would be in *.PLN format and stored at another location (usually at C:\Users\<Username>\Documents\Flight Simulator X Files). If you don't store a routing explicitly at this location, it will not show up there. It is not needed anyway for EFB v2 ops, as you can't load it directly from there. You would need to move it into the "uplink" folder. I'm afraid that I have no idea what STB is using for what purpose.

Well, this is not what EFB v2 does either. I can't see what you are describing. The flightplan (Routing) saved to the routings directory is still there after landing as it should be. There is no reason for EFB v2 to delete it. To what folder do you save the route after creation in PFPX?

It depends on the way you send the Flightplan to EFB v2.If you use the Uplink Option then the Flightplan is deleted as soon as it is uplinked to and accepted by EFB v2. If you want to keep it stored in either the FSX or the EFB v2 path for later use, you simply save it after successful uplink. There are exporters for both FSX/P3D and EFB v2 format.

Ben, while I keep out of this discussion as everything concerning Online Flying is outside my area of interest and is well handled by Urs an Jonas, I would ike to point to two things that I do not like on your post at all: - mentioning EFB v2 as being "in a early development" is a bit far off and is in fact not even worth being commented, were it not close to an insult to all concerned in developing EFB v2 - your comment on "the same comment keeps getting brought up by different people" is of course a valid point from your view. However you should also allow the developer to have his own view on the importance of such comments and proposals. AivlaSoft does in no way ingore those, but you should also be aware of the fact that "a few" or "different people" does not conclude a statement of importance. Given the fact that the number of those "complaints" are far, far, far - and again - far below the 1% mark compared to the number of licensed installations, you will certainly agree that the delevoper is allowed to draw his own conclusions on that fact. Nevertheless - as also Jonas stated above, it is not the intention of AivlaSoft to simply ignore any proposals, but going back to a previous system is just not an option. This kind of decision should - that's at least my opinion - still lie within the developers authority...

It's all described in the User Guide "5 Client", chapter 7.1.4 Miscellaneous The traffic labels are user customizeable and an show different entries on grund and in the air also depending on zoom level. And, btw, they don't only show VATSIM online traffic but also all AI traffic. Best way to step into this field of interest is to have a look at the Traffic Monitor called up from the Server's Menu.

What do you mean by "sceneries from xml-files"? FSX/P3D sceneries are generally made of BGL, not XML. I you however refer to the package system used by Prepar3D from V3 onwards then the answer is of course "yes"....?

During normal operation of EFB v2 some issues have shown up, that are already addressed and will be remedied within a suitable timeframe, depending on the workload for current development and importance. Issue: Missing Final Approaches for Finals with Visual Circling (let down approaches) Planned correction: AIRAC Cycle TBD Description: Final Approaches without designated Landing Runway cannot depicted with the present routines of EFB v2. This required some changes within the data structure. A number of remote airports are affected. Issue: Missing Runway on Ground Map Planned correction: only possible with described workaround Description: A few Add-On airports are missing Runway information in their layout (AFCAD) BGL. There are many reasons, why this information is missing. One specific reason is modeling of terrain-following runways, which are often used in mountaineous terrain (such as the French Altiports) and also a few others. In addition to that many Add-On Developers are directing AI-Traffic by using runways with various attributes not set or are designing ground layouts with Runway width of Zero or close to Zero. All these runway cannot be depicted properly in EFB v2 because the data in the BGL are not suitable for drawing a RWY. Workaround: EFB v2 features a specially designed routine using BGLs placed into a dedicated folder within the Client's Structure. Please follow the description in this thread: https://forum.aivlasoft.com/topic/3005-afcad/ AivlaSoft has already produced a number of special AFCAD BGLs listed for download in the mentioned section. Whenever an airport shows up with this deficiency, please report it in the General Discussion Thread with a descriptive screenshot. We will then take the necessary action to supply a downloadable AFCAD BGL.

What are you trying to do? Did ou follow the procedure for first start laid down in User Guide "3 Server"? Do you have a subscription for NavdataPro? Did you already create a database? What is your Build No # of your Server/Client?

We did not create those *.wav files. Those are freely available on the net.

Sorry gentlemen, I think we are talking about different issues. Ray, I remember well that you didn't like a few of the standard sounds during betatest (especially the buzzer), but this is not what Dan is talking about. Dan is accusing AivlaSoft of using sounds that have the potential of causing harm or hearing loss to the user. The sounds used in EFB v2 are simple *.wav files and can be found C:\Users\Username\Documents\AivlaSoft\EFB2\Client\Sounds. It should be made unmistakenly clear that those sounds are in no way manipulated in EFB but just played using the normal sound routines of Windows.

The AFCAD File for KHAF is available at: https://forum.aivlasoft.com/topic/3005-afcad/ Please read the instructions carefully to make sure the file is used in conjunction with the rules for EFB v2.

In addition to what Jonas said, there is a short decription of this pehomenon in the User Guide "4. Database", Chapter 2.7 EFB v2 specific "AFCAD" files. Such specific files can be found in this forum under the thread Contributions/AFCAD. In the case of KHAF we haven't set up a specific file yet, but we will take care of that airport and publish a respective file within short time.

As you might have experienced in your life, nonsense is something that you can't stop...?. The sounds however are of course controllable a) by the loudness control of your computer or b) on the Settings/Sounds tab, where they can be shut off... A quick search of the Client's Use Guide would also reveal that.

Mr. [noname] ? (see forum rules #2) Please create a set of Support Files. It would also be helpful if we knew the setup of your computer, i.e. whether the Server and Client is installed on the same machine or as a remote server. All this information would save your (and our) precious time if all pertinent information could be given at first instance ? instead of retrieving each piece of information separately. Trobleshooting can only start in an efficient way if we have all information right from the beginning. Otherwise it may become an endless game of Q & A....?

Thank you for the hint. We would never have guessed that this is necessary...? We learn something new every day! But just as a hint from my side: there is no demo, there is only a full version, and this works in quite a considerable number of installations...

Well, it doesn't help updating the database multiple times. More important is whether the path for LIMC is correct (i guess it is, otherwise you wouldn't see it in P3D V4), and whether there is a valid BGL containing the neccessary information. That's all it requires. As we don't know this installation, we can't say anything about that. With older sceneries it is easily possible that they use the default BGL. Check the scenery path of your LIMC installation for a valid AFCAD BGL.

Please make sure that you run both installers as Admin (rightclick to the installer and select "run as admin" instead of just doubleclicking it. And you have certainly also read in the User Guide ? that also the Server must run with full admin rights ...