RayProudfoot

Thanks Urs, great service and much appreciated. I'll report back later once it's installed.

Thanks Urs.

Hi Urs, Do you have a date in mind when you will release an update to cope with closed runways?

Thanks Urs, I remember it from years ago. Nice simple solution. I'll write to T2G and let him know how we've solved it. Other software might be affected.

Hi Urs, I had another look at the AFCAD this morning and have found (I think) the reason why those runways are not included by P3D in the drop-down. If you select the Pattern option for them you'll see both ends of the runway are closed for landing and take-off. That, I believe, makes them invisible to P3D. Can you include that check when building your database and exclude any that meet that criteria?

I wrote to support@taxi2gate.com and received this reply regarding the duplicate runways... Hi, its normal, we use like other developers double runways to use in the bridges so the ai traffic can cross over them. It appears we're stuck with them. However, they don't appear in the P3D runway selection drop-down so they must have properties that make them invisible. Maybe someone can spot what the properties are so Urs can exclude them from his scan. AFCAD attached. LFPG_AF.bgl

EGCC problem resolved. Thanks Urs.

I can't see any posts in the T2G forum about this problem so I've posted today. Hopefully it can be fixed. http://forum.iflysimx.com/topic/1533-double-runways-at-lfpg/ Urs, can you filter out runways without a number in the name? These runways are alpha characters only.

Hi Urs, Slightly different problem with UK2000 EGCC. The Surface type is shown as 'Unknown' but the AFCAD definitely has it as Asphalt. I'm running the 1.6.12 update.

Bob / Urs, I have P3D v3.4 but this version uses the same structure as v4. I have Lordy's utility (v0.99) and have most of the FlightBeam and FSDT scenery packages. I have just run the utility to generate a scenery.cfg from both the existing scenery.cfg and the two add-ons.cfg. The process generated a combined scenery.cfg but unfortunately the FSDT and FlightBeam entries also include the word scenery which makes the path invalid. You only have to point to the parent folder, not the scenery sub-folder. I edited and saved scenery.cfg to remove \scenery from the relevant entries, saved it and then ran the database builder in EFB. That completed without encountering any problems for the FSDT and FB airports and positioning my aircraft at several gates showed the EFB map to be perfectly aligned. I then completed the process by recovering the original scenery.cfg. I'll ask Lordy about that path and see what he says.

Hi Urs, Now that I know EFB cannot read a flight plan that contains comments I will make sure none do in future. You appear to have read my comments as an accusation of bad programming. I meant nothing of the sort. As a former programmer myself I know it can be difficult to capture all errors and output a meaningful message. I'm now aware of the situation so this problem should not reoccur.

Hi Urs, The original was created by PFPX but as I stated in my second post I loaded it into Little Navmap - a moving map utility - and because I was experimenting learning the program made a change which resulted in the pln being saved with a comment section. No change was made to the actual waypoints or other key data. So why did EFB reject this when the comment section has been created in line with XML standards? It seems you are unable to capture these errors before .NET so cannot output a more meaningful message. Pity. But as I said before the comment was to an agreed standard so why is .NET not ignoring it?

Hi Urs, Flight plan attached. This includes the comment added by the 3rd party program. Given that these error messages are unfathomable by anyone other than the programmer is it possible for you to output more meaningful ones? In this case it was because the flight plan could not be read. I was uninstalling and reinstalling both elements of EFB thinking something was corrupted. All completely unnecessary as it turned out, ENGMEGLL01.pln

After discussion with the author of Little Navmap he points to this article about adding comments to an XML file. It should not cause any program reading it to fail. Hopefully a fix to EFB can be provided.

I have discovered the cause of this problem. I installed a freeware moving map utility yesterday. I loaded this plan and it seems it has added a comment section near the top of the plan. This was sufficient to cause EFB problems. But wouldn't a more meaningful error message have helped? Like "unknown data in flight plan". This is what EFB objected to. The offending text in red. Why can't EFB just ignore a comment? <?xml version="1.0"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <!-- LNMDATA _lnm=Created by Little Navmap Version 1.4.3 (revision 7359ce8) on 05 July 2017 11:44:02| speed=100.0000 --> <FlightPlan.FlightPlan> <Title>ENGM to EGLL</Title>

