General Category > General Discussion
Aivlasoft EFB - Runways Missing in FSDT/Flightbeam airports
bhorv67:
Seems there's some issue for me using Aivlasoft EFB in some of the FSDT/Flightbeam airports. Not sure if this has anything to do with the new way these airports are stored in the file structure where the areas are greyed out in the scenery list within P3D.
Airports in particular are KORD and KMSP. I'm missing runways in EFB in both of these airports, although the AIRAC data does have them listed correctly in the wpNAVapt.txt. I've tried updating the airports by triggering new scenery added in the EFB Data Provider, but the areas that are greyed out (as mentioned before, all FSDT & Flightbeam airports) are not scanned by the new airport search.
Has anyone else had this issue and is there a fix? Thanks
BuddyDog:
AivlaSoft EFB was based on AFCAD's dating all the way back to the original FSX, so there are a lot of things that Aivla Soft will not recognize.
Please see this thread in AivlaSoft's forum.
https://forum.aivlasoft.com/index.php?/topic/2147-what-i-have-learned-about-adding-runways-and-scenery/
bhorv67:
Thanks- I've looked through that thread, unfortunately it didn't help.
I'm still convinced the problem has something to do with how FSDT moved their file structure and why their airports are greyed out of the scenery list in P3D. This wasn't a problem before that changed.
I'm still running v3.4 and probably will be for a while - until all the addons I'm using have been updated to v4. I'm expecting to still be here for a few months. Luckily with the 1080ti I just got, v3.4 is looking better than ever.
virtuali:
--- Quote from: bhorv67 on June 20, 2017, 04:14:04 am ---I'm still convinced the problem has something to do with how FSDT moved their file structure and why their airports are greyed out of the scenery list in P3D.
--- End quote ---
Sure, but the REAL cause of the problem, is the utility you use hasn't been updated to support what is the officially suggested method to install a scenery in P3D, starting with V3 so, utility developers had almost 2 years to prepare to support it.
We can only hope that, now that we (and other developers too) started using this system, utilities will finally be updated, if they want to call themselves P3D-compliant.
Captain Kevin:
--- Quote from: bhorv67 on June 20, 2017, 04:14:04 am ---I'm still convinced the problem has something to do with how FSDT moved their file structure and why their airports are greyed out of the scenery list in P3D. This wasn't a problem before that changed.
--- End quote ---
Only problem in that theory is that Flightbeam's KMSP doesn't use the FSDreamteam Add-on Manager, as Flightbeam created their own with that one.
Navigation
[0] Message Index
[#] Next page
Go to full version