mmaier41 Posted April 21, 2016 Share Posted April 21, 2016 Hi, The Manual says: "SimpleCam is starting automatically with the respective option active and also automatically closedupon closing the simulator." No automatically closed by FSX on Windows 10. Where can i look for clearing this problem. Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted April 21, 2016 Share Posted April 21, 2016 No problems here. I see it closing all the time, even most of the times after a crash of FSX/P3D. The only reason I could imagine is that there could be a conflict with UAC settings and/or Installation as Administrator. You should have the UAC set to the lowest level and the checkbox in the Properties Box set for "run as administator". Other than that I'm a bit at loss. Maybe someone else has another suggestion? Quote Link to comment Share on other sites More sharing options...
mmaier41 Posted April 22, 2016 Author Share Posted April 22, 2016 Hi Oskar, many thanks for your answer "UAC set to the lowest level" this was OK "Properties Box set for "run as administator"" this was not set After a System-Restart it seems to be ok. Quote Link to comment Share on other sites More sharing options...
mmaier41 Posted May 2, 2016 Author Share Posted May 2, 2016 Hi, Urs and Oskar, i'm back again with the same problem. Same times will be closed most not. Otherwise i am very statisfied with the functionality specifically with the PMDG 737NGX. Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted May 3, 2016 Share Posted May 3, 2016 Hi Manfred, is there any unusual behavior of FSX/P3D before you close it? If SimpleCam does not receive the 'quit' information of the simulator then it will stay open. Quote Link to comment Share on other sites More sharing options...
mmaier41 Posted May 3, 2016 Author Share Posted May 3, 2016 Hi Urs, there is nothing no accident, nor anything else. My normal Fly-Satus for FSX is with following ADDONS are active: LINDA for control Saitek X52 ASN for weather EFB for flyplane PRO ATC-X for ATC and pre-flyplane GTX groundservice Accufeel for noise and sametimes FS-FlightContol for Landing-Training ect. All this addone's where not involved (not loaded) when i have checked this behavior. I use two monitors M1=EFB and M2=FSX. This is not vital, i will handle this by myself. two mouse click. The Log shows two CLOSE-Situation. ********************************************************** 2016-05-03 22:33:41.464 Debug ------- SimpleCam started ------- *************** FSX gestartet jedoch Flug noch nicht gestartet System-Close [X] *****************2016-05-03 22:33:41.547 Debug Verify license2016-05-03 22:33:42.510 Debug License successfully verified2016-05-03 22:33:42.571 Debug Waiting for running simulator process ...2016-05-03 22:33:48.116 Debug Connection to simulator is established2016-05-03 22:34:18.355 Debug Simulator terminated by user [X] ******** OK ******* 2016-05-03 22:34:18.384 Debug *** SimpleCam terminated2016-05-03 22:34:18.405 Debug 2016-05-03 22:34:43.121 Debug ------- SimpleCam started ------- *************** FSX gestartet und Flug gestartet - Pause - System Close [X] *****************2016-05-03 22:34:43.198 Debug Verify license2016-05-03 22:34:44.184 Debug License successfully verified2016-05-03 22:34:44.249 Debug Waiting for running simulator process ...2016-05-03 22:34:49.811 Debug Connection to simulator is established2016-05-03 22:35:56.637 Warning DefWndProc (isConnected=true): Ausnahme von HRESULT: 0xC000014B [X] ********* nicht OK ***********2016-05-03 22:36:29.877 Debug UnsubscribeSystemEvents: COMException raised: Ausnahme von HRESULT: 0xC000014B ***** SimpleCam User beendet *****2016-05-03 22:36:30.005 Debug *** SimpleCam terminated2016-05-03 22:36:30.007 Debug Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted May 4, 2016 Share Posted May 4, 2016 Hi Manfred, thanks for providing the content of the logfile. The second one means that FSX closed irregular and therefore the connection to SimConnect was broken (0xC000014B means "Pipe broken", where a 'pipe' is an internal connection between two processes). As a result of this SimConnect could not send the 'quit' signal to SimpleCam. That's what I meant in my previous post. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.