Jump to content

PAVD - Possible library order issue?


Recommended Posts

Hi, I have separated this out from another post about dark tiles turning light as that part has been resolved and it's probably easier to deal with this separately.

I am seeing pronounced jagged silt streams in my sim, with some unnaturally straight edges in some areas, which didn't look so pronounced when I first got the area last year or in the Orbx website screenshots, but also I have a baked in pier that appears (pardon the pun) when Southern Alaska is running.  My scenery order however clearly has PAVD way above SA which in turn is above OPen LC.  Any ideas?

Please ignore the lighter and darker difference on the silt below.....this was caused by a different issue which has now been solved.

 

Isha4Ps.jpg

jqa2Q9f.jpg

9X8GmL6.jpg

VfGGOIj.jpg

H7uHUfx.jpg

Ir7eBD9.jpg

MbGSK7l.jpg

rMMWbM9.jpg

Link to comment
Share on other sites

I reeeeeemember that we had a similar issue once but damn i can't remember what the problem was. Think it was for FSX as well.

So ok :

 

SAK does not have any imagery for the Valdez bay and unless you are using another scenery (couldnt spot one) that is for the area then it should be the PAVD scenery that is not functioning.

 

The imagery file has the water masked and the harbour thingy should not be visible:

1056028483_TmfViewer--Valdez_60cm_B3.bgl2019-12-1308_03_35.thumb.png.c75c3746f40aec64bbe0bedf6deb07ab.png

 

And this is of course how it is supposed to look (just checked so nothing was broken on my end haha):

1621967279_Prepar3D2019-12-1307-59-49.thumb.png.55dda2cbfd7571c73e30a9c4b489515e.png

 

So yeah reinstall / verify files for SAK and PAVD and get back to us!

Link to comment
Share on other sites

4 hours ago, Marcus Nyberg said:

I reeeeeemember that we had a similar issue once but damn i can't remember what the problem was. Think it was for FSX as well.

So ok :

 

SAK does not have any imagery for the Valdez bay and unless you are using another scenery (couldnt spot one) that is for the area then it should be the PAVD scenery that is not functioning.

 

The imagery file has the water masked and the harbour thingy should not be visible:

1056028483_TmfViewer--Valdez_60cm_B3.bgl2019-12-1308_03_35.thumb.png.c75c3746f40aec64bbe0bedf6deb07ab.png

 

And this is of course how it is supposed to look (just checked so nothing was broken on my end haha):

1621967279_Prepar3D2019-12-1307-59-49.thumb.png.55dda2cbfd7571c73e30a9c4b489515e.png

 

So yeah reinstall / verify files for SAK and PAVD and get back to us!

really odd!  I managed to clear the issue the other day by unchecking SAK in my scenery library but obviously not what I want to do really.

The only scenery I have running that may impact this area is all ORBX and would be Global Base, Vector, OpenLC NA, SAK and PAVD.  I also have pilots mesh but that shouldn't be an issue and whether it is 'on' or 'off' it doesn't change it.

 

Link to comment
Share on other sites

Hey guys,

 

Ok, so I've got some good news regarding the issue. Well, I also have bad news as I still don't know why this is happening now (as it didnt use to happen) BUT I got a solution at least.

So, yes FTX SAK includes some imagery for Valdez as well, I had totally forgotten about that. Your issue seems to be that that imagery for some reason clashes with the PAVD imagery, which should not happen.

I think the absolute easiest solution at this point is simply to deactivate the imagery that comes with the FTX SAK package.

You will find two files in (if installed with the library feature in ORBX Central, otherwise you'll find it ORBX/FTX_NA/  in the P3D folder):

ORBX\P3Dv4\p3dv4\NA Southern Alaska\ORBX\FTX_NA\FTX_NA_SAK06_CVX\scenery

 

Files:

2_orthoimage_AK_USGS2007_Valdez_harbor_60cm.BGL

2_orthoimage_AK_USGS2007_Valdez_refinery_60cm.BGL

 

Change the name from .bgl to .OFF, or move the files to a back-up folder outside the P3D system, or remove them if you like living on the edge (you can always verify files later on and they should be installed again otherwise).

 

I'll see where we went wrong and if we can push a minor patch for that so it works again!

 

Sooo anway:

 

With the files active:

429632062_Prepar3D2019-12-1710-11-44.thumb.png.01345987fe61c1285b74cb184c049e3f.png

 

With the files removed:

 

1607689363_Prepar3D2019-12-1710-13-03.thumb.png.96de38cccdd5fc44676912afb8f91785.png

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...