10 minutes ago, Rogen said:

Here's a few other shots above the bay.

 

 

thanks for taking a look.

Yes I have verified, reinstalled....the full works lol.

Interesting about littlenavmap, how do you view which scenery is active?

 

Double click on the airport icon on the map.

The airport details will then be displayed in the Information window and at the bottom will be the list of bgl's underlying the airport itself.

Or you could just type in the name/code of the AP.

Cheers

25 minutes ago, Rogen said:

Double click on the airport icon on the map.

The airport details will then be displayed in the Information window and at the bottom will be the list of bgl's underlying the airport itself.

Or you could just type in the name/code of the AP.

Cheers

Thanks, will give it a try.  Noticed just now flying out there that I had a duplicate 'baked in' pier offset to the 3d model in PAVD so I wonder if it is some conflict with ORBX Southern Alaska.  Giving it a try without.

 

Thanks for your help 🙂

Edited December 7, 20196 yr by Dreamsofwings1

Well I can fix the baked in pier and strong saw tooth streaks by disabling Orbx Southern Alaska.

If I remove the PAVD BGL files in Orbx Southern Alaska but reinstate SA then streaks and baked in pier come back so they must be part of another element of SA

Either way those square water texture tiles appear.

Littlenavmap isn't showing anything else apart from LM 0101 base

Scenery Order?

I have Southern Alaska and PAVD is above, as are all my other airports.

I have a dummy entry in my scenery.cfg which I use to mark where I want the FTX entries to go below.

And openLC all go below FTX.

Also PAVD in LNM shows four bgls for me.

Default Terrain	H:\Lockheed Martin\Prepar3D v4\Scenery\World\scenery\ADE_FTX_SAK_PAVD_elevation_adjustment.BGL
0101 Base	H:\Lockheed Martin\Prepar3D v4\Scenery\0101\scenery\APX09100.bgl
FTX_NA_SAK05_SCENERY	H:\Lockheed Martin\Prepar3D v4\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ADE_FTX_SAK_PAVD.BGL
FTX_AA_PAVD	H:\Lockheed Martin\Prepar3D v4\ORBX\FTX_NA\FTX_AA_PAVD\scenery\ADE_FTX_SAK_PAVD.bgl

 

Edited December 8, 20196 yr by Rogen

9 hours ago, Rogen said:

Scenery Order?

I have Southern Alaska and PAVD is above, as are all my other airports.

I have a dummy entry in my scenery.cfg which I use to mark where I want the FTX entries to go below.

And openLC all go below FTX.

Also PAVD in LNM shows four bgls for me.

Default Terrain	H:\Lockheed Martin\Prepar3D v4\Scenery\World\scenery\ADE_FTX_SAK_PAVD_elevation_adjustment.BGL
0101 Base	H:\Lockheed Martin\Prepar3D v4\Scenery\0101\scenery\APX09100.bgl
FTX_NA_SAK05_SCENERY	H:\Lockheed Martin\Prepar3D v4\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ADE_FTX_SAK_PAVD.BGL
FTX_AA_PAVD	H:\Lockheed Martin\Prepar3D v4\ORBX\FTX_NA\FTX_AA_PAVD\scenery\ADE_FTX_SAK_PAVD.bgl

 

ah that's interesting you have same as me.  Also with my ordering my PAVD is above SA entries which is also above my OPenLC NA.  I agree though, this problem does look like an ordering problem.

9 hours ago, Rob_Ainscough said:

The only time I've seen the squares rendering like in your video is when using:

TEXTURE_SIZE_EXP=10  (pretty rare)  or TEXTURE_SIZE_EXP=9 and High Resolution Terrain unchecked.

or 

ORBX Vector with Frozen surfaces enabled

If you have REX EF installed, disable it and delete your temp shaders folder and test again.

The pier overlap looks like a scenery priority order issue ... check your Orbx Insert point.

Cheers, Rob.

 

Rob THANK you so much!  I first posted about this on the Orbx forums in April and after all this time nobody as managed to fix the squares until you came along!  I had High Resolution Terrain checked but I changed to TEXTURE_SIZE_EXP=8 and squares have gone!

Do you know if there is a way around this as it seems a shame to have to hold it back just to stop the squares in this PAVD area, or is this just one of those "it is the way it is" P3D quirks?

I also double checked my scenery library and I can't see any order issues.  PAVD is right there at the top and Southern Alaska is above OpenLC.  Can you spot anything out of the ordinary?

and thanks again for your help!!  Finally the mystery of the squares is solved!!!

 

Edited December 8, 20196 yr by Dreamsofwings1

Interesting discovery that the culprit of the squares would be a TEXTURE_SIZE_EXP= setting in the .cfg, Glad it's all sorted.

41 minutes ago, DJJose said:

Interesting discovery that the culprit of the squares would be a TEXTURE_SIZE_EXP= setting in the .cfg, Glad it's all sorted.

Yeah have to say as irritating as these things can be it’s always a learning opportunity for next time!  Odd how this doesn’t cause issues anywhere else but I guess thats one of the many quirks of simming