Report Bug and problems here

Everything related to SimElite Solutions FSTrackers
Message
Author
User avatar
victor.papa
Moderator
Moderator
Posts: 234
Joined: Thu Jul 20, 2017 12:00 am

Re: Report Bug and problems here

#31 Post by victor.papa » Sat Jul 06, 2019 4:34 pm

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.

florida_coast
newbie
Posts: 2
Joined: Tue Apr 02, 2019 6:40 pm

Re: Report Bug and problems here

#32 Post by florida_coast » 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:
************** 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

User avatar
victor.papa
Moderator
Moderator
Posts: 234
Joined: Thu Jul 20, 2017 12:00 am

Re: Report Bug and problems here

#33 Post by victor.papa » Wed Jul 17, 2019 4:28 pm

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.

User avatar
victor.papa
Moderator
Moderator
Posts: 234
Joined: Thu Jul 20, 2017 12:00 am

Re: Report Bug and problems here

#34 Post by victor.papa » Wed Jul 17, 2019 11:19 pm

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)

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest