Lighting is obviously broken and I'm sure LM is aware and fixing. Just because some dude trying to promote his YouTube channel wrote [SOLVED] in his click-bait subject line, that doesn't negate the reality of the state of lighting in P3D.

Why do you have HDR override checked in ChasePlane while also having HDR on in P3D? Makes zero sense.

This might have something to do with "Enable Mouse Controls" being checked in the Other Controls tab of the settings. Try unchecking that.

I updated my P3d to V5.1 and the Add on FSL A320 doesn't running with V5.1. A FSL's massage (Regarding the p3d version) is appeared during the launch and the P3d Crashed. When I return to P3d V5.0 the problem didn't appear again. So, the problem is the P3d software or the FSL software ? Thanks. You...

This bug sucks. LM needs to acknowledge it, because as we've seen over and over, reporting bugs on this forum is pointless unless they physically put their fingers to the keyboard and reply to the bug reports.

Just delete hazards.bgl and move on. It's been a bug for 9 years now since P3D V1, so you can guess where it lies on their priority list.

Turn off EA in Display settings.

I get a pop up that says "Please correct errors or cancel."

The only solution is to quit and restart P3D.

Hi all, Getting myself ready to fly today the scenery was looking great. Then as the sun started to set the sky went bright red and passthing through the cloud layer was completely black. Any idea what I may need to do to fix this? V5.1. Was also using the Activesky beta https://pasteboard.co/JyWzB...

Out of curiosity, can you post a screenshot of what the new window looks like? I'm not on 5.1 yet but am wondering what it looks like and if it's really going to be a problem.

jadolfo wrote: ↑Sat Oct 31, 2020 1:43 pm Hello,

With 5.1 is impossible to make a completed flight, always CTD. I tryied to disable SODE, but not resolve the problem. I rolled back to v5.0.

Cheers!

Be specific - is it the ucrtbase.dll CTD that you're seeing even with SODE disabled?

This bug was reported in July.... https://www.prepar3d.com/forum/viewtopi ... ng#p218314

How did they screw this up? 5 months to fix this bug. Not only is EA still in rough shape and using a ton of VRAM, but we can't even go back to the old 2D clouds without incurring this other issue.

Thanks for your reply Rob, I think this is the biggest fault of P3D at present. Seeing Rob's reply gave me a lot of confidence, and I still strongly look forward to the improvement of V5.2. Yeah, that's not coming for another 6 months. Meanwhile, P3D will continue to hemorrhage users and third-part...

Don't worry about the video. This bug has been around for months and I guess LM just punted on fixing it.

Alox wrote: ↑Tue Oct 20, 2020 5:33 pm Hi, LM

Would you share with us when will you release the next update.

Thanks.

Regards.

They don't give out release dates and they don't read this forum anyway.