I'm having the annoying issue with most FlightBeam products where the default airports are bleeding through in certain areas, BradM from Twitch also had the same issue, anyone else? 

So far SFO is having this issue.

Edited April 14, 20206 yr by mcdonoughdr

Is it confirmed Flightbeam installers made for v4.5 are working in v5? 

Here you go - this may apply to other but for Orbx - These are the known issues

 

https://orbxsystems.com/forum/topic/190950-known-issues-with-prepar3d-v5/

 

• Pixelated edges around trees and buildings, against clouds or background terrain, when Enhanced Atmospherics is active (note that LM note this feature as "Beta" and therefore still being improved upon)
• Hardened platforms on custom bridges don't seem to work meaning road traffic drops to the ground/water level instead. Extrusion bridge platforms work OK.
• The default road vector system is missing many tunnels and thus, outside of our regions, one will see roads crossing mountains.
• The visual effects system has been changed and thus some dynamic effects (smoke, spray, lighting, etc.) may be oversized or display odd colors or have transparency issues.
• [REGIONS + SOME AIRPORTS] Because all default airports have been made new and thus buildings, structures, and objects shifted around, it's likely that any third-party add-on that doesn't include an airport-wide object exclusion will now display duplicate or overlapping objects.

Edited April 14, 20206 yr by Skywolf

Thanks guys, just annoying because FlightBeam updated there store 1 hour ago with official installers for V5 lol

20 minutes ago, SAS443 said:

Is it confirmed Flightbeam installers made for v4.5 are working in v5? 

Yes, there official store was updated with installers that support V5 about an hour ago.

There was a specific issue that allowed this bug to slip through into our new installer. We've got new ones uploading at the moment that resolves the issue. In the meantime, if you want to patch it easily yourself, you can do so here: http://flightbeam.net/forums/viewtopic.php?f=32&t=3721

Oh well this can be a real headache for airports not updated to v5. Wonder if many airports suffer from these changes?