Jump to content

lonewulf47

Moderators
  • Posts

    2,643
  • Joined

  • Last visited

Posts posted by lonewulf47

  1. 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

  2. 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.

  3. 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

  4. 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.

     

    A310_profile.png.fb8c30456e5a0d61c75a6a0ba2b5950e.png

     

    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:

     

    A310_airfile.thumb.png.e2c77dce83eba052e4c4303c1a85c8de.png

     

    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

     

  5. 2 hours ago, bobsk8 said:

    ...The only thing that is strange is now my flight plans look like this at the top  TT:Airportek.KLAR ( USA)  

    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!

  6. 1 hour ago, CmteSiqueira said:

    There are all airports, not found in the base data

    It was after I updated, today.
    Yesterday everything was perfect.

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

  7. 1 hour ago, oskrypuch said:

    But, it may be even more than that, I didn't think that the flightplan transferred at all into MSFS, if using the 1000. Will double check that, it may be something along the lines of above.

    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.

  8. 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.

  9. 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

  10. 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.

×
×
  • Create New...