Well, I ran this morning v5.3 HF1 LF, and as soon as I was at my airport, I got complete pause/lock up, and then release...for about 10 seconds...and another full animation pause/lock up...and on and on...every 10 seconds or so!

The short story....it was Active Sky, that had not properly shut down and disengaged from P3D.  Now here's the part to note...this happened when I shut P3D down and then shut down A.S.   This morning, I did not run A.S. but got those lock ups...etc. 

I then REBOOTED my system, and ran P3D again...and lock ups...still there.

So...I ran P3D again...and started A.S.   Low and behold, a window popped up stating that a session was already in progress, do I wish to shut that down?   What?!??????   I had no 'session' running this morning before I in fact DID once...fire up A.S.  

So, the 'other' grandfathered 'session' was closed by A.S. and then I got the opening screen and my thunder clap.   

This suggests that unless A.S. is closed FIRST, and then P3D is ended, there is a chance that even if you then close A.S. it will not 'clean end' its 'session' which...seems to survive a complete system shutdown.  It's almost like a shopping cart COOKIE that will stay with that 'article' in whatever shopping cart until YOU remove it....system shut down or no.

That caused really bad performance, and was in the background when I ran P3D WITHOUT having started an A.S. session.  So...if you all of a sudden, or from the get go...have really terrible animation performance, stutter, freeze ups, total lock ups..it just might be that A.S. did NOT clean end...and it still has the connector trying to interact with P3D, but of course, it is not a genuine (by you..) act to connect to P3D.  

If you get any of what I have typed about...RUN A.S. and see if it tells you that you already have an 'active' connection...and do you wish to end 'that' connection?   Press YES, and that should take care of all of the above freezes, pauses, crashes, lock ups...and if it ever happens to you again...suspect the same thing IS happening and run A.S. to clear up the bad loud out...of your last use....and oh...always right click, end A.S. before you end or shut down P3D, not the other way around...for I think that that was the cause of a bad full detachment of A.S. with P3D.

Did you post this at HiFi forum or send in a support ticket? If you want this fixed you need to. If you want to keep dealing with this issue and continue to run into problems, then by all means just post here. 

Make sure Windows is not auto-starting running apps on startup.  That would mean if AS wasn't completely shut down prior to system shutdown Windows would auto-start the process at startup (potentially)  Otherwise no reason for AS to have a session running even after a reboot...

 

16 minutes ago, B777ER said:

Did you post this at HiFi forum or send in a support ticket? If you want this fixed you need to. If you want to keep dealing with this issue and continue to run into problems, then by all means just post here. 

I don't need this fixed...for it was only (I feel) that you need to close A.S. BEFORE you end P3D.   I have had no further incidents, with now doing that.   I just wanted to give others a head's up...in case they were experiencing the same...and then how to fix it...the order of shut down of the two programs.

4 minutes ago, psolk said:

Make sure Windows is not auto-starting running apps on startup.  That would mean if AS wasn't completely shut down prior to system shutdown Windows would auto-start the process at startup (potentially)  Otherwise no reason for AS to have a session running even after a reboot...

 

That well could be...but at least, I have posted that it was that 'background' session ,  not instigated by myself, that with the next running of P3D had horrible performance. This might be happening to others, without them realizing what is going on...

15 minutes ago, Sesquashtoo said:

That well could be...but at least, I have posted that it was that 'background' session ,  not instigated by myself, that with the next running of P3D had horrible performance. This might be happening to others, without them realizing what is going on...

It could be but then everyone with the issue would get a notification about an AS session already running.  More likely is Windows started it in the background because auto-start running apps may be enabled and it didn't shut down properly before the system shut down...  

Cheers! 

 

Are you sure the session ASP3D is talking about isn't the session/login into HiFi's servers? I'm asking because I used to automatically kill processes related to the sim after shutting it down. After just killing (i.e. not shutting it down gracefully) and then restarting the AS process, it would say there was still a session open. I now just leave AS running between fights/tests.

1 hour ago, Sesquashtoo said:

So...I ran P3D again...and started A.S.   Low and behold, a window popped up stating that a session was already in progress, do I wish to shut that down?   What?!??????   I had no 'session' running this morning before I in fact DID once...fire up A.S.  

This happens when ActiveSky is not closed by the user, but one restarts the system, before closing ActiveSky. 

I thought, this is just related to the weather server at hifisim or somewhere. It is nothing on the users machine and the only thing I mind about it, the window is behind another ActiveSky Window, making it difficult to answer the yes or no question. I always answer yes and ActiveSky can initialize itself and I have no performance problems then.

. 

 

 

@Sesquashtoo, I wonder if you’re minimising ASP3D to the System Tray. You should just minimise it to the taskbar otherwise it won’t close properly when you exit P3D.

4 hours ago, Ray Proudfoot said:

@Sesquashtoo, I wonder if you’re minimising ASP3D to the System Tray. You should just minimise it to the taskbar otherwise it won’t close properly when you exit P3D.

what I do Ray, is right click CLOSE WIndow, to shut down A.S. but, I do think it also has something to do with if you shut down P3D before you shut down the programs that associate with a running P3D session. Like A.S. or FFTP. I now have made a mental note to always shut down other associated programs before exiting P3D. Since that mental note, no further 'ah hahs!'.

Edited December 30, 20214 yr by Sesquashtoo

This message is about being logged in to the servers, not about the program running. Happens to me all the time when I forget to close Active Sky before shutting down the PC.

25 minutes ago, Fiorentoni said:

This message is about being logged in to the servers, not about the program running. Happens to me all the time when I forget to close Active Sky before shutting down the PC.

Thanks for that.  Yeah, I had it a couple of times, but now, make sure that I have exited all programs before shutting down. 🙂

41 minutes ago, Sesquashtoo said:

what I do Ray, is right click CLOSE WIndow, to shut down A.S. but, I do think it also has something to do with if you shut down P3D before you shut down the programs that associate with a running P3D session

Use the X top right to close the application. Any other method might not shut it down properly.

Consider SimStarterNG as it will start ASP3D when you want it but will also close it and other ancillary programs after P3D is closed. I use it for EFB, Chaseplane, and LittleNavserver. Much easier than doing it manually.

The closing order is not critical. But minimising ASP3D to the system tray can leave the server connection open when terminated.

 

6 hours ago, Ray Proudfoot said:

Use the X top right to close the application. Any other method might not shut it down properly.

That's what I do for all my programs after flight is finished. Not really a pain. I start most of them automatically by using an .xml entry, so they start at the same time as P3D.

ActiveSky I start once P3D is up and running, then of course RC4 can start a bit later once the weather is available.