Up to a couple of days ago EFB was just fine. Trying to load a flight plan today results in the error in the title of this topic and the following details:- Am I really meant to understand what all this means? Searching this forum for the same message results in no solutions being offered. This is a standard P3D flight plan created by PFPX. Please help. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at AivlaSoft.FlightplanHandlers.P3D.P3DHandler.ReadP3DTypeFlightPlan(String filenameSource) at AivlaSoft.FlightplanHandlers.P3D.P3DHandler.Read(String filenameSource) at yz.a(IFlightplanHandler A_0) at yz.w() at yz.p(Object A_0, EventArgs A_1) at System.Windows.Forms.Control.OnClick(EventArgs e) at DevExpress.XtraEditors.BaseButton.OnClick(EventArgs e) at DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m) at DevExpress.XtraEditors.BaseControl.WndProc(Message& msg) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.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.7.2053.0 built by: NET47REL1 CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- AivlaSoft.Efb.DisplayUnit Assembly Version: 1.6.8.33245 Win32 Version: 1.6.8.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/AivlaSoft.Efb.DisplayUnit.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 built by: NET47REL1 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.7.2053.0 built by: NET47REL1 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.7.2053.0 built by: NET47REL1 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:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/Castle.Windsor.DLL ---------------------------------------- DevExpress.BonusSkins.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.BonusSkins.v15.1.DLL ---------------------------------------- DevExpress.Utils.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Utils.v15.1.DLL ---------------------------------------- AivlaSoft.Efb.Common Assembly Version: 1.6.7.33244 Win32 Version: 1.6.7.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/AivlaSoft.Efb.Common.DLL ---------------------------------------- Castle.Core Assembly Version: 3.3.0.0 Win32 Version: 3.3.3.2300 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/Castle.Core.DLL ---------------------------------------- DevExpress.Data.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/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:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraEditors.v15.1.DLL ---------------------------------------- AivlaSoft.Efb.WeatherServices Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/AivlaSoft.Efb.WeatherServices.DLL ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 built by: NET47REL1 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.7.2053.0 built by: NET47REL1 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.7.2053.0 built by: NET47REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 built by: NET47REL1 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:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraGrid.v15.1.DLL ---------------------------------------- System.ComponentModel.DataAnnotations Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll ---------------------------------------- AivlaSoft.Efb.IFlightplanHandler Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/AivlaSoft.Efb.IFlightplanHandler.DLL ---------------------------------------- AivlaSoft.FlightPlanHandlers.A320Series Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.A320Series.dll ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.7.2053.0 built by: NET47REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Web Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 built by: NET47REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.AAXE Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.AAXE.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.FSC Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.FSC.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.iFly-747_V2 Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.iFly-747_V2.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.iFly Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.iFly.dll ---------------------------------------- AivlaSoft.FlightplanHandlers.iFms Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightplanHandlers.iFms.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.ISG Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.ISG.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.KML Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.KML.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.LevelD Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.LevelD.dll ---------------------------------------- AivlaSoft.FlightplanHandlers.MsFs Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightplanHandlers.MsFs.dll ---------------------------------------- AivlaSoft.FlightplanHandlers.P3D Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightplanHandlers.P3D.dll ---------------------------------------- AivlaSoft.FlightPlanHandlers.PmdgRte Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightPlanHandlers.PmdgRte.dll ---------------------------------------- AivlaSoft.FlightplanHandlers.ProSim737 Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightplanHandlers.ProSim737.dll ---------------------------------------- AivlaSoft.FlightplanHandlers.SimAvionics Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightplanHandlers.SimAvionics.dll ---------------------------------------- AivlaSoft.FlightplanHandlers.Squawkbox2 Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/plugins/AivlaSoft.FlightplanHandlers.Squawkbox2.dll ---------------------------------------- DevExpress.XtraRichEdit.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraRichEdit.v15.1.DLL ---------------------------------------- DevExpress.RichEdit.v15.1.Core Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.RichEdit.v15.1.Core.DLL ---------------------------------------- DevExpress.Office.v15.1.Core Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Office.v15.1.Core.DLL ---------------------------------------- DevExpress.XtraPdfViewer.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraPdfViewer.v15.1.DLL ---------------------------------------- DevExpress.Pdf.v15.1.Core Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Pdf.v15.1.Core.DLL ---------------------------------------- DevExpress.XtraBars.v15.1 Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraBars.v15.1.DLL ---------------------------------------- DevExpress.Pdf.v15.1.Drawing Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Pdf.v15.1.Drawing.DLL ---------------------------------------- DevExpress.Printing.v15.1.Core Assembly Version: 15.1.5.0 Win32 Version: 15.1.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Printing.v15.1.Core.DLL ---------------------------------------- WindowsBase Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 built by: NET47REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll ---------------------------------------- UIAutomationClient Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 built by: NET47REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationClient/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationClient.dll ---------------------------------------- System.Data.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.7.2053.0 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Data.Linq.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.

