lonewulf47

Hi Juergen, I take it that you use an AddOn for SEQM as it doesn't exist in the default database (only SEQU = the old airport is showing up there). The Filter Criteria for any Aircraft are only RWY Length, Width and Surface Type (see page "Filters" in the Profile Editor. How does the SEQM Airport Ground Map show up in EFB v2? Could it be that the RWY width is 0 (zero) due to the ondulated terrain? Other than that I don't have an explanation for this behaviour as indeed the "normal" filter criteria would not prevent SEQM from being selected/used. Could you indicate the Developer of SEQM? I will then have a look at it.

Hi ???? (please observe the Forum Rules regarding your First Name) Did you install FSUPIC?

It's explained in the above mentioned manual on page 65:

No, EFB v2 does not do things differently. I just created the same routing with PFPX, however with a different result. This is how it looks in the Flight Plan Window of EFB v2. I have no idea how your PFPX setup is creating flightplans. Here it works flawlessly. I do however work with latest updates of PFPX in every respect (database, DCT routes, hotfix).

Leodirk, It's very strange. The ServerLogFile you just posted here also carries the timestamp from november 15th (20181115-2036 hrs), whereas the ClientLogfile is with the correct date of today's november 18th (20181118 1742 hrs). Same applies for the entries in the logfile. I'm sorry, I have no idea how such things can happen. I would propose the reboot your system and check the date thereafter. After having run EFB v2 at least once, all new entries in the Logfiles and SupportFiles should show the current (actual) timestamp. More important though that things are running now smoothly again,

Have you ever considered the fact that all software coping with a Routing (aka Flight Plan) need to work with EXACTLY the same AIRAC data Cycle? I have no way of checking what you are using on your system. The only thing I can do is planning a Routing with the most recent AIRAC Cycle 1812 and using it in EFB v2 and other Addon A/C with exactly the same AIRAC Cycle database. This works flawlessly. Any other combination is simply not useful and may or may not generate errors. Same applies to Routings created with PFPX. I do it for months (if not for years when accounting for the Beta Phase) without any problems.

This is not true. EFB v2 works seamlessly with RouteFinder and PFPX. Please do not post such WRONG information. If you do not know how to do it, it does not automatically mean that it is not working. RTFM is always a good start. It's clearly written in the Manual. If Admin Privileges are required for a certain exdecutable, it's not the user's choice whether to comply with this requirement or not. If a User does not follow the procedures laid down in the User's Manual, how can you blame someone else than the User? Yes, in contrary to quoting meaningsless 3rd party forum entries, this is a meaningful remark. Thousands of users prove the contrary.

All I can see is that the latest Logfiles are from november 15th and the Server is NOT connected with a valid License, but still in Trial Mode for remaining 22 days. Furthermore I see that you did a dseries of flights in Swedish Airspace which seemed to have been working normally. This is going to be a bit confusing... Also the Logfiles are dated from november 15th. How comes? I thought you created them right before posting (which should always be done).

Hello ??? (please observe the Forum Rules) This means that the Server and Client have established communication, but the server does not connect to the Simulator. This would be indicated by the amber Message "Simulator" in the Message field in the upper right corner of the Client. Can you please be a bit more specific (again according to Forum Rules, Item 3). Please also post a set of Support files as described here: https://forum.aivlasoft.com/topic/3046-how-to-create-a-support-file/ either in this thread or send them to support(at)aivlasoft.com.

Please refer to the Forum Rules and refrain from posting such meaningless remarks.

This limitation is from freeware FSUIPC, not from EFB v2. Increasing this limit is only possible with full FSUIPC (payware) version.

No, there are no updates. Nevertheless I must add that I use it since the beginning with P3D V4.3 without any problems. You might want to check whether SimConnect is still working properly after upgrading from V4.2 to .V4.3. In rare cases SimConnect needs to be reinstalled. Other than that I don't see anything wrong as - as I mentioned before - I use SimpleCam on two different systems with P3D V4.3 without any problems. Be also sure that no other programs accessing the Camera Positions are in conflict with SimpleCam.

Hi Jürgen, That sounds great! Congratulations! So - for all future users of both FSX:SE and P3D v4 with problems in the setup you will be able to provide some good advice..? as we here at AivlaSoft do not use FSX:SE.

Hi ??? (please check the Forum Rules) Of course it is. Please see the Manual "5 Client", Chapter 7.1.4 Miscellaneous ff. the Traffic Labels can be configured to you personal liking.

