lonewulf47

Did you read the above tip about the actually loaded profile? Just use the "PRFL Filter" knob on the Airport Selection Panel to bypass the profile restrictions.

Do you have the correct database selected here? Btw, if you start the Sim BEFORE EFB the proper database should be loaded automatically. Also check whether the proper FSUIPC version is installed. For P3DV5 FSUIPC 6.0.3 or higher is required.

Three questions come into my mind: 1. Do you have databases created for all simulators? 2. Do you use the proper version of FSUIPC for each simulator? 3. Did you start the simulator PRIOR to starting EFB2? Automatic recognition does only occur if the simulator is already running

Cannot confirm the issue. All data available here:

Hi Michael, Unfortunately this is one of the mysteries Asobo/MSFS still keeps for themselves and so far we haven't found a definitive answer. MSFS draws the Parking Stands/Taxiways names despite the Developer missing the appropriate entry in the "delete section" (as Gaya did for this airport), EFB for obvious reasons has to consider it. So in the present BGL of this gaya installation the default names are depicted in the EFB ground map. Whenever an airport BGL is missing this entry in the "delete section", the default names and numbers are decoded. As a remedy you can replace the following BGL in your installation: Loww-scene - static.bgl It is to be found in "\Community\gaya-simulations-airport-loww-vienna\scenery\Gaya\Vienna". Make a safety copy of the old BGL and re-run the DbBuilder with this new BGL. All TWYs and Gates will be correct thereafter.

There were absolutely NO changes within that field of the database building process in update #128. I build a new database almost daily on two different installations, one of them containing almost 500 airports and I do not see any problems with procedures. You might waht to check your installed database. Do you use Navigraph?

Luis, It llooks to me as if you did not insert any departure RWY in your routing. So the A/C was not properly positioned to overfly tne necessary waypoints. Your active waypoimt is still "PTS". Even if there are no SID's, you still must insert the departure RWY with a convenient RWY extension. This is not a specific problem with Simbrief but with routing application. You did not overfly the first waypoint "PTS". Edit: To overcome this situation simply select "DIR TO" to the next waypoint.

Thanks for reporting, Michael. great to hear that it works now.

Hi Michael, I see that you are using P3DV5, right? Maybe the Add-On used on this simulator has an outdated ILS? I can't say because I'm only using default data for this airport on P3DV5 and there is no such error showing up.

Sorry, it is simply not possible for me to find out what you are doing with your profiles. I was talking about removing the old filename ynd you are talkin about removing the profile. Furthermore I was pointing to the *.air filenames from the FSL buses that seem to look strange to me. Nevertheless I can't really say whether they are correct or not. If the profile that you forwarded in your previous post is used WITHOUT the "A320" filename, I don't see anything that would prevent the profile from loading - except that the filenames need to be verified - which I can't do as I do not have this installation. So again: Please verify the *.air filenames for proper writing - character by character. If only one of these characteres is wrong, it can't be recognized. Maybe someone else using this FSL Bus can step in here? I'm out of ideas...

Hi Michel, To avoid a conflict with the existing A320 profile, it is important to delete the old filename "A320" or "a320", otherwise two profiles with the same key exist. Once you have removed the unnecessary airfile name, don't forget to close and restart the Client inorder to allow reindexing the profiles. As for the filenames: "A320-232 (sl-iae)" and "A320-214 (sl-cfm)" I have to rely on your information as I don't have this FSL installation.

No, definitely not. I wonder how you managed to update without replacing this URL. Do you have any Restore/Datasave or similar Apps running? The proper URL should be: https://api.ivao.aero/v2/tracker/whazzup and it is being replaced during the regular update.

Hi Michel, Please post the newly created profile(s) here so we can check.

Tobias, Have you ever tried to use the offered A320neo profile in our \Contributions\Profiles section? Dowload and unzip into the Client's Profiles path. Always when adding a new profile don't forget to restart the client.

please post you newly created profile here and please also post a screenshot of the PMDG aircraft folder containing the *.air file.

