1 hour ago, Sesquashtoo said:

Ian, I have all my Orbx 'sfuff' in the P3D root, except for the Library that will not install other than via a Library, and nothing got ruined. I merely re-verified and all was as before...and I have around 20 or so XML add'on's in the Add On folder that also were left intact.

I think it is like all PC/Sim stuff, no-one really knows what will happen until it does.

I've just completed Moscow - Paris de Gaulle. 3h 30m in the PMDG737-800 in real time. No issues whatsoever.

EA=Off. Vol Clouds=Off. ASP3D/ASCA injected weather.

FSUIPC log reports average fps = 30.3fps. Max AIG Ai traffic = 213 aircraft of which 163 were deleted to maintain 30fps when P3D was running. I had fps of 30 when on finals and landing at LFPG. That's impressive.

Here's my JobScheduler entry which I haven't touched. HT is off on a 6 core i7-8086K running at 5.1 for 3 cores and 4.9 for the remainder.

[JobScheduler]
AffinityMask=63
P3DCoreAffinityMask=63
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=4

6 minutes ago, Rob_Ainscough said:

That's unfortunately part of the problem, very few people will list everything they are actually using nor what might be installed on their OS etc. ... add to that confusion very few try to isolate and just rather come to conclusions which doesn't solve problems.  I've started from ground zero, default install, default aircraft ... logging all data parameters to file via HWinfo and RTSS ... 7 hours and counting ... I'll give it another 5 hours before I terminate the unlimited fuel flight and go over the log data to see if I detect anything.

Cheers, Rob.

EDIT: I kid you not when some users tell me, oh yeah I'm watching YouTube videos during my flight sessions.

Funny OT story.  When we upgraded one of our customers from a VPN/MPLS backbone to SDWAN they noticed the bandwidth at one of their Dev sites was skyrocketing.  After increasing bandwidth licenses a couple of times we decided to turn on AVC which for us is Application Visibility Control.  Turns out the excess bandwidth was developers watching live game streams...  Not even playing games but watching live game streams.  The customer just "assumed" all that bandwidth was going to their dev work.  So I absolutely believe some users are watching YouTube while simming!  That's why despite my personal frustrations I'm yet to point the finger at 5.3...  

Right now the only correlation I see is in every report both EA and a PMDG/FSL or equivalent add-on is in use.  I've only seen one user report this with default AC/Airport.  

I also had a "white screen" is the only way I could describe it with EA enabled and the 777.  While P3D was loading the entire screen went white.  Looked like the sim had hung but it was just loading.  Enabling the virtual Camera option in the PMDG 777-300 (CAM on C/P EFIS)  loaded that same white screen in the lower console screen until it loaded the image.   Funny thing is I had actually completed one flight in 5.3 and it was prior to .31, I was still on version .30 which had the road traffic fix but not runway lights if I am correct and I had EA disabled at the time...  Ray completed his flight with EA off as well.  Just noting that on the side for when I start again in a far more pragmatic manner from scratch.  

Currently flying pmdg 737 from imaginesim Katl to orbx kbur.

orbx open lc US, orbx „so-called“ , active sky, asca, ea enabled. No volumetric clouds. Global traffic and aigai traffic.

no issue’s nearly constant 28 -32 fps. (Limited to 32 fps)

 

 

Edited December 27, 20214 yr by 331BK

Just to restore my own sanity I threw my P3D V4.5 SSD back in, re-activated some add-ons with new codes and did KEWR-PHNL using the same ActiveSky build as 5.3 just a different connector, PMDG 777, GSXV2 same exact AIG files and all my add-ons active in 4.5.  11 hours from sim start to shutdown without any issues.  After all the stress testing and a successful 11 hour haul in 4.5 I'm confident in the "system" aspect of it.  Back to Radiology tonight and then tomorrow I will wipe my botched V5.3 install by resetting Windows and deleting files then start from scratch.  Even if there is some sort of EA issue in 5.3HF1 I need to get my own house in order 😉   

