river7

Hallo Urs, thanks again! Just for the record: While ADEX and FS Commander (old version 8) can read and display this scenery, various "decompiler" tools I tried (BGLanalyze, BGL2XML, etc.) all choke on it and crash. So there is indeed definitely something not quite right with the scenery. EFB is just the one to notice it . Cheers, Martin

Hallo Urs, many thanks for looking into this so thoroughly! As to the paths, that seems all OK, but just in case: scenery.cfg entry: Local=Addon Scenery\EVRA [and the BGLs are in ...\Addon Scenery\EVRA\scenery as they should be]. Info about EVRA from SceneryUpdate_log.txt: ... Info Area EVRA Riga, Latvia, required=False, active=True, layer=202, path=E:\FSX\Addon Scenery\EVRA ... Info Analyzing folder: E:\FSX\Addon Scenery\EVRA After that all further steps are also reported as successful, no error messages. So apparently the updater finds, reads and understands the scenery OK, but can then not display it because of that error in the BGL file. (I have in the meantime checked some other add-on airports, and they are all correctly displayed in EFB, so it is really a specific EVRA issue, nothing general.) So I have to try and look into the scenery itself. I'll also update EFB ASAP; I was aware that should be done, but didn't want to change too many things at once. Finally, out of curiosity: What is that debugger from which you took the screenshot? Is it your own one for EFB development, or some generally available tool? Thanks again for your help! Cheers, Martin

Hallo Urs, many thanks for the very prompt reply. That was my third bullet above: checked in the log file that the new add-on scenery folder was indeed seen and analyzed, no errors reported.And the "Info" in the logfile correctly reports the scenery as "active". Hmm -- I have done scenery development myself, both in FS9 and FSX, but have never heard of such a thing. Is it part of the AFCAD2 BGL file? Or an FS9 thing perhaps? Can one directly check for it, e.g. with ADEX (Airport Design Editor X) or similar tools? Or are you perhaps referring to exclusion files (or perhaps just exclusion rectangles)? And why would EFB be thrown off the track by this (and still see the default scenery) while in FSX the add-on does take priority (I checked of course, and do see the proper add-on in FSX). BTW this is the scenery in question (EVRA, Riga), in case anyone wants to have a look. Update: I googled and so far found one (1) reference which says that "delete sections" are part of runways.txt (as generated by Pete Dowson's makerwys.exe; for me that *.txt file is a 100 MB / 1.6 million lines monster). That file does indeed contain "deletion" info for other airports, but has EVRA only as the default one. Is this what you refer to? Does EFB depend on makerwys.exe and runways.txt ? Seems to be an "interesting" case after all. All further enlightenment welcome! Cheers, Martin PS. Just to make sure: DataProvider_log.txt in my case does not mention individual sceneries and their folders; it reports only on the start of the application and the connection (SimConnect, TCP, etc.) What I checked was SceneryUpdate_log.txt, which does list the sceneries processed (see above).

(...and yes I did run a scenery data update... ) Greetings, I have a problem where my EFB (1.5.0.19605) continues to display the default airport layout and not the newly installed add-on. Here is what I did / tried: installed add-on airport (which uses an AFCAD2 file; I could thus check the layout in ADEX, and it's very different from the FSX default one) ran the EFB Data Provider "Simulator scenery data update" checked in the log file that the new add-on scenery folder was indeed seen and analyzed, no errors reported. restarted both Data Provider and Display Unit still saw the default airport layout in EFB reset the Airport Data Cache (DisplayUnit>System>Settings>Miscellaneous) restarted both Data Provider and Display Unit again still seeing the default airport in EFB. What else could be preventing the add-on from turning up in the Display Unit? Are the default airport data somehow still "overwriting" the ones from the add-on? The AFCAD2 file is in the add-on's scenery folder, not in the global one (...Scenery\World\scenery), but that is the case for all my add-on airports, and EFB never had a problem with that. Thanks in advance for all tips and pointers. Cheers, Martin

Hello, did you activate the traffic display? System > Settings > Charts > Traffic > AI/Multiplayer Traffic Cheers, Martin

Hello, I was running FSX and the DataProvider on machine A and the DisplayUnit on machine B (both EFB components at v.1.5). Everything worked fine. But now machine B has broken down, so I tried to add the DisplayUnit to machine A, too. I re-ran the original installer (v.1.3) and checked only "Display Unit", installing to the existing EFB folder. Apparently that approach was too simplistic: The installation went smoothly, and the DisplayUnit does start. But the DataProvider no longer starts; it gives a long and complex error message (unfortunately not copypastable ) "Could not load file or assembly 'AivlaSoft.Efb.Common, Version=1.5.0.19603 [...] The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)." Version incompatibility perhaps? I tried to delete DataProvider_UserSettings.bin but it did not help. Can this be fixed in any way, or do I have to uninstall and re-install (and re-update) from scratch? Thanks for all tips! Cheers, Martin UPDATE: Thanks for the replies Case could be solved very simply, by re-running the v.1.5 updater* on top of everything else. EFB now working on one box, as desired. Cheers, Martin * I had forgotten that I had this as a "stand-alone" file; I thought the update had been done from within the program.