abax2000

According to your experience, does it happen to get a METAR in Ivap, but EFB does not show untill only when you are closer to the airport (60miles)?

The original issue is closed; everything works as described in your answer. It must have been what you described as "temporary techincal problem in the simulated world" (sic). When using Ivao connection (and no other weather reporting tool), I think that sometimes I don't get the METAR I see in Ivap, but most probably downloaded from NOAA, although "Weather Provider" drop menu is on FSX setting. Can it be like this?

The usual setup is FSX+EFB+ActiveSky (+IVao when online), which I expect to be quite common to lot of simmers. "Active Sky data file" in EFB is not active, but anyhow I would expect that EFB would be fed with METAR's from FSX (which is fed by AS). Nevertheless, EFB does not provide any FSX METARs. Is this systematic, or do I do something wrong (in the overexcitement brought by 1.3.1)? PS: 1. I did read EFB manual before asking. Maybe inattentive, but not lazy at least. 2. where the ActiveSky data files are found in order to correctly point the "Active Sky data file" option?

I have been through Navigraph charts also (as I should have done in the first place ). 36L,18L are prohibited for landing (except in emergency), 04 has only SRA procedure. 36R, 18R have not SID's; did not find any explanation but it seems that has to do with airport operation issues. It seems that Navigraph is off the hook this time

There are missing procedures missing, e.g in EHAM: approaches for 36L, 18L, 04 and departures for 36R, 18R. Latest airac used 1103 (same with previous) with 1.2 and 1.3. Any insight/suggestion on this? Otherwise, EFB has become a formidable tool. Compliments to all involved.

I am not a realworld pilot, but my understanding is according to Oscar's note. I attach also the relevant part of Navigraph legend (which is different, but still clear). As for "voting" for an amended notation in EFB, I would refrain as Oscar (and other real world aviation profs) can provide better consultation (at the end of the day the goal is "as real as it gets" and not "according to everyone's taste" ). Just please keep altitudes in bold and bigger font (as currently is). Closing remark from me on reference points: it is much more reliable and easy to have waypoints defined as DME distance from a navaid on a radial of which you are actually riding (for example, please see the other attachment). Then you easily know when to turn, in a quite busy part of flight. Being that said, I fully understand the programming and data restrictions Travis mentions. Regards, Apostolos

Hi Travis, as you mention, there are differences in notation used depending on the publisher and this makes things more complicated. Take for example SIDs for EGNM (just because it was the last in which I noted some ambiguities ). If you look at the latest available Navigraph published SID South, Southwest (p.30-1, 21 OCT 08) all is quite clear (if you take into consideration Navigraph legend also). 1. If you look at SID Rwy 32:POL1W in EFB, there are two issues: altitude ambiguity (as to what published altitudes exactly mean, and not the absolute figures which are correct). 2. distances/references of the first waypoints (05DME, 21DME, 35DME) are referring to a diffrerent navaid (to POL and not ILF). And the problem here is that, although geographically correct, the used references are very awkward to be used in flight (while the ones used in actual Navigraph map are the correct ones for inflight use). The two points above (when present) make the inflight use of EFB somewhat awkward; your only choice is autopilot on GPS mode (mainly because of point 2) and still not certain if you are procedure-compliant (because of point1). best regards, Apostolos

Sorry beforehand if this is already answered elsewhere. In such case, please direct to the info. Where a map legend can be found (explaining explicitly things like 3000+ or 5000- etc)?

