Page 4 of 5

Re: Report Bug and problems here

Posted: Sat Jul 06, 2019 4:34 pm
by victor.papa
Blue1308 wrote:
Sat Jul 06, 2019 2:05 am
Hi,

I did three flights recently with FSTrackers all was working well but I notice these three flights were not in "Historic flights" of FSTrackers.
Could you tell me why?

Regards,

Christian
Dear Christian,
Thank you for your report. Yes you are right. Your flights haven't been archived correctly by our automated system. I fixed those problems for you and now you can see them in historic flights.

Re: Report Bug and problems here

Posted: Tue Jul 16, 2019 5:37 pm
by florida_coast
I encounter the following problem:
- I plan a flight with Simbrief, download it to my P3DV4 folder and want to use it via FSTrackers, then I receive the following failure message:
************** Ausnahmetext **************
System.IndexOutOfRangeException: Der Index war außerhalb des Arraybereichs.
bei FSTrackers.FormFSTrackers.btnInputFlightPlan_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3815.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
FSTrackers
Assembly-Version: 2.8.0.0.
Win32-Version: 2.8.0.0.
CodeBase: file:///C:/Users/janmo/Desktop/FSTrackers/FSTrackers.exe.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3815.0 built by: NET48REL1LAST_C.
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.8.3801.0 built by: NET48REL1LAST_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.8.3752.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.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.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3752.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3815.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3752.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3752.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
msvcm80
Assembly-Version: 8.0.50727.9659.
Win32-Version: 8.00.50727.9659.
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9659_none_d08cfd96442b25cc/msvcm80.dll.
----------------------------------------
Accessibility
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3752.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3752.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

When I plan a flight within P3DV4, it works out normal.
I use Windows 10 Home 64-bit

Thx for the help

Re: Report Bug and problems here

Posted: Wed Jul 17, 2019 4:28 pm
by victor.papa
florida_coast wrote:
Tue Jul 16, 2019 5:37 pm
I encounter the following problem:
- I plan a flight with Simbrief, download it to my P3DV4 folder and want to use it via FSTrackers, then I receive the following failure message:

When I plan a flight within P3DV4, it works out normal.
I use Windows 10 Home 64-bit

Thx for the help
Hi,
Please send an email to support@simelite.com and attach your flight plan. We will check what the problem is.

Re: Report Bug and problems here

Posted: Wed Jul 17, 2019 11:19 pm
by victor.papa
florida_coast wrote:
Tue Jul 16, 2019 5:37 pm
I encounter the following problem:
- I plan a flight with Simbrief, download it to my P3DV4 folder and want to use it via FSTrackers, then I receive the following failure message:

When I plan a flight within P3DV4, it works out normal.
I use Windows 10 Home 64-bit

Thx for the help
We received your flight plan and the problem has been fixed. That error doesn't have anything to do with Simbrief. Only number of Waypoints in your flight plan caused that error. Your flight plan has 136 Waypoints but FSTrackers designed for 100! We increased number of Waypoints and it means you can load that flight plan into your FSTrackers without a problem.
(We already sent you an email with instructions)

Re: Report Bug and problems here

Posted: Sun Jul 21, 2019 10:10 am
by florida_coast
Thanks for your quick help.

Another question that has risen up:
It does not show the estimated flight time, nor the Time from the departure and the local time at origin, Airplane and Destination. Did I miss something in the installation process?
Thanks again for the help

Re: Report Bug and problems here

Posted: Sun Jul 21, 2019 3:47 pm
by victor.papa
florida_coast wrote:
Sun Jul 21, 2019 10:10 am
Thanks for your quick help.

Another question that has risen up:
It does not show the estimated flight time, nor the Time from the departure and the local time at origin, Airplane and Destination. Did I miss something in the installation process?
Thanks again for the help
Hi,
Please note that FSTrackers only can calculate departure and arrival time, flight duration, time of arrival ... if you start your tracking before take off and end it after landing at your destination airport. Those information will be available when you take off and reach about 500 feet above the ground. if for any reason you start your tracking after take off, FSTracker won't be able to calculate those information.

If you start your tracking before take off and you still don't have those information there could be another possibility. If FSTrackers can't find your departure or arrival airport information (ICAO code from your flight plan) in our database then that kind of problem will be occur.

Please let me know what exactly happened in your side and I will help you fix the problem. ;)

Re: Report Bug and problems here

Posted: Sat Aug 10, 2019 2:30 pm
by Blue1308
Hi,

I've noticed, my last flight "landed" was not shown when I arrived at my destination (flight was LSGG-EIDW).

I'll try one more to see if I have the same problem this time.

Regards,

Christian

Re: Report Bug and problems here

Posted: Sat Aug 10, 2019 7:40 pm
by Blue1308
Hi

Ok my second flight was correct..I don't know what happened in my first flight.

Regards,

Christian

Re: Report Bug and problems here

Posted: Sat Aug 10, 2019 11:15 pm
by victor.papa
Blue1308 wrote:
Sat Aug 10, 2019 7:40 pm
Hi

Ok my second flight was correct..I don't know what happened in my first flight.

Regards,

Christian
Thanks for letting us know the result!

Re: Report Bug and problems here

Posted: Sat Aug 17, 2019 1:14 pm
by Blue1308
Hi,

Just report my last flight, landed in EGLL but destination still show me at 41 miles from EGLL.

Regards,

Christian