Jump to content
Sign in to follow this  
Rhinozherous

No ILS at LOWW Vienna (FlyTampa)

Recommended Posts

Hello!

I never had any problems with EFB recognizing the ILS at the FlyTampa LOWW scenery... today I updated to the latest EFB and now I dont get ILS Approaches.

I already have read thru the Forum here and that this problem occurs to others too.

 

But is this already in a fixing process or do we have to do something as a workaround? (I dont think it is scenery related as I never had a problem with older versions of EFB)

 

Thank you!

Share this post


Link to post
Share on other sites
26 minutes ago, Rhinozherous said:

Hello!

I never had any problems with EFB recognizing the ILS at the FlyTampa LOWW scenery... today I updated to the latest EFB and now I dont get ILS Approaches.

I already have read thru the Forum here and that this problem occurs to others too.

 

But is this already in a fixing process or do we have to do something as a workaround? (I dont think it is scenery related as I never had a problem with older versions of EFB)

 

Thank you!

Hi Klaus,

 

Did you re-run the DbBuilder (not only the "Update Navdata" tab, but also the "Update Simulator" tab)? I have the very same airport and no problems with the ILSes.

 

LOWW.png.9ac43ddf671830deee003c69b20b056d.png

Share this post


Link to post
Share on other sites

it seems that build #113 contains a bug which does not assign the ILS in all situations. I'm working on a fix. Sorry for the inconvenience.

 

Workaround (only until build #114 will be available, and only if you have to run the "Update Navdata" only):

1) Always run "Update Simulator" after you had to run "Update Navdata"

or

2) Delete the database and create a new one. This includes the internal call of the above mentioned function.

 

You don't have to run both workarounds, only 1) OR 2).

Share this post


Link to post
Share on other sites
6 hours ago, aivlasoft said:

it seems that build #113 contains a bug which does not assign the ILS in all situations. I'm working on a fix. Sorry for the inconvenience.

 

Workaround (only until build #114 will be available, and only if you have to run the "Update Navdata" only):

1) Always run "Update Simulator" after you had to run "Update Navdata"

or

2) Delete the database and create a new one. This includes the internal call of the above mentioned function.

 

You don't have to run both workarounds, only 1) OR 2).

 

Thank you!

I used workaround #1 and it worked!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...