thnx for answering, point taken. It is just that this could be extremely useful in busy airports (or in case pilot's top of descend calculation was somewhat off target ... Apostolos

Looks amazing! A very useful addon would be holding patterns (besides missed approach ones), i.e. in STARs and IAFs. Apostolos

Frans, does this mean that deleting uiautomationcore.dll did not totally freed up from hangups and you still experiencing them although uiautomationcore.dll deleted? Apostolos

I realise that Urs...Just keep dreaming... Apostolos

UIAutomation.dll is a problem on its own and a different problem is OOM hangups. Christian issues seem to me like OOM related, but this is only a hunch as I am not an expert. I have installed some time ago the UIAutomation.dll fix that Frans mentions which for quite some time freed me up by hangups. Now, I think I will try the new fix but I am not sure if removing completely the dll affects other things in W7 also. As for Christian's question some posts ago, I use UTX Europe, GEX Europe and STLandclass but I had the same issues and before installing them. Anyhow, it would be great if Urs could find a magical solution to get EFB from within FSX (and not windowed) as windowed mode has inherent deficiencies (esthetic and frame-wise). I would be offering to buy to Urs the full Harry Potter series if that helps .

Sorry for late response, but I was out of action for some days... I tested FSX and EFB without taskbar autohide and it gave several trouble free hours and flights. And then hangup again with the same old message...this time it followed an odd screensaver poping up during playtime (in a long leg over the sea on autopilot with no keystrokes, mouse movement etc)... the system hungup just after the screensaver appearance... So for the time it appears that (for my system at least) i have to avoid autohide and deactivate screensaver. At least until someone finds out the real reason/remedy (lol)... PS. Even with this problem, EFB is still a great product, very close to perfection which hopefully will be achieved in the next update.

Any ideas on the message error?

ok, I managed to replicate it: FSX windowed, taskbar in auto-hide. When the mouse goes over the taskbar area, FSX hangs up. I think that if taskbar is not in autohide does not happen. I will try to verify. Message below: Microsoft .NET Framework Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immiadiately. Exception from HRESULT: 0xC000014B See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type) at a5.f() at a5.a(Object A_0, EventArgs A_1) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- AivlaSoft.Efb.DataProvider Assembly Version: 1.1.0.23865 Win32 Version: 1.1.0.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/AivlaSoft.Efb.DataProvider.exe ---------------------------------------- log4net Assembly Version: 1.2.10.0 Win32 Version: 1.2.10.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/log4net.DLL ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- DevExpress.Utils.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/DevExpress.Utils.v9.1.DLL ---------------------------------------- Castle.Windsor Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.5114 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Castle.Windsor.DLL ---------------------------------------- Castle.Core Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.5114 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Castle.Core.DLL ---------------------------------------- Castle.MicroKernel Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.5114 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Castle.MicroKernel.DLL ---------------------------------------- Rhino.Commons Assembly Version: 2.0.0.0 Win32 Version: 2.0.0.1414 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Rhino.Commons.DLL ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Rhino.Commons.Clr Assembly Version: 2.0.0.0 Win32 Version: 2.0.0.1414 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Rhino.Commons.Clr.DLL ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- Castle.DynamicProxy2 Assembly Version: 2.0.3.0 Win32 Version: 2.0.3.5114 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Castle.DynamicProxy2.DLL ---------------------------------------- AivlaSoft.Efb.Common Assembly Version: 1.1.0.23864 Win32 Version: 1.1.0.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/AivlaSoft.Efb.Common.DLL ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.4926 built by: NetFXw7 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- DevExpress.Data.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/DevExpress.Data.v9.1.DLL ---------------------------------------- DevExpress.XtraEditors.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/DevExpress.XtraEditors.v9.1.DLL ---------------------------------------- System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- DevExpress.XtraBars.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/DevExpress.XtraBars.v9.1.DLL ---------------------------------------- Desaware.MachineLicense20 Assembly Version: 1.1.0.0 Win32 Version: 1.3.0.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Desaware.MachineLicense20.DLL ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- Desaware.Dls.Interfaces20 Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB/Desaware.Dls.Interfaces20.DLL ---------------------------------------- System.Security Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Security/2.0.0.0__b03f5f7f11d50a3a/System.Security.dll ---------------------------------------- Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61259.0 Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421) CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.4927 Win32 Version: 8.00.50727.4927 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5/msvcm80.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

No other addons usin SimConnect. Only addons are UTX, GEX, STLandclass and local small stuff (airports etc in addon library). I remember reading somewhere that there was a problem with windowed FSX (which is the case when EFB is used) and the windows taskbar. I will try to verify. If you know something on this, please fill me in.

i do not get a yelow message (at least when I start the sim and EFB). I have not checked when the problem arises, but when it does the only option is to kill the sim and at the same time DataProvider is killed also (Display stays on). The message I get mentions SimConnect. And yes, I do not use FSUIPC. I will try to capture the message with PrtScn. This issue is quite annoying as it happens in long flights.. so for the time being I will have to carefully save flights, I guess.

Great update, nice job! I am experiencing (both with the new update and the previous one) FSX hangups. The message directs to net framework and the connection between the EFB and the sim. Unfortunately, I cannot save the message (or I just do not know how). This usually happens after an hour of flight. The operating system is W7 32bit (which means preinstalled framework 3.5). I have also installed the recommended Microsoft C++ Library update from the following link http://code.msdn.microsoft.com/KB961894/Release/ProjectReleases.aspx?ReleaseId=2067 Any suggestions?

ok, understood. I thought that there would be a EFB menu list in FSX meny bar.

sorry for late feedback... I just meant that as I cannot open EFB from within FSX, I open it directly doubleclicking the EFB icon on my desktop.

Both FSX and FSB are installed on the same computer and on the same harddrive that also has the operating system installed on.

It is the same computer and both (FSX and EFB) installed on the OS hard disk.

thnx a lot for the prompt response. I will wait for 1.0.4... and I am not asking when exactly when it will be available It seems also that I cannot bring up the EFB menu from within FSX using the assigned shortcut (it is not used by FSX for other purposes). Besides that, EFB is following the flight (being opened in a separate window manually). Did I mess up something during installation (I tried to follow instructions carefully)? OS is W7 32bit Ultimate.

I am still trying out the demo version. It appears that not all Navigraph maps are available through EFB (I have downloaded the latest update from Navigraph). Just an example, Heraklion airport (Greece) approach charts are missing, although all are available through nDAC3. Am I doing something wrong or misunderstood something?