lonewulf47

Compare your IVAO URL with the one I use. In my install IVAO traffic is working normally. I haven't changed anything lastly.

Not entirely true. There are no SID's for RWY 04C/22C in the Navigraph Cycle 2213, at least not to my last information based on this AIRAC Cycle.

Yes, I became aware of this too. RDPresets is not very patient designing a proper ground layout. As a remedy please copy the attached file into your "ARPT" folder in the Client's data structure and then restart the Client (if still running). That's exactly why we designed this filetype some months ago. ENBR.arpt

To find out more about profile calls in X-Plane, please refer to the manual, "5 EN Client, Chapter Profiles/Airfile names", page 103

The DC3 returns either "dc-3" or "douglas dc3". Enter both airfile names into the respective section. You can easily find out about these names by looking at the server protocol when starting the DC3 in-game. This has been described many times here in the forum.

Sorry, this didn't answer my question. As for graphic conversion: I use XnView freeware. The above graphic is in *.png format and uses 15.0 kb.

Did you check with Navigaph whether your SimBrief ID may possibly have changed?

H Erdal, It is absolutely impossible to see what has happened on your computer with just a snippet of a screenshot. Please make a set of support files and attach it to your next post or alternatively send it to: support@aivlasoft.com

You "M"anually selected the airport. See manual 5.Client: section "5.1 Selecting an airport"

A313.profile.zipHi, I have no idea what IniBuilds uses as ICAO-Code (this is usually what the designers use as the source for the airfile name). Nevertheless this extremely unusual name "tt:aircraft.ui_model" is only a placeholderbut still recognized if entered as the airfile name, as is shown in the screenshot below. I have checked all MSFS aircraft. No other uses this. As long as no other aircraft shows up with this anomaly we're fine to use it as airfile name. Maybe after some updates a more reasonable name might show up. It can then be entered as an additional name into the profile's airfile name list. In any case the airfile name shows up in the EFB-Server Protocol page, as shown below: Find attached the profile I'm using. This is however a temporary measure. We will check whether we can find a definite solution to this problem and then possibly issue an update. A313.profile.zip

Did you REBUILD your databases after the Update? Please DELETE the old databases and CREATE new ones. That will most probably cure the issue.

Well, this is one if the reasons for the Update ! Did you notice the message in the update splash screen after the update which reads: THIS UPDATE REQUIRES A REBUILD OF ALL DATABASES !! So - DELETE all old databases an CREATE new ones and you'll be fine!

Did you rebuild the database? i.e. DELETE the old database and CREATE a new one?

It would be very helpful if you could tell us, WHICH airport is affected... Plase see also our Forum Rules.

Please read our Forum Rules before posting

Hang on, Microsoft/Asobo once more surprised us with some changes within their database systematics. We have to investigate. No need to repeat findigs anymore.

Server Error at the Sigmet Server Side. There's nothing we can do about that. It happens at random and cures itself after a while. There's no impact on EFB's functions other than that the SIGMET's are not available at this time.

Yes, I agree. I have noticed that too. This seems to be a change within the WorkingTitle G1000NXi. As I wrote before, the G3000 and the G3X work normally. Again, there is nothig we can do about this, if a developer decides to change major behaviour within the dataset.

Possibly also a problem with WorkingTitle's G1000NXi. The G3000 and G3X from WorkingTitle still work normally after updating to SU10.

Hi Robert, Well, first of all it should be the developer's task to provide proper taxiway and parking position layout. In case of the mentioned EGQS Lossiemouth AB I cannot comment as I don't have any scenery besides the default, which has a proper layout. So it seems that - whoever developed it - should care in first priority for a proper layout. Additionally be aware that we do not establish corrected files for freeware scenery. In any case a list containing ICAO Code and Developer would be more helpful.

Hi Rolf, here's the zipped profile. Unzip it into the profile's folder of your client's installation. Default path is: "C:\Users\<username>\Documents\AivlaSoft\EFB2\Client\Profiles". You may change any parameters to your liking with the Profile editor. I entered "143" as the airfile name. Just be advised that in some rare cases MSFS is not always returning the same airfile name. This is one of many MSFS mysteries, that couldn't be solved so far. If this happens, just look for another (new) airfile name showing up in the Client's window and add the new name to the existing airfile name. Remember to restart the Client after adding the new profile. BAe146-300.profile.zip

Hi Rolf, I could provide you with a BAe145-300 within short time, however, as I do not have this A/C in my collection, I'm unable to determine the airfile name used by JustFlight. To find out please see here: https://forum.aivlasoft.com/topic/6812-i-cant-create-a-new-profile-for-the-pmdg-737-800-msfs/#comment-30300 , second entry.

Please see here (and please observe our Forum Rules) : https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/#comment-17906

Not sure, whether you refer to the OneDrive (Cloud) of Win10. Anyway you might read this: https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/#comment-17906

Yes, I see the same error. It seems that EFB is somehow irritated by the WYP name "TOSID". We have to check on that. As a temporary remedy use the "COPY/PASTE" tab and copy the route string "ZYTX SID TOSID A588 UDETI W106 MAKNO W5 GUMED V42 REPOL W4 WXI V33 LEKUB STAR ZHCC" from RouteFinder into the respective field. This will work normally.