LatinVFR forums

Just a FYI, I am getting trees at the Bravo Gates at KBWI with Photogrammetry off. Many of us don't like using PG as it makes the building look melted and it effects performance. With PG on there not there and the ground textures are more sharp. I take it your scenery is built around Photogrammetry?...

If this can't be addressed with Asobos help at least give users the option to choose between realistic and unrealistic terrain in the next update. Unless the plane is doing back flips some of us can live with a little wobbling during taxi.

Thanks Ricardo That took care of the issue. Seeing I like to have my autogen all the way up I will just get into the habit of enabling or disabling KMIA or KFLL when I fly to them. Now I need to fix the texture issues at KMIA, When I zoom up to view the airport it looks like the default building com...

I briefly read through the forums and was wondering if any plans were still in works for fixing the performance issue at KFLL? I just finished a new build "see specs" and I run my system on a 4K @ 30hz. New install of Win 10 and P3Dv5.1, all latest versions. I've tested over 3 dozen tops end sceneri...

You guys pushed out an update but you still left this option out in the SDK check box to tag the scenery in the map

Next time you update the scenery can you check the box in the SDK that will tag KMIA with a yellow star to show it's an enhanced/add-on airport. It makes it really convenient when look at the map and knowing what we have installed.
Thanks

Sorry but turning down the Autogen/Draw Distance to medium is not a good option just to get your scenery's to play nice with each other. By turning it down to medium will effect the entire sim. I've used medium before and watching autogen load right under you compared to further out is not an option...

Do you know when this will be fixed because I see the same problem as the original poster. My system is a 1080ti, and a 8086K @ 5.2 with M2 SSD and 32gb of memory so I know it's not my system. I know your working on P3Dv5 but those of us on 4.5 would like to see this fixed.

I should have added, several of us in my VA are all seeing this issue and we all have different setups. I take it now that v5 is out that support and fixing this issue is not going to happen for 4.x users?

The first spot is on T just before N and the second spot is when you turn on N from T.
https://youtu.be/RYVuaZXRu6k

https://prnt.sc/rn7xb6

https://prnt.sc/rn7zcp