I've discovered the problem. I was editing the runways.txt file in the wrong folder. I thought the one in D:\P3D\Aivlasoft\NavData was the correct one. Seems not. It reads the one in Users\MyName\Documents\Aivlasoft\EFB\UserData. Never too old to make a mistake or learn from it!

I cannot resolve the problem with EFB and runways at GCTS in P3D v3.4. I have the default scenery. The runway numbers in P3D are 08/26. In the file WPNAVAPT.txt in D:\P3D\Aivlasoft\NavData the runways are shown as 07/25. So to correct this I have added two entries in Runways.txt in the above folder as follows:- GCTS 07 08 GCTS 25 26 I have saved the file, restarted EFB and in the Data Viewer I have reset the airport data cache. But when I start EFB and enter GCTS in the Display Unit I still get the runway assignment warning saying runway 07 and 25 could not be assigned. What am I doing wrong? All this is with AIRAC Data Cycle 1706.

I'm so pleased I found this question. If I load ConcordeX in P3D the default zoom is 0.3 (even though the value is 0.7 in the camera.cfg) and that is perfect for the Captain's seat view. But when I started SimpleCam the default zoom became 0.7 and I was having to position the Captain's view around 4 feet behind his seat. That meant I then needed to zoom in to get the instruments into view but doing that killed the wide angle view including the views out of the left windows. I changed the default zoom to 0.3 in camera.cfg for the virtual cockpit and have been able to setup perfect views now for the Captain's seat. This is especially important for Concorde as the nose blocks the view of the runway but once it's down the view is perfect.

I had the same problem with the default port causing a problem when I launched P3D v3.4. I increased the port number by 1 and that solved the problem. Windows can show you what ports are in use making it easier to find a free one... Right-click the Taskbar and choose Start Task Manager Switch to the Performance Tab and at the bottom choose Resource Monitor... Choose the Network tab and click on the arrow against Listening Ports to open the list. The Port Number is listed for each process and at the right shows if it's Allowed or Not Allowed. If the number you want to use is listed just check if it's Allowed.

I've circumvented the problem. Rather than have SimStartNG start EFB I'm now using FSUIPC. When I close P3D the EFB Data Provider display stays visible for several seconds and then closes elegantly with no "program has stopped working" message.

Hi Urs, I'm attaching a log file showing my most recent activity. EFB Data Provider is started by SimStarterNG and should be closed by that program once P3D has closed. However, what is happening is as soon as I close P3D the "program has stopped working" popup appears. Given that EFB works fine during a flight I fail to understand why it ceases working as soon as P3D is closed. If I require a separate SimConnect for P3D / EFB please advise which it is and where I can find it. Ray_EFB_Log.txt

Hi Urs, No I didn't purely because everything seemed to work except when closing P3D. I shall investigate further. Pity P3D can't install what it needs. LATER: Urs, why would P3D and EFB work fine with existing SimConnect versions and only have a problem when P3D is closed? Doesn't make sense. If I didn't have the right version EFB wouldn't connect with P3D.

I've recently switched from FSX to P3D v3.4. I reinstalled EFB (Data Provider on P3D computer and Display Unit on a separate one). I haven't uninstalled FSX and my SimConnect settings are unchanged. Every time I close P3D Windows 7 displays a message that EFB has stopped working. I open Event Viewer and this is the message. Any idea why it's happening and how I can stop it. In all other respects EFB works fine during a flight. Faulting application name: AivlaSoft.Efb.DataProvider.exe, version: 1.6.8.0, time stamp: 0x56c5ffaa Faulting module name: SimConnect.dll, version: 10.0.61637.0, time stamp: 0x46fad5b6 Exception code: 0xc0000005 Fault offset: 0x00001f8b Faulting process id: 0x1728 Faulting application start time: 0x01d2c7fffdc0b5b3 Faulting application path: C:\Program Files (x86)\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll Report Id: 8a8e8acb-33f8-11e7-8fd3-94de80a6c959

Hi Urs,I had a different folder set for my P3D files. Once I corrected it to the same as yours (with a different username of course) the Garmin option works fine. Thanks for your help.