Glenn H
-
Posts
20 -
Joined
-
Last visited
Posts posted by Glenn H
-
-
2 minutes ago, Glenn H said:
2018-09-03 11:42:12.182 Error : Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at System.Windows.Forms.WindowsFormsSynchronizationContext.Send(SendOrPostCallback d, Object state) at a.a.l.x.s.w() at a.a.l.x.s.awx(a A_0) at a.a.l.x.y.adu(a A_0) at a.a.l.d.h.l(w A_0)
I see this in the client support file.
-
5 minutes ago, aivlasoft said:
I guess that it happens if you press the PROC or WX button immediately after the Client seems to be ready. Try to wait some seconds, until you see the active airport indicated on the top of the map.
Waiting doesn't fix anything.
The airport is already loaded anyway. You can wait as long as you want and the error is still there.
-
EDITED by Admin:
unzipped content of the support file (8997 lines) removed.
Sorry, but it was meant to upload the zipped file, not the entire content.
Thanks anyway, I will analyze it now.
and BTW, could you please also provide the support-File from the Server (as mentioned in my previous post)? THANKS.
-
9 minutes ago, aivlasoft said:
Some questions:
- where was your aircraft before the update. Was it on ground, or airborne.
- was there a flight plan active before the update?
- when the Client starts, do you have an active airport indicated on the top of the chart/map before you press the PROC or WX button?
Support files to follow
1) P3D wasn't running when I did the update. I have also tried with P3D running and not running and it makes no difference.
2) Not sure. Dont think so though.
3) Yes
-
It seems you need an active flight plan to stop these errors. Try it. You will have to click on one of the RSB tabs after creating the flight plan but eventually the errors will go away and the wx / dep / arr tabs will work.
Then if you delete the flight plan and restart the client, the errors come back until you create a flight plan again
-
Ok, I think I have figured it out. The only way you can get the errors to go away is to create a flight plan then click on one of the RSB tabs. Keep clicking continue and the errors eventually stop and the wx /arr/ dep tabs work ok.
If you delete the flight plan, restart the client the error returns and then goes away again if you create another flight plan.
Not very handy though
-
So I can get it to work by keeping clicking around and it seems that if you go to an arrival tab at a random 'other' airport then eventually the error goes away and the program works normally.
Only problem is the same thing happens when you exit the program and start it again.
Seems I have to hit a tab button in the 'RSB' section first then the error goes away.
-
Its still doing it to me. And I just reinstalled server and client as a check
-
Yes, same thing
-
Updated this morning, now getting these errors on pressing procedure or weather tabs - all was working fine before the update.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at a.a.l.z.t.iu(Int32 A_0)
at a.a.l.u.al.a.n(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.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.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3163.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
AivlaSoft.Efb.Client
Assembly Version: 2.0.75.0
Win32 Version: 2.0.75.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Efb.Client.exe
----------------------------------------
Castle.Windsor
Assembly Version: 3.3.0.0
Win32 Version: 3.3.0.2412
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/Castle.Windsor.DLL
----------------------------------------
AivlaSoft.Common
Assembly Version: 2.0.12.0
Win32 Version: 2.0.12.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Common.DLL
----------------------------------------
DevExpress.Utils.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.Utils.v16.2.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
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.3151.0 built by: NET472REL1LAST_B
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.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
AivlaSoft.Efb.Common
Assembly Version: 2.0.30.0
Win32 Version: 2.0.30.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Efb.Common.DLL
----------------------------------------
AivlaSoft.Efb.Skins
Assembly Version: 15.1.5.0
Win32 Version:
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Efb.Skins.DLL
----------------------------------------
AivlaSoft.Database.Common
Assembly Version: 2.0.6.0
Win32 Version: 2.0.6.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Database.Common.DLL
----------------------------------------
AivlaSoft.Efb.Database
Assembly Version: 2.0.19.0
Win32 Version: 2.0.19.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Efb.Database.DLL
----------------------------------------
DevExpress.XtraEditors.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.XtraEditors.v16.2.DLL
----------------------------------------
Castle.Core
Assembly Version: 3.3.0.0
Win32 Version: 3.3.3.2300
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/Castle.Core.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3160.0 built by: NET472REL1LAST_C
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.3056.0 built by: NET472REL1
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.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
DevExpress.Data.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.Data.v16.2.DLL
----------------------------------------
DevExpress.XtraGrid.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.XtraGrid.v16.2.DLL
----------------------------------------
System.ComponentModel.DataAnnotations
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3160.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3160.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
DevExpress.XtraBars.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.XtraBars.v16.2.DLL
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
DevExpress.XtraTreeList.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.XtraTreeList.v16.2.DLL
----------------------------------------
AivlaSoft.Efb.Export.Interface
Assembly Version: 2.0.2.0
Win32 Version: 2.0.2.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/AivlaSoft.Efb.Export.Interface.DLL
----------------------------------------
DevExpress.XtraRichEdit.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.XtraRichEdit.v16.2.DLL
----------------------------------------
DevExpress.RichEdit.v16.2.Core
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.RichEdit.v16.2.Core.DLL
----------------------------------------
DevExpress.Office.v16.2.Core
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.Office.v16.2.Core.DLL
----------------------------------------
DevExpress.XtraPdfViewer.v16.2
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.XtraPdfViewer.v16.2.DLL
----------------------------------------
DevExpress.Pdf.v16.2.Core
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.Pdf.v16.2.Core.DLL
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3160.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
DevExpress.Pdf.v16.2.Drawing
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.Pdf.v16.2.Drawing.DLL
----------------------------------------
DevExpress.Printing.v16.2.Core
Assembly Version: 16.2.3.0
Win32 Version: 16.2.3.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/DevExpress.Printing.v16.2.Core.DLL
----------------------------------------
AivlaSoft.Efb.Export.Efb
Assembly Version: 2.0.1.0
Win32 Version: 2.0.1.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/FlightplanExport/AivlaSoft.Efb.Export.Efb.dll
----------------------------------------
AivlaSoft.Efb.Export.Fsx
Assembly Version: 2.0.1.0
Win32 Version: 2.0.1.0
CodeBase: file:///C:/Program%20Files/AivlaSoft/EFB2/Client/FlightplanExport/AivlaSoft.Efb.Export.Fsx.dll
----------------------------------------
UIAutomationClient
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3160.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationClient/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationClient.dll
----------------------------------------
UIAutomationTypes
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3160.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll
----------------------------------------
System.Data.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.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. -
2 hours ago, lonewulf47 said:
What is so odd about that? Each A/C type has it's limits. So at least this part is of course Aircraft Specific. Now whether you want to land with some tailwind rather than flying an approach to the opposite RWY is to some extent your decision. I could give you example of aiports from my real life experience where you would land with up to max. Tailwind Component before they are changing the operational RWY... This said, it is up to you to set the limits to your requirements, including the warning level. Green simply means that the RWY is within your A/Cs limits, with a warning level set at your discretion. This is even in real life a fully legal aspect, believe me.
I fully understand your argument for the RWY selection but I can assure you that this is only valid for Simulation and even there only if your don't fly online. The rest is taken a out of your decision process as a pilot to some extent. This applies to the last part of your argument - > if available. You can of course always ask for the RWY with headwind, The only question is whether you are give a clearance to that RWY within due time... see above, and I'm not talking about some wish-wash airports of the coutryside...
An aircraft can always be operated within its limits. This also applies to the tailwind component. Whether you want to set the warning level to a lower percentage is purely your decision. The figures used in the default profiles are - as the wording says - default figures and in no way connected to the Holy Grail ? They are simply based on Real Wold Experience.
I get all that. I have over 200 hours myself in real world (enough to be dangerous I guess) but I think the misunderstanding comes from the original version of EFB where the procedures would always give you a statement something like "wind favours runway(s) xx".
From the topic on Avsim my understanding was that this had been replaced by the 'green' highlight. Clearly this is not the case as the highlighting only shows if the runway and wind conditions are within limits of the aircraft. It's not been designed to do what I was assuming it was doing based on that toipc over there.
-
Ok, so the coloring is aircraft profile specific not what actually makes sense in terms of wind speed and direction?
I find this choice a little odd to be quite honest. Regardless of an aircraft's ability to land with a tail wind component, the preferred runway would always be one with a headwind component if it is available.
I guess modifying the parameters as you suggested is always an option here.
-
So I have two options for weather generation in EFB v2.
I can use either Opus FSI (my normal method) or I can use NOAA (real world)
No matter which option I choose to get the weather data, I seem to get all runways highlighted in green for take off and departure even though in this case shown here with a screenshot at EGCC and a valid current Metar the wind clearly favours runways 23R and 23L.
Any idea why this is? Am I missing something. As far as I can tell from the manual, two of the runways should be 'blue' (within limits of aircraft) and two should be 'green' (optimal conditions)
According to Avsim users I should be seeing things differently here. Hope this screenshot isn't too vague..........
EDIT - Have added EHAM too - All runways shown as 'Green'
-
Well, I had the demo of V1 a few years ago but decided against purchasing.
Went ahead and purchased V2 straight away this time and after a day of using it I can only say I'm blown away with what this package does. It really is quite fabulous. Well done!
-
Ah ok.
So if im reading the manual correctly, the only way to have the RVR in feet instead would be to manually edit the text files contained in the 'minima' data path?
Suddenly this UOM issue doesn't bother me so much......:)))
Glenn
-
Hi, even with RVR set to feet in the units settings, the display still shows RVR values in approach charts as meters / km.
Am i missing something here?
-
Hi,
Thanks for the info. Just set it up on main pc using secondary monitor and it works well with only on average 0.8% CPU usage. Occasionally it jumps to 1.6% but seems insignificant. Also have set it to run on last two cores only so should be good.
Glenn
-
Hi all,
Just got V2 and was wondering about the benefits of running the client on a networked laptop?
I already have a second display screen on my main PC and was just going to run the server and client on the main system. Is there a performance gain to be seen if the client runs on a second networked machine?
Thanks,
Glenn
-
On 7/1/2018 at 8:29 AM, ArzaanK said:
I'm pretty sure this is due to exchange fees. I have seen the same issue with eSellerate. I live in Canada, and CHF 59.90 corresponds to about about CAD 80.00. However, Cleverbridge was trying to charge me CAD 91.00. I chose to purchase in CHF and have my credit card to the conversion (usually charges only a 2.5% conversion fee, much less than Cleverbridge).
Even when I purchase scenery from FSDreamteam/FlightBeam and the FSLabs using esellerate, I get charged hefty conversion fees. In the mean time, I suggest you contact your credit card
company and find out what your foreign exchange fees are (they are usually reasonable).
This is what I did too. Cleverbridge conversion rate for CAD$ was disgraceful.
Update Build #75 - Now getting errors
in EFB v2 - Support forum
Posted
Thanks for the fast response! Much appreciated.