Ah, what a relief to complete a flight LOL.  I feel like I am really in Honolulu right now (until I walk outside and it is 36F and raining LOL)  

Cheers and back at it tomorrow afresh.  Time to go count backwards from 1,800-0 which is what I do to pass the time during the tests...  I lose track and have to start over so many times during the 30 minute test it's usually over before I get down to 1,000 LOL.  

Edited December 27, 20214 yr by psolk

7 hours ago, Rob_Ainscough said:

I thought both PMDG and FSL require HiFi ASP3D in order to get their weather radar working?

On a side note, I was using iFly which also loads weather from HiFi ASP3D and I did notice that it took 30 seconds to read the weather data from ASP3D which seems odd.  However, the task should be threaded and running on a separate core ... I'm wondering if that ASP3D task is being pushed to the RenderThreadScheduler core or FrameWorkerThreadScheduler core which is might be the source of stutters and drastic FPS drops.

I have seen the issue where my screen goes completely black (which I assume is the shader cache being flushed) when HiFi ASP3D does it's weather injection for EA ... that only started happening with the latest HiFi ASP3D build 8027.

If my default 12 hour flight doesn't show any issues, then I'll try PMDG fully fueled but I'm not sure how long PMDG are willing to keep resetting my license count on my test PC.  

I'll keep folks posted if my 12 hour "default" flight with default aircraft has any FPS issues in my log data.  If that flight is good, then testing moves in a different direction and I start looking at specific add-ons (i.e. PMDG/FSLabs + HiFi ASP3D) and see if I can replicate.

Cheers, Rob.

 

Then how do you explain people getting this bug that are not running ASP3D? It seems to me you're fixating on one program for some reason without anything to back it up. Not trying to be snarky but I fear as your a beta tester with LM, your are beginning to draw conclusions that are not correct. The only common denominator is EA on is what the trigger seems to be. 

Edited December 28, 20214 yr by B777ER

11 hours ago, Ray Proudfoot said:

I've just completed Moscow - Paris de Gaulle. 3h 30m in the PMDG737-800 in real time. No issues whatsoever.

EA=Off. Vol Clouds=Off. ASP3D/ASCA injected weather.

FSUIPC log reports average fps = 30.3fps. Max AIG Ai traffic = 213 aircraft of which 163 were deleted to maintain 30fps when P3D was running. I had fps of 30 when on finals and landing at LFPG. That's impressive.

Here's my JobScheduler entry which I haven't touched. HT is off on a 6 core i7-8086K running at 5.1 for 3 cores and 4.9 for the remainder.

[JobScheduler]
AffinityMask=63
P3DCoreAffinityMask=63
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=4

Now try with EA on, volumetric off for a few flights. 

6 hours ago, B777ER said:

Now try with EA on, volumetric off for a few flights. 

One flight should be enough according to the reports. I’ll have to edit the cfg to keep HDR off as the VC becomes too dark.

5 minutes ago, Ray Proudfoot said:

One flight should be enough according to the reports. I’ll have to edit the cfg to keep HDR off as the VC becomes too dark.

 

5 minutes ago, Ray Proudfoot said:

One flight should be enough according to the reports. I’ll have to edit the cfg to keep HDR off as the VC becomes too dark.

You find it half way down the .cfg as HDR=1   replace the 1 with 0 and then press SAVE.  

22 minutes ago, Sesquashtoo said:

You find it half way down the .cfg as HDR=1   replace the 1 with 0 and then press SAVE.  

I knew that but thanks anyway. 😉

9 hours ago, Rob_Ainscough said:

Not sure the point of that?  P3D v4.x doesn’t have EA which is one of the three requirements to trigger the problem some (not all) users are having.

• EA on
• HiFi ASP3D
• A complex aircraft that requires ASP3D when EA is On

Cheers, Rob.

