Welcome to St. Paul Airlines, !
Main Menu

Who's Online
 Welcome Guest
Join Us!


 Login:
User:


Password:


Remember me



Retrieve lost Password
 Online
 Members:0
 Guests:1
 Total:1
 Online Members
No Online members

SPA Recommends
VirtualCol Simulations

Return to Misty Moorings

flyawaysimulation.com

Avsim.com

Flightsim.com

SimRoutes

Flight Simulator Navigation

FS Goof's

Airman's Information Manual

NOAA Metar Access

IFR Refresher Magazine

History of MSFS

Flightaware.com

Fly Better

Aviator90 videos

search pnForum latest posts Note: Registered users can subscribe to notifications about new posts Note: Registered users can subscribe to notifications about new posts

to previous topic Print topic to next topic

Start ::  Pilot's Lobby ::  SPAACARS Updates Issues Suggestions ::  SPA ACARS Version 1.4 Released
Moderated by: Admins

Bottom 

SPA ACARS Version 1.4 Released

jer029 Posted: 22.09.2015, 13:03

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
For those annoying FSX system crashes (or FSUIPC Disconnects) that sometimes happen, this release should mitigate some of those problems by allowing you to resume your flight.

V 1.4
• Added Resume Flight button for restarting your flight after an unexpected Flight Simulator program crash. (Please see the Instruction Manual for step-by-step procedure for having the most success in resuming a flight).

• SPAACARS will recognize most menu actions and should stop FSUIPC communication until completed. This might prevent “FSUIPC Disconnect” messages during temporary interruption of FSUIPC.

As always - to update, just download the SPAACARS.zip file again and copy over the top of your current SPAACARS files. The manual should show 1.4 as will the "About" menu option if the update was successful.

John

jer029

Top  Profile send PM Homepage
 
jer029 Posted: 22.09.2015, 18:56

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
Larry M. discovered an error in the latest release that prevents it from starting.

I discovered that I left my personal cfg file in there. Please re-download the current zip and it should fix things.

If you're more computer-savoy, just go to your SPAACARS folder and find the file called SPAACARS.cfg. Open with text editor and find the only line in there:

inifile=[my settings]

just remove all of my settings so that it looks like:

inifile=

and resave the file. Now when you start SPAACARS, it will prompt you again for your spa.ini file your first use and then it will automatically put your own ini file location in there.


Sorry bout that!

John







edited by: jer029, Sep 22, 2015 - 07:54 PM

jer029

Top  Profile send PM Homepage
 
Anonymous Posted: 23.09.2015, 15:08
Unregistered User 1.4 is unstable. I tested it out anfd when I redo a flight and hit resume it tells me FSUIPC is not loaded. I know it is because all other programs that use FSUIPC are running fine. This includes FS Commander ans my SAITEK panels. We can discuss further on TS tomorrow if you like.
Top 
 
jer029 Posted: 23.09.2015, 18:23

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
Sorry this didn't help you Steve, but I'm not sure I would classify it as "unstable' at this point just because it doesn't work for your sim setup. I can look further into WideFS compatibility, which adds some complexity to things, but I think this might salvage flights for some pilots using a more conventional setup. If there is an alternative that restores a flight after an FSX crash, feel free to use it.

I've been able to resume flights on my test system without problem, and I hope to hear from other pilots too regarding the usefulness of this latest resume function.

As for being "unstable", based on the number of flights being posted using this software, I'm relatively satisfied that it works satisfactorily for most pilots. The resume feature is the only new addition and should not have much affect on the rest of the program that has performed satisfactorily on past releases for most pilots. Further - I believe this option might (in its current form) be of benefit to those pilots in the event of an unexpected FSX crash. I also intend to do further testing while using it myself :-) .

Also - I suspect that the programmers behind those other programs have a lot more programming background than I do.


That doesn't mean I'm not interested in solving whatever issues you're having.

John










edited by: jer029, Sep 23, 2015 - 07:04 PM

jer029

Top  Profile send PM Homepage
 
