ScottecLEMD

Hi Urs Yes for me the addition of a CSV version would be great! Thanks and regards Ken

And here is your file saved in Excel format! Scratch that, I am not permitted to upload this kind of document

Hi Ray Yes, for the moment it will be a manual task. The Flight Logs should be in the following folder unless you have made any changes: C:\Users\XXXXX\Documents\AivlaSoft\EFB\UserData\FlightLogs - where XXXXXX is your username. I have a full Adobe Acrobat programme as I use it for my work so not sure if the basic reader has a similar function or not. Brgds Ken

Assuming that you a valid copy of microsoft excel and Adobe Acrobat (not sure if you can do this just with the reader app or not) on your PC. Open up the PDF IFR Flight Log, Once displayed, click File, Save As Other and then you should see a list of available options including Word, Excel, HTML etc. Works perfectly. Best regards Ken

That would be good, in the meantime you can still export from PDF. Ken

Even in its present format, EFB 1.6.8 is the best add on for FSX/P3D. I never fly without it. Like everyone else I am eager to see v2 released....how can you make the best better? Brgds ken

When you installed THE UK2000 scenery, did you select static aircraft? This uses gate assignments and renders them unavailable and will not show on any other programme, ie EFB, FSTramp Ken

Hi Urs Actually, they appear disabled for the Dash-8 but are enable for others (PMDG, QW etc). However, the Off blocks always appears to be completed and I found out the hard way that, if you press any of the other buttons you cannot change them with a subsequent push I wonder then how SmartCars gets the informatiom as the Off/Out/In/On times seem to work correctly when I use this in conjuction with the VA that I fly with. Anyway, no big deal, I can wait, eagerly for V2. Best regards Ken

Rob On the same website there is a Navaid editor tool, you might want to try that, but at your own risk . UK2000 usually use the underlying default .bgls for the navaids. Regards Ken

Hi Urs That's great, thanks for confirming this, Just one follow up question, you say that the buttons are enabled once the first engine is running, does that mean I should be able to manually click for the blocks off as when I do it seems to have no effect. Regards Ken

Rob Try this. http://www.aero.sors.fr/navaids3.html, there is an updated there for most of the European navaids. Ken

Hi Guys I have noticed a slight problem when using EFB and the Majestic Dash 8. I am guessing this has something to so with the Dash 8 being modeled outside of the native FSX/P3D envronment. When flying the Dash 8, the off blocks time is not being taken from there brake release but from when I save and activate the EFB flight plan. So, before I have even loaded the flightplan in my stationary Dash 8, EFB thinks I have already pushed off stand. I notice on the flight log page that there are buttons for the off/out/on/in times but these are not user selectable. Maybe that would be a work around whereby you can click the button once you start the push? Thanks Ken

Having used EFB in Prepar3D V3.0 for almost a month now the only issue I have is the Off Blocks time in the Flight Log. This seems to be automatically completed once the sim launches, not when I actually release the parking brake. I thought it might initially be associated with the Majestic Dash 8 but I've also noticed it now on PMDG and Aerosoft products. Still does not stop me using this excellent software to it's full potential, in my opninion one of best flightsim addons. Roll on V2.0. Ken

You might want to turn off UTC syncronise. FSX/P3D have an inherent fault whereby they do not keep time correctly so when you set the UTC synconise option, EFB will keep the time between your PC and the Flightsim syncronised which will cause the message. Ken

Hi Urs, Many thanks for the reply. I will look into changing the port number since I think this is due to running the EFB and Majestic Control panel at the same time; was never a problem prior to installing Majestic. I will give it a go and monitor the situation and report back if not sovled, Thanks again. Ken