The point was strictly for my own sanity to ensure the system would still complete a long haul in 4.5 and the issue didn't lie in my HW...  If I put 4.5 back in and the system crashed the clearly there is an internal system issue.  Confirming 4.5HF3 is fine, running multiple stress tests and benchmarks, confirming temps all helps exclude that there may be something HW related on this side.  As I said, it was a sanity check on my part and quite frankly after a weekend of watching 5.3 crash on my system I just wanted to do a flight and complete it... 

There are reports of this happening on vanilla P3D installs on the LM forums with no ASP3D as well so not sure those are "requirements" of the issue.  A bit soon to come to a definitive statement on my part.  Also used the same version of ASP3D with 4.5 HF3 just the V4 connector instead of the V5 connector.  So it doesn't appear to be an issue with ASP3D injection, maybe how 5.3 is using that injection in conjunction with EA but I don't think the issue is with ASP3D or anything it is doing, perhaps it's in the connector or how 5.3 is implementing what it gets from ASP3D in conjunction with EA.  The fact there are reports without ASP3D at all does tend to make that less of a factor in my opinion.  

There are reports of this occurring at default airports with default aircraft after some time of just sitting at the gate so there may not be 3 requirements to replicating this.  Users who simply shut off EA seem to be experiencing far better results even with HiFI ASP3D and complex aircraft so the issue "may" lie in LM not resolving all the EA issues in 5.3.   @Ray Proudfoot I believe you know Andrew at FSL.  He seems to have confirmed this issue and that it is not resolved in 5.3HF1.  I did not see any mention it has anything to do with ASP3D but seems to be saying the bug lies with LM and has not been addressed  in HF1.  

It seems like everyone who reverts from 5.3 resolves the issue using the same add-ons they were using in 5.3...   It certainly points to something in 5.3HF1 or the 5.3HF1 upgrade process going sideways despite some people not encountering the issue. It's too far from being isolated issue at this point, reports are here, the LM forums the PMDG forums the FSL forums all with the exact same results.  For some reason or another 5.3HF1 is not playing well with a lot of systems out there at the moment that worked fine prior on 5.2 and work fine again after reverting to 5.2 including the FSL dev team and I'm fairly certain they are aware what they are doing which helps to rule out this being a user issue and sort of disputing the "requirements" to trigger the problem.  FSL is in no way pointing to ASP3D being a requirement of replicating the issue that I can see. 

Edited December 28, 20214 yr by psolk

25 minutes ago, psolk said:

@Ray Proudfoot I believe you know Andrew at FSL.  He seems to have confirmed this issue and that it is not resolved in 5.3HF1.

Yes, I know Andrew but as I don't have the Airbus I can't discuss this on an even playing field. But if he say's there's a problem I believe him.

I've just departed KBOS(Fly Tampa) and enroute to O'Hare (FSDT) with the PMDG737. I have changed EA to On via SimStarterNG but HDR is Off. Date is 27/12 departed 09:38 Local.

There was one lengthy pause (3 secs) at 2500ft after departing 33L but since then it's been fine. I've changed nothing in ASP3D to cater for EA being On. If you change more than one thing and the sim has a problem you don't know which change was responsible.

Landed at KORD a short time ago. No issues at all with EA=On. fps sufffered a bit on approach as it's a complex airport plus there was a low cloud base. FSUIPC killed all but 50 of the Ai to keep the frame rates up.

Sorry I can't deliver any positive news. Clearly the problem is more than just EA being enabled.

39 minutes ago, Ray Proudfoot said:

Landed at KORD a short time ago. No issues at all with EA=On. fps sufffered a bit on approach as it's a complex airport plus there was a low cloud base. FSUIPC killed all but 50 of the Ai to keep the frame rates up.

Sorry I can't deliver any positive news. Clearly the problem is more than just EA being enabled.

Keep the sim running and try a few more flights with EA on and see..... 

3 minutes ago, B777ER said:

Keep the sim running and try a few more flights with EA on and see..... 

I thought @Rob_Ainscough had already concluded EA=On with no other changes was not the cause.

I will try a few more flights but I doubt this setting alone is responsible.