There is a profile for the B777-200. However as I do not use the PMDG 777 fleet anymore, I cannot say what airfile name the 777-200ER has. My guess is that it might be "b777-200er". As a test you could enter this into the existing profile and check whether it will be called up. But first you will need to check in the PMDG installation path for the proper airfile name for this aircraft.

Sorry Bernd, you report three different issues: Taxiways not indicated, no manual input, "Taxi" field does not react.... Have you tried to restart EFB (Server AND Client)?

Hi Charlie, As far as the encrypted layout files are concerned, there is no solution possible and will never be. That's the culprit with individual encryption. For all other cases we will introduce a possibility to create a ground layout BGL (by any official means, e.g. ADE20 or similar), rename it to *.MFS and put it into the AFCAD path of the Server. This will allow EFB2 to render such a ground layout with highest priority. See Manual 4, Chapter 2.7 EFB specific "AFCAD" files. The ending *.MFS will enable EFB to distinguish between FSXP3D files and MSFS files. The next update is due to be released within short time. We had to introduce recognition of the new data format used by IVAO (similar to VATSIM). Users are then highly welcome to provide airport layouts and publish it though our website.

Hi Ricardo, Thank you for the information regarding the database. As for the CRJ's: There is a profile for the CRJ-700. Just open the profile in the profile editor (please see the manual about that) and add the airfile name "crj7" (without the "") into the input field for the airfile names. Then select "OK" and RESTART the client. This will re-index the profiles and thereafter the CRJ-700 profile should be available in EFB. As I don't have the CJ-550/700 I'm not using any of these profiles. Maybe some other users here will step in and provide you with a profile for the CRJ-550.

Hi Ricardo, For any reason that I don't know yet I can't download the attached flightplan. Neverhtless I have recreated the very same routing in SimBrief and imported into EFB2. See attached screenshots: This is the routing as it is presented after downloading with my SimBrief ID: and this is the routing when completed with SID and STAR: I do not see any warnings regarding "wrong waypoints" at any stage. So the question arises whether you really are using the latest AIRAC Revision in EFB2. You mentioned that you are still in the evaluation period. Maybe you are still using the Navdata Files from the basic install? Can you check this in the following directory, whether you have exactly the same files there (replace the pathname "user" by your username): Other than that I have no idea what is wrong in your installation. In any case I can use the suggested routing without any problems.

How do you export the file? Can you post the flight plan file here (should have the ending *.efbr) for investigation? I can do it both ways without any problems - i.e. either export the file dirctly from SimBrief and then copy it into "C:\Users\User\Documents\AivlaSoft\EFB2\Client\Routes" or using the SimBiref Downloader, which copies it directly into the mentioned path. Both ways work flawlessly. Nevertheless I ask myself why you don't use the direct import into EFB with your SimBrief ID number.

One of the oddities of MSFS that we haven't found out about yet. I have two installs of MSFS running on two different computers. In my first install I see the following line: 2021-06-22 19:08:00.996 Debug : Airfile name: dc6b whereas in my second install I see: 2021-06-23 09:33:11.350 Debug : Airfile name: dc6 both when the DC6B is loaded I have seen also on other aircraft, that not always the same airfile name is returned. We have no idea what the reason for this is. As an example I have seen both "optica" and "opca" for the Edgley Optica. In any case, DO NOT USE THE SAME AIRFILE NAME IN TWO DIFFERENT PROFILES! This will lead to unforseeable results!

Communication between EFB2 and P3DV4.5 is exclusively done by FSUIPC. It might be worth checking whether the most recent version of FSUIPC is installed on your system. According to P&J Dowsons download website it is V6.1.2.

I see, that's where the scaling hits it's limits. You can't scale up unlimited (My guess is to have better visibility). You might try with a somewhat reduced enlargement, say 125%. nevertheless you might have noticed that as soon as the window width is reduced, some buttons are "collapsed" into one button. In your screenshot e.g. the "TFC" button will expand to three buttons "TFC", LBL" and "TCAS" as soon as you click it. Same happens to the (only partially) visible "MISC" button.

Sounds great! Thanks for reporting.