Anyone know what this billboard is for, right next to the approach end of runway 14 at MYNN? It must be 100 feet high at least.  

 

 

Edited October 15, 20223 yr by Bobsk8

This is an old one... do not recall the fix.. start searching the forum for Billboard!  Or MYNN.

 

Edited October 15, 20223 yr by Bert Pieke

Yes, i had that too. It's caused by one (or more of your sceneries. This thread has the explanation and the cure (using Total Commander):

 

It would be nice if the dev could just fix this.  It's a really good scenery.

2 hours ago, Bobsk8 said:

Anyone know what this billboard is for, right next to the approach end of runway 14 at MYNN? It must be 100 feet high at least.  

 

 

One of the Asobo samples contains objects placed at Nassau. Developers used to clone those samples, without deleting Asobo stuff..I'm quite sure that near that giant sign there is a little streetlight lamp post 

To know the offending package causing the issue, in the Dev Mode you need to activate debug model lods, then display package name, near the sign will appear the name of the offending package 🤓

13 minutes ago, Jeff Nielsen said:

It would be nice if the dev could just fix this.  It's a really good scenery.

Read the threads in the links we posted. He is not using any scenery, as far as I can tell. This happens with default MYNN. The devs of the other sceneries causing this problem in MYNN are the ones who need to fix their sceneries, then MYNN will be ok.

Edited October 15, 20223 yr by Alvega

2 hours ago, mamu82 said:

To know the offending package causing the issue, in the Dev Mode you need to activate debug model lods, then display package name, near the sign will appear the name of the offending package 🤓

Hi, do I need to physically (in the sim) be near the sign when activating debug mode? Also, is there a certain package name that I am looking for or will something be highlighted as conflicting to let me know?

Yes, I already checked, and this is default scenery for MYNN.

2 hours ago, mamu82 said:

One of the Asobo samples contains objects placed at Nassau. Developers used to clone those samples, without deleting Asobo stuff..I'm quite sure that near that giant sign there is a little streetlight lamp post 

To know the offending package causing the issue, in the Dev Mode you need to activate debug model lods, then display package name, near the sign will appear the name of the offending package 🤓

I'm guessing using Dev Mode, and exclusion/polygon won't remove the sign?

I don't see the sign in my default setup, but I do not have a lot of World Updates installed other than USA and Canada ATM (and a couple others). Most likely what happened is the object got placed by accident and the coordinates scrambled and it ended up somewhere it shouldn't be.
 

Edited October 15, 20223 yr by Alpine Scenery

9 minutes ago, Alpine Scenery said:

I do not have a lot of World Updates installed

Some threads mention as a culprit an object from Barra Airport included in World Update III: UK & Ireland.

But anyway there are lots of other freeware & payware airports causing conflict/anomaly in MYNN airport.

33 minutes ago, Alpine Scenery said:

Most likely what happened is the object got placed by accident and the coordinates scrambled and it ended up somewhere it shouldn't be.

That is not what is being documented above if you read the links... it is an ordinary object with a name conflict with some undetermined addon airport data. The coordinates are fine, but the object type is wrong.

38 minutes ago, Alpine Scenery said:

I don't see the sign in my default setup, but I do not have a lot of World Updates installed other than USA and Canada ATM (and a couple others). Most likely what happened is the object got placed by accident and the coordinates scrambled and it ended up somewhere it shouldn't be.
 

Nope, what happened is well described by Virtuali in the link I posted before, or in this one: http://www.fsdreamteam.com/forum/index.php/topic,25562.msg168146.html#msg168146

7 minutes ago, Bert Pieke said:

That is not what is being documented above if you read the links... it is an ordinary object with a name conflict with some undetermined addon airport data. The coordinates are fine, but the object type is wrong.

I didn't read the links, but thanks for letting me know...

For anyone having this problem and wanting to fix it, you just need to search for the GUID number in Total Commander (Commands tab > Search) and it will show what is the scenery (or sceneries) causing the problem. In the "Search In" field insert the path to your community folder.

Just look at the image in this post and you won't need to read the full threads on the links we posted before. In the "Search In" field insert the path to your community folder.

 

 

Edited October 15, 20223 yr by Alvega