FlightSim Development Group

Hi,

I'm having some significant issues with this scenery I recently picked up. The airport itself appears to render without issue, but the surrounding countryside is a mess of textures - mismatched, blurry... sometimes random water tiles appear too! All of these seem to randomly change, with texture squares swapping about as I fly around the area! A couple of screenies to illustrate:

https://imgur.com/lODKjBH

https://imgur.com/rvvqWNK

I'm sure it must be a conflict, but I've yet to chase it down. I've looked for other BGL files that might be causing a conflict, and the only other thing I can find is one from MyTraffic, and renaming that to BGL.OFF makes no difference. Here's a snap of what Little Navmap reports about where it's getting LTFE data from:

https://imgur.com/4bn2m5T

I've uninstalled the FSDG Bodrum scenery, and the default textures looks fine, with no anomalies. I reinstalled, running as admin, and I get the exact same issues back again :/

I'm running P3D 4.1 on Windows 10 Home, I have FTX Global and Vector, and use Toposim terrain mesh.

One other strange issue I encountered, which may or may not stem from the same root cause... When taxiing around the apron it appeared as though I was going over grass, with particles kicked up from the wheels, and one time the aircraft even crashed. Clearly what the simulator thinks the ground surface is doesn't tally with what's being rendered.

Any help would be greatly appreciated!

Thanks,

Sam.

I have never seen this before. The Sim rendering aerial imagery instead of landclass tiles is very unusual. I would assume there's something wrong with P3D. Did you recently install an update? Please check if you have the latest version installed.

So after much googling it appears that the issue was down to a bad FTX Global install. I followed the following advice:

https://www.avsim.com/forums/topic/5222 ... nt-3735011

And after a "Repair" install of FTX Global, the Bodrum region then rendered as expected.

Thank you very much for getting back to me... Hopefully this might help others out in the future if they encounter similar issues.

Thanks for that information. We did not have any reports of that before but good to know there is a fix for it.