Archived

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

GodAtum

Corrupt scenery around plane

Recommended Posts

Hi all,

 

I'm flying atm and have corrupt scenery which follows me as I fly. The ground is all fuzzy and black. Outside my route its OK.

 

8853752900_fbd6b66882_c.jpg
Untitled by GodAtum, on Flickr

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I would disable all the addon scenery in your Scenery Library then reenable them 3-4 at a time until you find the scenery that is causing the problem.  Once found, uninstall/reinstall.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I'm not sure whether this will help, but if you're using UTX, you could try running the configuration tool. It doesn't really look like the usual issue that can be fixed by that, though.

Share this post


Link to post
Share on other sites

I would disable all the addon scenery in your Scenery Library then reenable them 3-4 at a time until you find the scenery that is causing the problem.  Once found, uninstall/reinstall.

 

Best regards,

Jim

 

Unfotunately that hasnt worked. here is my scenery.cfg from C:\ProgramData\Microsoft\FSX

 

http://sdrv.ms/13cl3zt

Share this post


Link to post
Share on other sites

Your scenery config is corrupted.  I doubt it will fix this problem but your scenery.cfg is corrupt.  The [Area.xxx] should match the Layer.  For instance [Area.166] the Layer=166 and not 128.  One solution is to download and install Scenery Config Editor 1.1 which looks for errors and tells you where they are if found.  It can also fix Areas/Layers.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Your scenery config is corrupted.  I doubt it will fix this problem but your scenery.cfg is corrupt.  The [Area.xxx] should match the Layer.  For instance [Area.166] the Layer=166 and not 128.  One solution is to download and install Scenery Config Editor 1.1 which looks for errors and tells you where they are if found.  It can also fix Areas/Layers.

 

Best regards,

Jim

 

Hi the Scenery Config Editor says there are no errors?

Share this post


Link to post
Share on other sites

Okay.  Did you click on Actions and click on Reset Area and Layer numbers? 

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Okay.  Did you click on Actions and click on Reset Area and Layer numbers? 

 

Best regards,

Jim

 

Ah thanks! That fixed the numbers but not the original issue unfortunately.

Share this post


Link to post
Share on other sites

The [Area.xxx] should match the Layer. For instance [Area.166] the Layer=166 and not 128.

That's not correct. The Area entry is added sequentially when something is placed into the Scenery Library. The Layer entry is for when something is moved around in the Scenery Library and gives priority to that entry.

 

If it were a requirement that those two identifiers match, I'm pretty sure Microsoft would have hard-coded that into the game.

 

 

Back to the visual issues, does the OP happen to have an add on, regional package for England. You know, the one that messes with the rest of Europe?

Share this post


Link to post
Share on other sites

 

 


But Scenery Config Editor says that Scenery\1107, Scenery\1106 etc is "title is non-unique".

 

Suspect that means you have two titles with the same name?

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

That's not correct. The Area entry is added sequentially when something is placed into the Scenery Library. The Layer entry is for when something is moved around in the Scenery Library and gives priority to that entry.

 

Thanks Meshman.  You are the expert in this area and I'm not.  I know this was a requirement in FS9.  I was just looking at Microsoft's description of the scenery.cfg file and they state the Layer is "typically" equal to the Area.nnn -http://msdn.microsoft.com/en-us/library/cc526966.aspx .  I know it will not cause a scenery program or a problem with FSX if they are not equal; however, I like to keep things tidied up a bit.  It seems to me that if a layer is duplicated (and I have seen this), there will be some problems encountered somewhere in FSX or in the terrain.cfg.  Thanks for your help for the OP!

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thank you both for your help its greatly appriciated :). Apperently the scenery titles where missing so ive added them!

Share this post


Link to post
Share on other sites

 

 


The [Area.xxx] should match the Layer. For instance [Area.166] the Layer=166 and not 128.


No, this is wrong.

The area is just a unique number for each scenery layer, with no function. It only indicates when that scenery was added (larger means later).

The layer number, is the position in the scenery library, 1 is the lowest, the larger one is the highest.

So they do not have to match - in fact, they rarely do, as their function is completely irrelevant from each-other.

Share this post


Link to post
Share on other sites

 

 


So they do not have to match - in fact, they rarely do, as their function is completely irrelevant from each-other.

 

I hope you were able to read Post #12.  I think Microsoft refutes your assumption.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I think Microsoft refutes your assumption.

Yeah, 'cause the SDK is never wrong.

 

Truth is if those numbers were required to be the same there would be no need to have both of them.

 

Yes, they will be the same if, and this is a big if, all you ever do is add scenery areas without ever deleting any or changing any priority in the Scenery Library.

 

If you simply add areas and always leave them at the top of the Scenery Library, those 2 entries will be equal.

 

Once you delete an area or change the priority of an area in the Scenery Library they will no longer be equal.

 

Again, if you have 2 entries that always have to be the same, why have 2?

 

regards,

Joe

Share this post


Link to post
Share on other sites

 

 


Yeah, 'cause the SDK is never wrong.

 

It doesn't say they have to be the same.  It's just "typical" they are the same.  When you got your brand new FSX installed, the scenery.cfg has the area/layers the same for all default scenery.  It's not going to mess things up if they are not the same as we have all proven that.  I'm just saying I try to keep mine the same as much as possible.  I think we are all right in what we are saying.  I made the lousy mistake of calling the OP's scenery.cfg "corrupt".  That's what I call things when they are not as neat as mine.  As I stated in my post - "I doubt it will fix this problem" - I was meaning that it is okay to have different areas/layers numbers. 

 

I really apologize for the confusion I have caused.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I hope you were able to read Post #12.  I think Microsoft refutes your assumption.

 

 

Do you read what others write, before you write?

 

Microsoft agrees with me, because I wrote above the same things, just with different words.

Share this post


Link to post
Share on other sites

Do you read what others write, before you write?

 

Microsoft agrees with me, because I wrote above the same things, just with different words.

Okay, cool... I apologize since you appear to be very upset.  I didn't mean to do that.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I think while it's not necessary to have matching Areas/Layers in the Scenery.cfg, Jim's advise about Scenery Config Editor 1.1 being helpful is spot on. Since I have many different Scenery.cfg files that I use for my work, I see a lot of issues that come up with FSX that never seemed to appear with FS9. Missing Area and Layers, gaps between the numbering of each. So having a tool that can scan and correct these problems is a good thing.

 

Then there are the many FSX.cfg files that I have for working on things... At times, it's hard to keep all the files synch'ed up!

Share this post


Link to post
Share on other sites