P3D V5.1 Status after 10 days

[Bob Scott 7,720]

Rather than have folks wade through 23 pages of history in the initial release thread to see what's up with v5.1, let's recap and proceed in a new thread.

As I understand it, as of today (7 Nov 2020):

This point update really needs you to install the content and scenery modules in addition to the client module.  Though content/scenery are listed as optional, not installing them may cause issues or result in not having some of the fixes LM has made (e.g. scaleform windows used by ATC/Simconnect that caused crashes in v5.0 were replaced by HTML5 windows in the content module).

ucrtbase.dll crashes were an early unhappy phenomena and found to be caused by changes to simobject removal calls, often triggered by SODE jetways--a simple prepar3d.cfg setting is available as a workaround (and I would recommend it be standard for most users right now)--see post on the topic in our P3D tips and tricks forum.

ActiveSky for P3D has a beta version now working with v5.1, after initially having big problems with the 5.1 point release.  LM says a hotfix is coming to address the bug that caused the problem, but until then ASP3D appears to be functional with the workaround used in ASP3D beta version 7613.

Enhanced Atmospherics (EA) has issues with some objects from third-party scenery devs showing through cloud/fog layers, and excessive orange tinting around sunrise/sunset.  Some of the issues seen in v5 are still there in v5.1.  In general, there's a lot of angst still over the state of EA in this point release.  There's a lot more detail for those that want to dig through the initial release thread here:

PMDG, FlightSimLabs, Majestic Q400 add-ons that are already officially compatible with v5 are reported to work in v5.1, although the status of VC lighting issues in them is still unclear (a lot of general complaints about excessively dark VC lighting in v5.1).

Leonardo MD-80s not yet v5.1 compatible--their website says they are waiting for LM hotfix.

Status of other aircraft add-ons unclear.

Flight1 GTNs not compatible yet, RealityXP Garmins are.

That's what I have so far in my notes...feel free to update/add to the list.

[micstatic 4,319]

thanks for the new thread on this.  I intend to take the plunge from V5 HF2 once the maddog is updated.  

[threexgreen 3,139]

Personally, I'll wait until a few days after the hotfix has dropped and fly 5.0 HF2 in the meantime. I want to see first what the hotfix fixes, what needs to be updated again and what might go belly up with the hotfix.

[BerndB 349]

@w6kdeverything you wrote can be signed. Very good assumption. I updated 2 days ago, because i was waiting for AS to have it least for non-ea mode. All my add-ons have no issues with 5.1 and behave as in 5.0. If this point update can give us more stability in Terms of those anoying CTD like vcruntime.dll it´s worth to Upgrade.

Edited November 7, 2020 by BerndB

[ideoplastic 86]

Release version installed and done long hauls with PMDG, ActiveSky, FFTF, and payware scenery. Running smooth, no crashes so far. Envshade on, no HDR, running, Monitor at 30Hz and fps matching it. In clear conditions a thin fog layer is always present and with EA on it gets even worse. Hope they fix t his on next update.

[mikeymike 360]

 VC's with HDR on is almost pitch black..

 

 

This is because 3rd party content needs to be updated to cater for the new lighting environment. 

You cannot have a simulator with a new light engine and spec it to continue to work with all add-on's without any update.. such thing can only be achieved via which-crafting and Sorcering.. not via source code.
 

 

😂 thanks simbol.

can’t you give those idiots over at qualitywings at shout and tell them this.

as I read in their forums how someone stated the same issue with the 787. And  their reply from qw was that the aircraft in real life is the same it  is actually darker so it’s normal.

mike

 

[newtie 533]

This is easily fixed with FSL Spotlights.

https://www.flightsimlabs.com/index.php/spotlights-2/

Until the actual problem is fixed.

[IUBrian 151]

5.1 has been pretty unstable for me with existing ad-odds. I’ve had CTD panning around with ezca 3.1.0.40 at FSDT KORD and Flightbeam KSFO, problems with GSX requiring continuous restarts. I understand that with each add-on there’s another unknown variable added in terms of identifying the source of the crash, but I can only say prior to 5.1 with HF2 I had a relatively stable sim in terms of lack of random CTD. I have added the line to the cfg that was supposed to address the SODE issues, so I’m not sure what the source of the issues are. 
 

This is on top of issues with EA and HDR that have already been extensively documented. I’m not going to put LM on blast as others have done; in no small part the widely variable ways to modify the sim means an almost infinite number of possible combinations of modifications for which it would be virtually impossible to test prior to release “in the wild,” but that said, it has been a bumpy and frustrating experience thus far for me. 

[Flic1 976]

11 minutes ago, IUBrian said:

5.1 has been pretty unstable for me with existing ad-odds. I’ve had CTD panning around with ezca 3.1.0.40 at FSDT KORD and Flightbeam KSFO, problems with GSX requiring continuous restarts. I understand that with each add-on there’s another unknown variable added in terms of identifying the source of the crash, but I can only say prior to 5.1 with HF2 I had a relatively stable sim in terms of lack of random CTD. I have added the line to the cfg that was supposed to address the SODE issues, so I’m not sure what the source of the issues are. 
 

This is on top of issues with EA and HDR that have already been extensively documented. I’m not going to put LM on blast as others have done; in no small part the widely variable ways to modify the sim means an almost infinite number of possible combinations of modifications for which it would be virtually impossible to test prior to release “in the wild,” but that said, it has been a bumpy and frustrating experience thus far for me. 

Brian - Have you tried this fix for the CTD?  It fixed the CTD's for me and was recommended by LM as a temp fix.  Just add it to the 'SIM' section of your P3D.cfg:

[SIM]

AdaptiveSimGroupEnable=False

 

 

[IUBrian 151]

.

Edited November 8, 2020 by IUBrian
Duplicate post

[IUBrian 151]

Thanks, yes I did add that line, was hoping it would be the cure all, but alas it was not 

[Gridley 257]

This was very helpful thanks!  I initially just did a client update, but after seeing this have done the content as well, and the sim is much smoother.  I have yet to do the scenery update, but I suggest every follow these tips and at least do the client and content.

[Dreamflight767 312]

Sorry, what do we need HF for v5.1 to fix?  Is it just compatibility with AS?

[fluffyflops 1,858]

1 hour ago, Dreamflight767 said:

Sorry, what do we need HF for v5.1 to fix?  Is it just compatibility with AS?

And the txt box issue, if you use the FSL and want the sticky warnings on.  

Edited November 8, 2020 by fluffyflops

[micstatic 4,319]

Hopefully they fix the dark side of the plane. Almost looks like P3d used to before pbr or tomatoshade