My 5.1 - installed client only- loads the start menu (with the LM 35 lighting selected) but freezes after 10 seconds and eventually CTDs claiming that faulty module is KERNELBASE.dll.

Looks like I complete wipe is in order. Sigh...

4 minutes ago, Nuno Pinto said:

Never seen such a phenomena, but then again i don't use shader modifiers etc. The nacelles look bright and shiny... like metal.

nothing to do with shaders.  I don't use them.  A great way to see it is to look at the old american paint ngxu in V4 then compare it to V5.  You can read all about it on their forums.  But hopefully it's a thing of the past and we don't need to go into it

5 minutes ago, Flic1 said:

I just installed the client and hmmmm.....not sure what is going on but we have that strange 'haze' still with EA.  Also, you can see all the black buildings through it which was a big issue before.  EA always had that strange haze near the ground which looks to still be there even with clear sky setting.  I will have to mess around more but something seems off with the EA visuals for me. I also still see the issue with trees making that strange "blinking" against the EA sky/clouds......

Yes. Saw that too.

Overall it looks better as it was in Beta. But the following things still there, which I hoped they get solved:

• Blocky/White lines across simobjects (planes, trees, buildings, mountains
• Strange haze
• Still looking from high FL,  like FL300 and higher, down to the clouds ugly "quadratic pattern". Very imersive killing.
• Still "Simobjects" like trees, autogen, coming through the clouds

Overall performance seem better to me. I mean smoothnes, not necessary fps. 

Shading, reflections, shadows much optimized

Had 2 G2D.DLL and .NET CTD, which I also had prior this new release. Allthough NO ADDONS and completely clean install of windows 10 2004 with clean installed P3D V5! 

I will investigate some time further testing. Every improvement is welcome. But with the EA mode I think still lot of improvement should be done! MSFS has a clear big step ahead compared to P3D on this single point (just to compare ONLY Atmospherics). I still don´t like P3D basic implementation with EA. It is very shortcoming.

But time will tell.........first...enjoy what we have and I am also interested what others are saying about EA!

😉

Marcus

Sounds like EA still stands for Early Access...

40 minutes ago, Greggy_D said:

Been waiting for this update since Spring.  Finally time to install 5.x.

Err, why?  What am I missing?  Doesn't seem like an earth-shattering update to me.

20 minutes ago, micstatic said:

says in notes.  client only if you prefer

My fault; I meant which do most users find better?

2 minutes ago, Boomer said:

Err, why?  What am I missing?  Doesn't seem like an earth-shattering update to me.

You probably did not read the update info. It is a long list...

the grid like clouds I was hoping they could fix.  

I am a bit confused, and I know this has been addressed a million times so I apologize in advance. If I only update the client, do I get all of the updates? On the LM site they only recommend the client update. If not, I assume I can update the client, content, and scenery separately without messing up my P3dv5 instal? I have never done an update to Scenery, just client and content in the past and everything was fine.

Cheers, Pete

Edited October 28, 20205 yr by PilotPete99

2 minutes ago, Rob_Ainscough said:

I would update all three, Client, Content, Scenery (some AG legacy objects were updated to be compliant) ... I believe ORBX Central will do any "sync" process that "content" and "scenery" updates might overwrite ... other vendors not so sure about but in the past if I've had any specific vendor issues I just uninstall and reinstall for that specific vendor (be it aircraft, airport, scenery, etc.)

Cheers, Rob.

Thanks Rob, if any of the scenery needs to be reinstalled after, would P3d just indicate an error message? If not, what is the best way to tell if anything needs to be updated?

Cheers, Pete

36 minutes ago, SAS443 said:

My 5.1 - installed client only- loads the start menu (with the LM 35 lighting selected) but freezes after 10 seconds and eventually CTDs claiming that faulty module is KERNELBASE.dll.

Looks like I complete wipe is in order. Sigh...

Might as well add this is NOT a P3d issue.
I fixed it by disabling Ezdok.

Glad to read they added back in airport parking that has been missing.  Sadly, I guess the fix is not universal but a one-by-one, airport-by-airport fix.  Nice to see they fixed KSNA and curious to see how they improved San Diego (my home town and home of Flightsim Expo 2021).

How is EA VRAM usage now?

1 hour ago, KenVerburg said:

FSLabs just posted on their Discord: "@everyone with 5.1 out, please remember the A320 may need a patch to bring it up to standards. If you wish to continue to fly them please remain on 5.0."

I.E., continue to use the inferior version for about the next 2 months while we again update all 3 products which will again require a full complete reinstall and yes the Sharlets version that were "weeks" away in April 2020 will now be here in 2021. Thanks for your continued support.🙄

As the developer of the freeware volumetric cloud add-on for X-Plane (https://forums.x-plane.org/index.php?/forums/topic/218819-enhanced-cloudscapes-freeware-volumetric-clouds-for-x-plane-11/), I really would like to mention a few things about the visual glitches people are mentioning:

Sadly, aircraft and other objects (including terrain) having pixelated / flickering edges issue will probably stay forever - it is an issue caused by lower-resolution rendering of the clouds. Basically, as our current GPUs are unable to render all pixels of clouds real-time, a compromise needs to be done.

It is possible to render less per frame and then use temporal reprojection to reposition rest of the pixels (which is what MSFS is doing). It is quite nice, but it also causes lots of noise / grain artifacts.

Another approach is to render clouds off-screen with a lower resolution - as clouds are inherently blurry, it is possible to get similar results while rendering a lot less pixels (which is what trueSKY is doing). However, this approach causes an issue with depth testing (hence the interaction with all objects) as the depth buffer is now also low-resolution. This creates pixel "gaps" and these gaps become visible once they are overlapped into the final high-resolution screen.

trueSKY tries to prevent this effect by using both high and low resolution depth testing passes with some edge detection magic (I might be slightly wrong, check out the trueSKY SDK for more details: https://docs.simul.co/programming/rendering.html - the "Mixed Resolution Rendering" part) but it is not 100% effective, so you still get these artifacts. My plugin has the exact same artifact, and iirc even xEnviro. In other words, this is a general issue with all volumetric cloud implementations and there's not an effective fix yet.

Sadly, it's the same with new rectangular pattern observable in higher altitudes. But I still believe further updates might be able to hide that effect a lot better than now.

Edited October 28, 20205 yr by BiologicalNanobot