Pete -  if you have any traffic programs like MyTraffic - disable their specific bgl and see if that helps.

 

Yeah, thanks. Always done that.  Also I have a scenery checker which looks for and lists duplicate AFD files and even which class of element they contain. It draws a blank on EGLL - only the one in the Aerosoft folder it seems.

 

Pete

Also since the update I am not abel anymore to open up the ASN in-game menu. Did someone else discovered this problem? My ASN is updated to the last beta build.

 

As stated a few times before, any addon that uses pop-up menus requires the Content update (ASN, GSX, SODE etc.)

Yeah, thanks. Always done that.  Also I have a scenery checker which looks for and lists duplicate AFD files and even which class of element they contain. It draws a blank on EGLL - only the one in the Aerosoft folder it seems.

 

Pete

 

Well sorry to hear this - its the only scenery thats doing it ? strange - no its a pain wonder if you had a fresh install and only that airport - check it - if all is well - then start adding one by one then you will find the culprit - as you know uninstalling orbx completely is not a viable solution in my eyes

Thanks for the quick response.....So obviously I download the content.msi. Must I also download the individual cont1.cab file also?

Yes. Just place it in the same folderas the content.msi. That got me up and running...

 

Martin

With only 500M free over Michigan, there was no way that I was going to be able to land at KORD without an OOM. So I bailed out, and have reverted to 3.1.

 

I would give version 3.2 one more chance and try that flight without any VAS measurements. Just enjoy it I recommend deleting shaders and also completely switching off the road traffic (it solved OOM problems for me in 3.1). At least on my setup, version 3.2 looks better and performs better.

At Aerosoft's EGLL scenery I am getting grass textures over some parking areas and a bit over taxiways, mainly at the East end.

 

My two cents - terrain.cfg? Changes in terrain.cfg (made by an ORBX installer) caused trees on runways at Aerosoft EDDT. Would try the default or backed-up version of this file.

My two cents - terrain.cfg? Changes in terrain.cfg (made by an ORBX installer) caused trees on runways at Aerosoft EDDT. Would try the default or backed-up version of this file.

 

Good idea! (I was running out of ideas .. ;-) )

 

Pete

 

[LATER]

No difference. I noticed in any case that all of the ORBX changes are additional entries, it doesn't appear to change any existing lines.

Anyone else getting horrible night textures with aerosoft heathrow looks yellow and green anyone know a fix.

There's no harm Deleting your Shaders after the Update

There's no harm Deleting your Shaders after the Update

 

Or I can find ( Shaders) ?

Is ASN working on v3.2?

 

 

Or I can find ( Shaders) ?

 

Located here     ► Computer ► Local Disk (C:) ► Users ► your user name ► AppData ► Local ► Lockheed Martin ► Prepar3D ► Shaders

 

http://www.avsim.com/topic/479630-where-to-find-my-shaders-folder-prepar3d/

But it doesn't list EGLL, and you can't make it accept EGLL by typing it in the box above the list -- that box seems only to be a filter for the list.

 

I'm not seeing the grass you are talking about at the "East" end (or "West" for that matter).  Made a quick video of what I see:

 

 

This is with FTX Global + Vector + OpenLC EU with Pilot's mesh.  If I change to FTX EU Region I do see two Concorde aircraft overlayed, but not seeing any grass issues?

 

Can you describe or post a screenshot of what you see?  I'm not that familiar with this airport since it's an area I usually avoid until very recently with P3D 3.x releases.

 

And yes, it does appear EGLL can't be added to Vector config exceptions.   Is it possible you installed UK2000 EGLL V3 at some point, perhaps that introduced this issue?

 

Cheers, Rob.

Yes. Just place it in the same folderas the content.msi. That got me up and running...

 

Martin

Thanks..worked perfectly...menus are back.

I'm not seeing the grass you are talking about at the "East" end (or "West" for that matter)

 

Nor does anyone else I've found. That's why I *know* it can be solved. I've persevered now for three days (!), almost ot the exclusion of all else.

 

Can you describe or post a screenshot of what you see?

 

 

I'll try to get a screenshot of the main area where it's bad, and one from the UK2000 one whewre it's fine. I think I need to find a screenshot program to install. On my development PC I use ScreenHunter, but it isn't yet installed on my Flying PC -- I keep it as clean as possible!

 

And yes, it does appear EGLL can't be added to Vector config exceptions.

 

 

Strange, isn't it?

 

Is it possible you installed UK2000 EGLL V3 at some point, perhaps that introduced this issue?

 

 

I've always had UK2000 EGLL, and, yes, an up to date on v3. I prefer it. But the Aerosoft version gives TWICE the performance, allowing me to keep my AI traffic levels (UT2 + MtTraffic6) to the fuly realistic levels places like EGLL deserve. This performance difference is pretty much the same in both FSX-SE and P3Dv3.2 with P3D maybe just having the edge, but not by enough.

 

I have been swapping between UK2000 and Aerosoft versions whilst looking for this problem. Both are listed in the SCENERY.CFG, I just enabled whichever. I've been doing this long before being an Orbx user. And it's only since installing the very latest versions of ORBX and giving up my assorted UTX layers that I've had this problem.

 

Next I might try re-enabling the UT layers. Tomorrow though. I'm whacked for the day ...

 

Pete