ErichB

P3D 4.4 Texture (layering) issues?

Recommended Posts

My entry into the 4.4 space has been somewhat frustrating.  After a number of issues with the P3D modular upgrades, I decided to wipe everything and start from scratch.

I have installed Orbx Global Textures, LC and Vector,  FTX Lights and Orbx Libs., PTA,  FT Amsterdam, FT Boston and Drzewiecki Design's JFK and NY City scenery - so far.   The scenery layering is logical in my scenery library - and also as per the recommended method using Poppet's tutorials - (Airports/FTX layers/ OpenLC layers.  Everything followed the Orbx tutorials.

The strange issue I have is that the ground texture I'm seeing at airports  (DD NYC,  Boston) and surrounding Orbx scenery (using winter season) is a brown low res,  base layer photoscenery - over which the final high res textures are usually placed.   When I switch to summer season, the Orbx textures are pale green, low res,  photo textures.    I experienced this issue when using the modular upgrade method (which is why I decided to start from scratch) and I'm experiencing it again having done a clean install.  

It doesn't appear to be a problem with Orbx specifically, because it's also happening at my airports.  Not experienced this before and I have tried all possible remedies suggested  in the Orbx tutorials to remedy issues.

Obviously I'm missing something really simple (usually the fix is annoyingly undramatic) but I'm stumped if I know what it is.

I cleaned out all residual folders/files before the clean install.  When I experienced this issue using the modular upgrade, I thought it might be shader related so I flushed the shaders.  It didn't help.  I updated graphics drivers over the weekend, although this seems to be a layering issue and not a graphics issue.

Pearls of wisdom eagerly sought.

I have pasted some pics of NYC (after clean P3D install) and Toronto (after modular install).  You can see the surrounding Orbx region and the airport ground texturing )

DD JFK

UnH5Ovh.jpg

 

FT Toronto with Orbx Global, LC and Vector installed.

CbU3uLc.jpg

UdBdPhw.jpg

 

 

 

 

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Did ftx central do the lclookup migration routine? You can force it if not. 

Edited by GHarrall

Share this post


Link to post
2 minutes ago, GHarrall said:

Did ftx central do the migration routine? You can force it if not. 

Yup, did that

Share this post


Link to post

I have exactly the same problem after numerous clean installs and by the way if you turn auto gen buildings to spares ore none buildings and sim objects disappear. 

I think this happens with clean installs and not if you update the sim by client as the v4.3 scenery is still present. Glad i am not the only one, been struggling with this one since v4.4 was available- a week now 😢

Share this post


Link to post
10 minutes ago, kurtb said:

I have exactly the same problem after numerous clean installs and by the way if you turn auto gen buildings to spares ore none buildings and sim objects disappear. 

I think this happens with clean installs and not if you update the sim by client as the v4.3 scenery is still present. Glad i am not the only one, been struggling with this one since v4.4 was available- a week now 😢

Thank God. I’m not a total blithering word not allowed.  

This doesn’t happen when you only install the client. But it does when you install content and scenery as well and it has also happened with a full clean install with everything wiped. 

Hope some light gets shed on it soon

 

Share this post


Link to post

I started noticing it when I turned off the autogen building slider because for one, i dont like the autogen prefer photoreal, so even with clean installs this happens. Installed FS GLOBAL mesh ORBX , the same problem. I even wiped my system fresh installed windows, then v4.4 , agh what a shame

Share this post


Link to post
45 minutes ago, kurtb said:

started noticing it when I turned off the autogen building slider because for one, i dont like the autogen prefer photoreal,

Well the autogen sliders are set to half on my sliders and the autogen seems to be pretty badly rendered in my pics too.

Share this post


Link to post

Ensure ORBX Libs are up to date, that cause a similar issue for me in 4.3. Did you delete your P3D.cfg and let it rebuilt after installing the new client? And try limiting the framerate see it makes any difference.

Share this post


Link to post

believe me i tried all of that several times🤞

Share this post


Link to post

The first thing that I would do is install the Lorby Add-on Manager and see if anything seems unusual when looking at the scenery library. I'd suspect DD add-ons as I have had problems with their installation app a few times before.

  • Like 1

Share this post


Link to post
33 minutes ago, ckyliu said:

Ensure ORBX Libs are up to date, that cause a similar issue for me in 4.3. Did you delete your P3D.cfg and let it rebuilt after installing the new client? And try limiting the framerate see it makes any difference.

Multiple times.

Share this post


Link to post
24 minutes ago, jabloomf1230 said:

The first thing that I would do is install the Lorby Add-on Manager and see if anything seems unusual when looking at the scenery library. I'd suspect DD add-ons as I have had problems with their installation app a few times before.

