The scenery config editor opens up your working scenery.cfg and saves it as your scenery.cfg.  There is no other config made. 

 

 

 

i have 257 areas (C:\user\me\appdata\roaming\microsoft\FSX new scenery.cfg = 257 areas)

 

Don't worry about that.  That's not where your "working" scenery.cfg is located.  That folder holds a default scenery.cfg when you first install fsx and it is suppose to be left alone and not deleted.  I suppose you can edit it all you want as FSX does not read it at all when FSX is loaded.  The working scenery.cfg is located in a hidden folder in C:\Program Data\Microsoft\FSX.  That's the one that the scenery config editor should be reading (but maybe you changed the location to show it's located in the User folder?).

 

The scenery config editor will automatically save any changes you made to the working scenery.cfg.

 

Best regards,

Jim, i read that one now from C:\Program Data\Microsoft\FSX, and from area 1 to area 239, area number and layer number are the same. (area 1 layer 1 etc) but from after area 239, that's area 241 with layer 240 and it continues up to the last one. area 242 layer 241 etc) Could it cause a problem?  Maybe i have stupid question but i'm really not confortable with computer but i keep learning.....thanks again

 

 

(area 1 layer 1 etc) but from after area 239, that's area 241 with layer 240 and it continues up to the last one. area 242 layer 241 etc) Could it cause a problem?

 

No, unless it gives you an area.  FSX can operate with different areas/layers numbers.  But, to tidy things up, you should keep them nice and neat (developers get very upset when I say things like this).  So keep them in numerical order....Area 239/Layer 230, Area240/Layer240 etc.  When you restart FSX, your terrain.cfg will see the changes and that's the important file.  Back in the FS9 days, having layers and areas out of sequence created problems occasionally and we then recommended they fix their corrupted scenery.cfg.  FSX was programmed to handle changes.

 

Best regards,

I was pretty busy last few weeks. Didn't have time to work on my CTD problem. But i've noted that i have only CTD when i'm flying over an ORBX region and not if i'm flying over FTX Global.  I can fly hours over FTX Global without any CTD but when i'm flying over NA, Australia, England or other ones, i almost have a CTD each flight. Yesterday, i departed from Vancouver to Calgary. Being leaving PNW toward  FTX Global no CDT, but if i do the opposite (Calgary/Vancouver) or often Nanaimo, i got a CTD and same happens over the other ORBX regions.Hope it could help you. ( i don,t know if it is the same, but message i have it's that FSX does not respond)

 

Thank you and best regards

Orbx has suggested FSX settings for their software. Remember, you MUST enable/disable Orbx scenery through FTX Central. Any other way of disabling/enabling will cause crashes as you have completely confused FSX. This is most likely the reason you are getting crashes with ORBX but not with FTX Global (which is really a default scenery replacement program right?). Post #13 reveals you messed around with the FTX Central scenery in the FSX Scenery.cfg. You just cannot do that. I know I did it once and paid the price of hours of repairs. I think I now have it resolved. So, uninstall all of your Orbx scenery, run fsx at least once, then reinstall the Orbx scenery.

 

If you are using the Scenery Config Editor, make sure you have loaded the FSX scenery.cfg and NOT the FSX New Scenery.cfg.

 

Best regards,

Thanks Jim. A lot of works ahead...OMG!.

 

Best regards

Orbx has suggested FSX settings for their software. Remember, you MUST enable/disable Orbx scenery through FTX Central. Any other way of disabling/enabling will cause crashes as you have completely confused FSX. This is most likely the reason you are getting crashes with ORBX but not with FTX Global (which is really a default scenery replacement program right?). Post #13 reveals you messed around with the FTX Central scenery in the FSX Scenery.cfg. You just cannot do that. I know I did it once and paid the price of hours of repairs. I think I now have it resolved. So, uninstall all of your Orbx scenery, run fsx at least once, then reinstall the Orbx scenery.

 

If you are using the Scenery Config Editor, make sure you have loaded the FSX scenery.cfg and NOT the FSX New Scenery.cfg.

 

Best regards,

Hello Jim, i'm preparing to uninstall and reinstall all ORBX products. You say "if you are using Scenery Config Editor (i am), make sure you have loaded FSX scenery.cfg and not FSX New Scenery.cfg" How i can do that. Thanks again. Best regards.

 

 

make sure you have loaded FSX scenery.cfg and not FSX New Scenery.cfg" How i can do that.

 

Look at the very top of the scenery config editor and it will show you the scenery.cfg you have open and are editing.  If it does not show c:\ProgramData\Microsoft\FSX\scenery.cfg, then click on File > Open default scenery file.  This will open up the current working scenery.cfg.  If you save a NewScenery.cfg, you will note that the changes you made were not made to the scenery.cfg when you start up FSX and open up the Scenery Library.

 

Best regards,

Thank you very much Jim. It's so easy when you know....Ok now i'm going to uninstall all ORBX products and reinstall them. Hope it will solve that CTD problem.

It scares me.....

Best regards.

Hello Jim,

 

I'm reinstalling all ORBX products (i still have the airports to install) but so far i have no more CTD. I cross my fingers. Best regards.

In the end, that's probably the best option.  Hope it fixes your problem(s).

 

Best regards,