rangerobert 11 Posted April 18, 2015 Share Posted April 18, 2015 Hello everyone, probably already said in different forms on other posts, but without solution: FSX properly working with other planes. No crash on exit, or CTD of any type. If I use A320/A321, everything works for unlimited time. Only after that this plane has been loaded, when I close the simulator - by END OF FLIGHT - by direct EXIT on "x" at the right superior corner - or even also trying to LOAD A DIFFERENT PLANE on all these different situations I've got CRASH ON EXIT (" ... FSX stopped to work ... Windows is trying to find a solution ...") with the very annoying secondary trouble that all the Controls setup get back to default, by loosing ALL MY JOYSTICK, PEDALS, QUADRANTS, etc etc CONFIGURATION. I must restore the situation by a backup standard.xml file, that I wisely learnt to save in the years just in case. I'm talking about: FSX Steam Edition - v. 10.0.62613.0, AS A320/321 1.30 plus hotfix 1.30e Windows 7 64bit Pro / i7 3.06GHz 12 GB RAM with MS Visual C++ 2005, 2008, 2010, 2012, 2013 properly updated and SimConnect.msi manually run on all three SDK dedicated folders. Thx a lot for your help, roberto Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted April 18, 2015 Aerosoft Share Posted April 18, 2015 If you exit FSX one time with another aircraft the settings should be saved. If not contact Dovetails as it could be a bug in the beta. Link to comment Share on other sites More sharing options...
rangerobert 11 Posted April 18, 2015 Author Share Posted April 18, 2015 Sure, but when I'll use Aerosoft Airbus, I'll have controls settings screwed up again. Anyway, I'll try with Dovetails, ... hoping they won't reply is a bug in the 1.30a AS320/321 hotfix ... Best regards roberto Link to comment Share on other sites More sharing options...
airbusliker 1 Posted April 19, 2015 Share Posted April 19, 2015 Good day! I also Get the error since SP3. Aerosoft, please fix that and dont try to send the error to other Programms. I am shure it comes from your side, sorry. Marius Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 19, 2015 Deputy Sheriffs Share Posted April 19, 2015 Good day! I also Get the error since SP3. Aerosoft, please fix that and dont try to send the error to other Programms. I am shure it comes from your side, sorry. Marius Are you on the same system as Roberto? Please give your full specs. Link to comment Share on other sites More sharing options...
airbusliker 1 Posted April 19, 2015 Share Posted April 19, 2015 I'm not on the Same System. amd in my pcC , 8gb RAM. Have fsx with acceleration. My settings are also not saved when fsx crashes. Link to comment Share on other sites More sharing options...
airbusliker 1 Posted April 19, 2015 Share Posted April 19, 2015 In my so called : ereignisanzeige I see that Fmgs.dll is Causing the error. Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 19, 2015 Deputy Sheriffs Share Posted April 19, 2015 Can you post the exact message of the event log (Ereignisanzeige), please? Link to comment Share on other sites More sharing options...
airbusliker 1 Posted April 19, 2015 Share Posted April 19, 2015 I Also get 2 faults in less than 3 second. The first protocoll says at 08:26:53UTC Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14 Name des fehlerhaften Moduls: FMGS.DLL, Version: 1.2.7.82, Zeitstempel: 0x552db3f3 Ausnahmecode: 0xc0000005 Fehleroffset: 0x000f138e ID des fehlerhaften Prozesses: 0x1810 Startzeit der fehlerhaften Anwendung: 0x01d079a0db8be92f Pfad der fehlerhaften Anwendung: D:\Programme\Flight Simulator X\fsx.exe Pfad des fehlerhaften Moduls: D:\Programme\Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\DLLs\FMGS.DLL Berichtskennung: aa7a705b-e5a4-11e4-924a-e03f49e90cf5 The second one 08:26:56UTC Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14 Name des fehlerhaften Moduls: FMGS.DLL, Version: 1.2.7.82, Zeitstempel: 0x552db3f3 Ausnahmecode: 0xc0000005 Fehleroffset: 0x000ee937 ID des fehlerhaften Prozesses: 0x1810 Startzeit der fehlerhaften Anwendung: 0x01d079a0db8be92f Pfad der fehlerhaften Anwendung: D:\Programme\Flight Simulator X\fsx.exe Pfad des fehlerhaften Moduls: D:\Programme\Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\DLLs\FMGS.DLL Link to comment Share on other sites More sharing options...
GermanyGreece93 3 Posted April 19, 2015 Share Posted April 19, 2015 Same here ************** Exception Text ************** System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type) at .?.(? timeRecvr, DateTime FSXStarted, DateTime FlightStarted) at .?.?() at ..?(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- UT2Services Assembly Version: 2.1.0.0 Win32 Version: 2.1.0.0 CodeBase: file:///F:/Flugsimulator/Flight%20One%20Software/Ultimate%20Traffic%202/UT2Services.exe ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.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 ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.6195 Win32 Version: 8.00.50727.6195 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/msvcm80.dll ---------------------------------------- System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Transactions Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- System.Management Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- System.ServiceModel Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5463 (Win7SP1GDR.030729-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceModel/3.0.0.0__b77a5c561934e089/System.ServiceModel.dll ---------------------------------------- SMDiagnostics Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5463 (Win7SP1GDR.030729-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/SMDiagnostics/3.0.0.0__b77a5c561934e089/SMDiagnostics.dll ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5463 (Win7SP1GDR.030729-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Serialization/3.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- System.IdentityModel Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5463 (Win7SP1GDR.030729-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.IdentityModel/3.0.0.0__b77a5c561934e089/System.IdentityModel.dll ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.5420 built by: Win7SP1 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.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. Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 19, 2015 Deputy Sheriffs Share Posted April 19, 2015 Same here ************** Exception Text ************** System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type) at .?.(? timeRecvr, DateTime FSXStarted, DateTime FlightStarted) at .?.?() at ..?(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ....... Nowhere in your report is a file mentioned related to the Airbus. Only Windows and FSX core files. Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 19, 2015 Deputy Sheriffs Share Posted April 19, 2015 Aerosoft, please fix that and dont try to send the error to other Programms. I am shure it comes from your side, sorry. If so, answer the following question: - Why do I not get this error on my system: FSC with AccPack, Win7 64bit and tons of addons? - Why do only get a few people out of thousands get this error? A developer can only fix a bug that is recreatable under standardized conditions. In such a very specific case in nearly all cases at the end it turned out that on the effected systems something was not as it should be, like: - Windows not really up to date - library files not up to date - some tweaks and others. We are really trying to help those people, but it is impossible to debug every single system. Link to comment Share on other sites More sharing options...
airbusliker 1 Posted April 19, 2015 Share Posted April 19, 2015 Why worked everything well with 1.21?? Link to comment Share on other sites More sharing options...
GermanyGreece93 3 Posted April 19, 2015 Share Posted April 19, 2015 okay, but the error appears since the hotfixes a and b Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 19, 2015 Deputy Sheriffs Share Posted April 19, 2015 Why worked everything well with 1.21?? That's what I'm trying to explain. An example: If you update a program file and this new file calls a function which is not properly supported by old/outdated/damaged system libraries you might experience a crash. okay, but the error appears since the hotfixes a and b Not for me. So what problem do I have? Link to comment Share on other sites More sharing options...
airbusliker 1 Posted April 19, 2015 Share Posted April 19, 2015 Would it be possible to write, which Drivers Your Product needs in which Version? I know it´s a lot of work, but I think it would help many users. Greetings Link to comment Share on other sites More sharing options...
rangerobert 11 Posted April 22, 2015 Author Share Posted April 22, 2015 ... probably already said in different forms on other posts, but without solution: FSX properly working with other planes. No crash on exit, or CTD of any type. If I use A320/A321, everything works for unlimited time. Only after this plane has been loaded, when I leave - by END OF FLIGHT - by direct EXIT on "x" at the right superior corner - or even also trying to LOAD A DIFFERENT PLANE on all these different situations I've got CRASH ON EXIT (" ... FSX stopped to work ... Windows is trying to find a solution ...") with the very ennoying secondary trouble that all the Controls setup get back to default, by loosing ALL MY JOYSTICK, PEDALS, QUADRANTS, etc etc CONFIGURATION ... FSX Steam Edition - Open Beta version of 2/3 days ago, AS A320/321 1.30 plus hotfix 1.30a Windows 7 64bit Pro / i7 3.06GHz 12 GB RAM [EDIT now Hotfix 1.30e] Hello everyone. I solved my problem. It is great to fly this masterpiece of an add-on airplane, especially considering the incredible quality-to-price ratio, but even more it is a pleasure to have such a support forum. And for both things I wish to thank this committed development team. It is almost impossible not to find an already available solution to ANY trouble. The only issue is ... to know how to find it, lol. In any case, I got it. All my CTDs encountered after using the bus just disappeared by unticking "Webserver" on MCDU section of the Configurator utility. Exactly as specified on this posthttp://forum.aerosoft.com/index.php?/topic/93757-strange-fmgs-error/?hl=webserver#entry668763 These crash-on-exit were especially annoying, also due to absence of any walkaround, included the attempt of loading another airplane (as suggested), and for the randomly occurring reset-to-default of the whole controls configuration for throttle, joystick, etc Hope that could be helpful to someone, folks Cheers, roberto Link to comment Share on other sites More sharing options...
welsol 3 Posted April 28, 2015 Share Posted April 28, 2015 Solved also .... thank you Roberto Link to comment Share on other sites More sharing options...
gkertesz 1 Posted May 13, 2015 Share Posted May 13, 2015 So that means if I do not want to have crashes on exiting, (and endanger in-flight FSX operation, because I suppose this kind of CTD is responsible for some others), I should not use the webserver, which was one of the most excellent feature of this aircraft to have the MCDU on a tablet, and which gets us closer to reality with a big step? Question mark. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted May 13, 2015 Aerosoft Share Posted May 13, 2015 The crash on exit should have no impact on anything running in FS as it happens when the memory used by FS is being released to the OS. The FS process is at that moment already stopped. Link to comment Share on other sites More sharing options...
KAPTEJNLN 237 Posted May 13, 2015 Share Posted May 13, 2015 well I just tested this problem and can confim the CTD by the webserver turned on. As roberto say he tryeid and I just tryeid get my controls reset aswell, quite annoyeing.But any way A crash of something is not good, as it also crates other files generated when the sim crash. like a text file of FSX.CFG file and other processes like weather program files, notclosed corectly, as the simulator dont end all the processes caused due to the fact the sim crashed before it compleated all of it. So yes a crash is always 1 to much, especialy when we knowhow many bug combinations we might get, as then we might start having problem by a new add-on and no one knows why and could be lead back to something.. I know ASN create a file: exe.xmlthat file had caused low prerformance and by delting it the sim run much better and ASN build a new one.. all those small things gets hard to keep track of by it self, but when things start to fail along the road it dosent make life easyer for costumers or support..you can even get the sim Crash if you use "Reload user object" thats the quick way to re-produce it or just take off and land then the sim crash when you exit, as long as the webserver turned on. Link to comment Share on other sites More sharing options...
gkertesz 1 Posted May 13, 2015 Share Posted May 13, 2015 Completely agree with the "not closed correctly" thought. Then this might be the cause of strange issues that happening from one day to an other with the sim. Thinking over leaving the webserver: the MCDU is an undockable 2D window, so moving it to an other monitor can be a solution for me. Link to comment Share on other sites More sharing options...
rangerobert 11 Posted May 13, 2015 Author Share Posted May 13, 2015 ... I should not use the webserver, which was one of the most excellent feature of this aircraft to have the MCDU on a tablet, and which gets us closer to reality with a big step? Question mark. In fact ti is just what I do, also because that if I try to use this feature (MCDU-left on iPad) by accepting the malfunction of Crash-on-exit with Webserver ON ... it doesn't work, in simple words. On my system, actually. I suppose that still exist other people happy with that. But be advised we have some hope, as Mathijs is working right now on this issue on one support ticket opened on the issue under my name .... Thinking over leaving the webserver: the MCDU is an undockable 2D window, so moving it to an other monitor can be a solution for me. Good luck, my friend! Also this workaround unfortunately is not allowable to me. Or at least, not with 100% of satisfaction. In fact the "undockable 2D gauge" window moved to my secondary monitor suffers on my side of another trouble: "MCDU-left - Fonts distortion?", that is another post originated by me. You can follow it here http://forum.aerosoft.com/index.php?/topic/94585-mcdu-left-fonts-distortion/ Minor issue, as when I input my flight plan data I can temporary eliminate the "residues of former text line" on the right edge of MCDU-left display by resizing the window to get back to original size with a few moves of mouse. Too bad ... but it looks like this feature (MCDU on iPad ...) was doomed for me, lol Bye roberto P.S. Confirmed: I'm in trouble in quoting or multi-quoting on posts on this forum if I use Internet Explorer 11. No problem if I use Chrome browser Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.