airhogg Posted: 24.09.2015, 20:48



registered: Feb. 2010
Posts: 68

Status: offline
last visit: 08.12.17
FYI, l just completed 11 leg of the Mississippi River Tour, 15 more to go, haven`t encountered any problems yet. With John`s spaacars program, l should be done within the week. Nice job John.
Top  Profile send PM
 
Anonymous Posted: 24.09.2015, 21:17
Unregistered User Yeah, I've had a lot of those too. Also spent an hour or two trying to untangle a mystery too. I can handle it, no problem, keep on gettin on!
Top 
 
jer029 Posted: 24.09.2015, 21:46

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
...and remember, I promise a full refund of the purchase price of SPAACARS for all dissatisfied customers. :lol:

Might try for a flight tomorrow am. Busy with broken ceiling fan and electricians today.

jer029

Top  Profile send PM Homepage
 
Anonymous Posted: 25.09.2015, 10:17
Unregistered User Not dissatisfied John, just trying to help you get the error handling bugs out The other day, it terminated something in .net and I had to completely reboot my system.
Top 
 
jer029 Posted: 25.09.2015, 15:45

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
That's unfortunate for sure Steve, but again I think it probably has to do with your WideFS and/or your disconnects with that - although likely exacerbated by SPAACARS and your other addons not properly handshaking to catch and deal with these error problems in a more graceful way.

My desire is to inform other pilots reading these posts that the SPAACARS program has proven to be relatively stable as these things go, even though it's been in a constant state of chance since the first release, and they need not fear they are using an "unstable" program, as thus far you've been the only user who has had significant problems.

While the "Resume Flight" option may have caused you trouble, that doesn't mean the program is unstable until we can do further testing. Certainly there's some issues with your setup that are unstable if it's having FSUIPC disconnects that another ACARS program also detected. It would be nice to know what your logs in fsuipc and widefs show.

I've adjusted (once again) SPAACARS and have it out there in the same zip file for download. Not officially announced yet as I wanted to run it a few times on my own game system.

This is V 1.5 and it changes how it handles the resume flight process. I fear it won't solve your problems though at this point. Basically it now continually polls the FSUIPC connection and will not enable the "REsume Flight" button until it has a connection. It will again disable the button if that connection is lost.

Until you check your fsuipc and widefs logs, I'm not sure I can troubleshoot this further. I've researched all that I can based on web posts and FSUIPC SDK documentation.

As for the .net error, it would be great to have as much detail from any error messages received as this might also help identify the problem and a solution so that it might be addressed.

John

jer029

Top  Profile send PM Homepage
 
Anonymous Posted: 25.09.2015, 16:19
Unregistered User John, I really don't want to get into a pissing contest, but SPAACARS is the ONLY program that can't handle FSUIPC interruptions on my computer without bombing out. With that said, it may only be my system, but that is all I can report on. If you don't want feedback, say so. I think your program is good, again just trying to assist.

Now here is the event log of the .net stoppage:

Application: SPAACARS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at System.Runtime.InteropServices.Marshal.CopyToNative(System.Object, Int32, IntPtr, Int32)
at System.Runtime.InteropServices.Marshal.Copy(Int32[], Int32, IntPtr, Int32)
at FSUIPC.FSUIPCConnection.Process(Byte, System.Collections.Generic.IEnumerable`1)
at FSUIPC.FSUIPCConnection.Process(Byte, System.String)
at FSUIPC.PayloadServices.RefreshData()
at SPAACARS.MainWindow.startLog(Boolean)
at SPAACARS.MainWindow.startLogBtn_Click(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
at System.Windows.UIElement.OnMouseLeftButtonUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at SPAACARS.Application.Main()

And the other associated error

Faulting application name: SPAACARS.exe, version: 1.0.0.0, time stamp: 0x5601d81d
Faulting module name: MSVCR120_CLR0400.dll, version: 12.0.51689.34249, time stamp: 0x54d1d585
Exception code: 0xc0000005
Fault offset: 0x0000137a
Faulting process id: 0x4540
Faulting application start time: 0x01d0f62d9e8b2adf
Faulting application path: F:\SPAACARS\SPAACARS.exe
Faulting module path: C:\Windows\system32\MSVCR120_CLR0400.dll
Report Id: 40316db9-6221-11e5-b961-6c71d9755604

they occured at 2:31:05 and 2:31:06




edited by: BBQSteve, Sep 25, 2015 - 04:22 PM
Top 
 
Anonymous Posted: 25.09.2015, 16:25
Unregistered User Additional:

at 2:31:19 just after app crash:

Fault bucket 239253356, type 25
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SPAACARS.exe
P2: 1.0.0.0
P3: 5601d81d
P4: MSVCR120_CLR0400.dll
P5: 12.0.51689.34249
P6: 54d1d585
P7: c0000005
P8: 0000137a
P9:
P10:

Attached files:
C:\Users\Steve Stevens\AppData\Local\Temp\WERC58.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Steve Stevens\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_SPAACARS.exe_3cfeba54acc9a6f3a127b363561f33c91ee7597_01cf3e02

Analysis symbol:
Rechecking for solution: 0
Report Id: 40316db9-6221-11e5-b961-6c71d9755604
Report Status: 0

As you can see all SPAACARS related not FSUIPC. There are no other errors or warnings for this time period.
Top 
 
jer029 Posted: 25.09.2015, 17:18

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
Thanks Steve,

Not sure this ever was a "pissing contest". In fact these last two program versions have been in an effort to identify and mitigate issues you've mentioned regarding FSUIPC disconnect. I had thought you mentioned another ACARS program that also identified a FSUIPC disconnect - perhaps I misunderstood.

Perhaps email or TS exchange would have been a better forum throughout this exchange, including the log sending. Although I appreciate the additional information and your assist in troubleshooting.

While it's true that the SPAACARS is the application affected according to your event log, the first issue according to your log was related to routine process request sent to FSUIPC that was not caught through the normal error handling process I followed based on the SDK:

at FSUIPC.FSUIPCConnection.Process(Byte, System.Collections.Generic.IEnumerable`1)

It's very likely the other programs are not using the .net FSUIPC library I'm using (based on the programming language there are a number of dll's that are used to interact with FSUIPC), and this error appears to be one that was not expected by the developer of that library either as it's not mentioned in the SDK, and probably would have to be handled at the dll level to prevent a .net crash, where I think all I can do is gracefully exit my program by the time it gets back to SPAACARS - and that would be too late if it's already brought .net to its knees.

But then again, I'm not programming expert - so I might be wrong on some of this. All I know is a call to FSUIPCConnection.process should not bring down .net, and that's something I'd probably have to ask Paul Hently about.

Again I might suggest you see what those FSUIPC and WideFS logs are saying too, as it might be necessary for me to have Pete Dowson (or more likely Paul Hently) look at them to see if they can find the problem, if you'd be so kind to send them to me. I'm sure they would need to know what those logs said as well as your event log in order to identify and solve the problem wherever it might be.

John

jer029

Top  Profile send PM Homepage
 
Anonymous Posted: 26.09.2015, 12:33
Unregistered User John, looks like 1.5 has taken care of my crash problem. good job, thanks
Top 
 
jer029 Posted: 26.09.2015, 15:47

jer029

registered: Nov. 2011
Posts: 688

Status: offline
last visit: 18.01.18
Thanks Steve,

Perhaps so, but don't count on that...could be Larry discovered a contributing factor too. I'll put out a 1.6 that should fix pirep upload problem and help prevent other possible error conditions (unless I create a few more errors some place else :roll: ).

John

jer029

Top  Profile send PM Homepage
 
Anonymous Posted: 26.09.2015, 15:55
Unregistered User :-?
Top 
 


Users online:


This list bases on the users active in the last 60 minutes


Powered by pnForum Version 2.6

Copyright © 2000 - 2012 St. Paul Airlines

Web site powered by PostNuke ADODB database library PHP Language