Hi Currently using EFB Version 1.6.5 on Windows 10 and Prepar3D V3.0 I have an intermittent problem whe I launch the data provider windown (with Admin rights), normally when either the NavData has been updated to a newer cycle or I run the Scenery Updater, as follows: "Only one usage of each socket address (protocol/netwrok address/port) is normally permitted. I am running the Data Provider and the Display Unit on the same PC. This has only started happening with V1.6.5 and, as mentioned above, I can only tie this to either a Nav or Scenery update. The program seems to initialise again without problem after restarting the PC. Any help would be much appreciated. Thanks and regards Ken Update! Just noticed that when I closed the Majestic Dash8 Control Panel the problem disappeared so it would appear to be more related to having this running first. So, if I load the Data Provider 1st then the MJC Panel then everything is OK. **************************************************************** See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at er.b(IPEndPoint A_0) at ic.a(id A_0) at fe.e() at fe.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: 4.0.0.0 Win32 Version: 4.6.127.1 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- AivlaSoft.Efb.DataProvider Assembly Version: 1.6.5.18356 Win32 Version: 1.6.5.18356 CodeBase: file:///D:/AivlaSoft/EFB/AivlaSoft.Efb.DataProvider.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.6.93.0 built by: NETFXREL2STAGE CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Castle.Windsor Assembly Version: 3.3.0.0 Win32 Version: 3.3.0.2412 CodeBase: file:///D:/AivlaSoft/EFB/Castle.Windsor.DLL ---------------------------------------- AivlaSoft.Efb.Common Assembly Version: 1.6.5.0 Win32 Version: 1.6.5.0 CodeBase: file:///D:/AivlaSoft/EFB/AivlaSoft.Efb.Common.DLL ---------------------------------------- DevExpress.Utils.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///D:/AivlaSoft/EFB/DevExpress.Utils.v15.1.DLL ---------------------------------------- Castle.Core Assembly Version: 3.3.0.0 Win32 Version: 3.3.3.2300 CodeBase: file:///D:/AivlaSoft/EFB/Castle.Core.DLL ---------------------------------------- Desaware.MachineLicense40 Assembly Version: 2.0.0.0 Win32 Version: 2.0.5.2 CodeBase: file:///D:/AivlaSoft/EFB/Desaware.MachineLicense40.DLL ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- DevExpress.Data.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///D:/AivlaSoft/EFB/DevExpress.Data.v15.1.DLL ---------------------------------------- DevExpress.XtraEditors.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///D:/AivlaSoft/EFB/DevExpress.XtraEditors.v15.1.DLL ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.6.127.1 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- DevExpress.XtraGrid.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///D:/AivlaSoft/EFB/DevExpress.XtraGrid.v15.1.DLL ---------------------------------------- System.ComponentModel.DataAnnotations Assembly Version: 4.0.0.0 Win32 Version: 4.6.93.0 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll ---------------------------------------- DevExpress.XtraBars.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///D:/AivlaSoft/EFB/DevExpress.XtraBars.v15.1.DLL ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Xml.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- System.Security Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll ---------------------------------------- System.Management Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- UIAutomationClient Assembly Version: 4.0.0.0 Win32 Version: 4.6.79.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationClient/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationClient.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: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> 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.

Works fine in v3.0. Change the destination folder paths and all is good. Ken

Hi Urs Given the fact the removing the AIrbus fonts solved not only my EFB font problem but another unrelated font problem, maybe Windows 10 thinks that the Airbus Fonts are the default Arial?? How I have no idea..... Regards Ken

Hi Pauga Thanks for the info, I did remove the Airbus fonts and everything for me is working OK. It also solved the font problem for another progamme that I have, totally unrelated to flightsim. Regards Ken

Guys I was one of the lucky ones in that EFB worked for me on Windows 10, albeit with the crazy fonts, although the FlightLog did not seem to create after the flight was completed. However, I have installed V1.6. My only question regarding the deletion of the Airbuis Fonts, will this have any effect on the Aerosoft A320 family products? Thanks Ken

best news ive heard, a developer actively supporting windows 10, fantastic and thanks in advance of v1.6.0

Sme problem here, I think Windows 10 might be using a different default font - 9 point Segoe UI?? That´s what shows up for me when you try the Custom sizing option

Hi Travis Correct, there are no SIDS for 18R or 18L as these runways are for landing aircraft only. Departing aircraft would use 14L and 14R. Similarly 32L and 32R are for landing aircraft only and 36L and 36 right for departing, it is known as the North or South configuration. Brgds Ken

I have also noticed this, but only because I was running FSC and FSTramp at the same time. Both of these program continued to show all the traffic but EFB did not. I'm not sure how these two programs connect to FSX. Ken