I have similar issues in Europe too and don't have DD installed there.  It seems to be a global issue.  But I might give Lorby's Addon Manger a try

Share this post


Link to post

Use it just to see if there are issues. 

  • Like 1

Share this post


Link to post
2 minutes ago, jabloomf1230 said:

Use it just to see if there are issues. 

I ran the P3D Content Error reporting tool, but that didn't raise anything related to scenery, terrain or texture conflicts

Share this post


Link to post

Erich,

Try rebuilding a new "terrain.cfg" located in %ProgramData%.

Rename "terrain.cfg". Start P3D to the scenario screen then shut down. Start FTX Central and let it do its thing then shut it down. Delete shaders in your AppData\Local directory.

Run P3D to see if there's a difference. Not familiar with your scenery, some might have also written to the "terrain.cfg" and have to be reinstalled.

  • Like 1

Share this post


Link to post
22 minutes ago, ErichB said:

I ran the P3D Content Error reporting tool, but that didn't raise anything related to scenery, terrain or texture conflicts

What about the order of entries in the scenery library? Anything look unusual (like having ORBX entries at higher priorities than 3rd party airports)?

It's possible that terrain.cfg got muddled up somehow but except for ORBX, most add-ons don't tinker with that file. Twenty6's suggestion is worth a shot. 

  • Like 1

Share this post


Link to post
10 minutes ago, jabloomf1230 said:

What about the order of entries in the scenery library? Anything look unusual (like having ORBX entries at higher priorities than 3rd party airports)?

It's possible that terrain.cfg got muddled up somehow but except for ORBX, most add-ons don't tinker with that file. Twenty6's suggestion is worth a shot. 

No, the library order layering is all logical and as per Orbx tutorials.

27 minutes ago, Twenty6 said:

Erich,

Try rebuilding a new "terrain.cfg" located in %ProgramData%.

Rename "terrain.cfg". Start P3D to the scenario screen then shut down. Start FTX Central and let it do its thing then shut it down. Delete shaders in your AppData\Local directory.

Run P3D to see if there's a difference. Not familiar with your scenery, some might have also written to the "terrain.cfg" and have to be reinstalled.

I went through those routines when i was having issues with the modular installations over the weekend, but haven't deleted the terrain.cfg with the new install yet.   I'll try this sequence out tonight. Thanks.

 

Share this post


Link to post

Various ORBX packages add a bunch of landclass and vector types to terrain.cfg. A few other 3rd party add-ons do so. Some examples are Tongass Fiords and Return to Misty Moorings. But most 3rd party scenery doesn't modify terrain.cfg. Once one deletes it, any scenery package that relies on the modified version of the file will not work correctly. Also there is no mechanism in place to prevent two scenery installers from different developers from updating the same entry in terrain.cfg.

  • Like 1

Share this post


Link to post

I had same problem over Spain and over Germany. Don't know the solution to that

Share this post


Link to post
6 minutes ago, mulgrave said:

I had same problem over Spain and over Germany. Don't know the solution to that

What problem specifically?  Base layer low res, photo textures .  Only over Spain, Germany, or are those the only locations you tested?  Including addon airports?

Share this post


Link to post

I have the same issue in asia 

parts of land textures all whited out.

Bud that needs to be addressed 

 

Share this post


Link to post

Hi,

I only tested flights over Spain and Germany. Get same blue and brown textures on the grounds as in pics submitted by Erich.

Software:  Orbx FTX Global, FTX Germany, OPEN LC EU and Vector,  FS Global Ultimate,., PTA for P3dV4.4, active sky P3dV4.4 beta, Envtex, ASCA, PMDG planes

Spec:Win10 pro, I7 8700K CPU, GTX 1080TI, 4K Monitor ( running at 30 Hz resolution), 32Gb ram

Share this post


Link to post
4 hours ago, Twenty6 said:

Erich,

Try rebuilding a new "terrain.cfg" located in %ProgramData%.

Rename "terrain.cfg". Start P3D to the scenario screen then shut down. Start FTX Central and let it do its thing then shut it down. Delete shaders in your AppData\Local directory.

Run P3D to see if there's a difference. Not familiar with your scenery, some might have also written to the "terrain.cfg" and have to be reinstalled.

Jay

 I've tried all of these steps now, in the sequence you have suggested, but unfortunately no dice.

Would posting my terrain.cfg or scenery.cfg here assist anyone in spotting anything wrong?

I'm a bit lost as to where next.  

Share this post


Link to post

Starting over.  Clean install, but the rest tomorrow.

Share this post


Link to post

Might be a big PITA but when you reinstall your sceneries, do them in small blocks and test after each install. Perhaps you can narrow it down before installing ALL the scenery.

 

Vic

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now