Hi ??? (please observe the Forum Rules) Sorry, your inquiry got somehow "lost" as we were busy at the traditional FlightSim Weekend in Hergiswil/Switzerland. The depiction of a holding is dependent on the information that we can derive from the respective ARINC data. If it is clearly defined as a HOLDING PATTERN, we depict it with the information provided. If it is marked with an "ENROUTE HOLDING" flag only, we can only depict it as a standard Right Holding Pattern on the last inbound leg. Many of the holdings at the end of aMAPt are unfortunately coded this way. For the specific holding you mentioned here we will have to check with the ARINC database, which of the two cases is used. Nevertheless of course there is always also the possibility that something went wrong. We will check and be back in due time. Thanks for your understanding forthe delayed answer.

Difficult to say but it looks as if EFB doesn't find any default scenery. Did you check the FSX-SE install to be complete with everything at its proper location?

Juergen, I'm not really knowledgeable on FSX:SE, but frankly, I don't understand what you wrote about the FSX:SE installation. On one hand you explain that Steam doesn't let you install FSX-SE in another directory than the default, on the other hand you explain that you have installed FSX-SE on a separate SSD. If Steam insists on installing a program into a specific (system) directory and drive, I doubt that any redirection of the install will do any good. You could do it on the FSX, if you knew exactly how to do it. Same applies to Prepar3D. Whenever you want to install Prepar3D into another place than default, you first need to create a basic directory and point the installer to it. That's how I did it many times, also with FSX and all on the same drive. Whether this "trick" is possible with FSX-SE is beyond my knowledge. There is really no reason th install these simulators on different drives. Of course you need to run any of the simulators at least ONCE, because many system files are written only after an initial run has been completed.

Hi MR??? (please observe the forum rules) I'm afraid there is nothing to fix as it is exactly the case in EDDF ?! You might check this with the latest AIP Germany AD2 EDDF 4 ff RWY 07L: ILS Z Cat III, AA 3.0°, 111.75 MHz, IFEL RWY 07L: ILS Y Cat I, AA 3.2°, 110.30 MHz, IFNE RWY 25R: ILS Z Cat III, AA 3.0°, 111.35 MHz, IFWR RWY 25R: ILS Y Cat I, AA 3.2°, 109.75 MHz, IFNW ATM we cannot distinguish between two ILS' on the same RWY. Therefore whenever you select one of the 4 ILS' check for the proper IDENT and then select the corresponding "Y" or "Z" ILS. "Y" ILS should have an Apporach Angle of 3.2° iso 3.0°. This is wrongly modelled from the Addon Developer. If using our EDDF AFCAD (see here:https://forum.aivlasoft.com/topic/3005-afcad/) the GS angles are corrected for display in EFB v2, it must however be noted that the approach angle in the SIMULATOR is still at 3° for all ILS', as it is derived as a tuneable Navaid solely from the Sim (AddOn) BGL. To have the real 3.2° approach angles the corresponding AFCAS of the AddOn needs to be changed.

Hi ??? (please observe the forum rules) I see from your partial logfiles that you are using EFB v2 on a Win10 machine with a single Server/Client setup on the same machine. Please use the windows start menu function "AivlaSoft - EFB 2 create Support Files". See also here: https://forum.aivlasoft.com/topic/3046-how-to-create-a-support-file/ This will create two zipped files on your desktop screen. Please post them here or alternatively send them to support(at)aivlasoft.com. BTW Port 13 is not involved in any case with opening the Client. This is solely required for Server Verification during the Trial Phase.

Hi Nigel, This has been discussed previously already, see here: https://forum.aivlasoft.com/topic/2719-missing-runway-0220-on-barcelona-airport-lebl-aerosoft/?tab=comments#comment-15677 The solution is to be found here: https://forum.aivlasoft.com/topic/3005-afcad/

Sorry, you are wrong. See a cutout of the latest AIP Ground Chart of BIKF. The valid Runway designators as of today are 01/19 and 10/28. I have no idea where you get your information from. The official source is the AIP and the ARINC database. Both are depicting the Runways as mentioned above.

Just to make sure: you are talking about a Virus Threat Warning during Server Download and not during Server Install? On the download side there's nothing else that we can do than checking the downloads on our machines and see if we can reproduce. So far I'm unable.See the most recent screenshot:

Hi Joe, Sounds strange! I just downloaded both Server and Client with McAfee and Windows Defender active without problems. Could you reboot your system and try again?

Can you please post a screenshot of the Client Ground Map of BIKF with the wrong designators? Can you select procedures?

Hmm, extracting the *.zip should not create a folder. It is a single zipped BGL file. It may depend on the way you unzip the file. In any case just copy the BGL file into the AFCAD folder and re-re-run the database updater as mentioned in the description. Great to hear that you have found your way. Enjoy!