I copy the scenery.cfg and then install my ORBX product.

 

I then delete the scenery.cfg and rename my copy back to original and then add my ORBX stuff manually.

 

Works a treat.

 

Dave

Blimey what a messup.  Is that an issue with FTX Central, or Scenery config editor then?

Scenery Configurator: Best piece of software / advice for avoiding OOM messages during long haul flights in FSX!

Along with Process Explorer open on a second monitor it is easy to keep an eye on VAS usage. Judicious use of the sliders (nothing maxxed to the right!) and FSX long hauls, even with complex and code-heavy aircraft such as the PMDG T7, are now easily achievable and those include real Wx injection (ASN), OpusFSX's nice camera system, EFB or EFASS plus company ACARS, all running off one medium spec PC (i5 - 3570K) with 8GB RAM and a GFX670. Nothing fancy.

 

My grateful thanks to all who dedicated sizeable chunks of their free time exploring and testing the limits of FSX and their subsequent suggestions. Hats off, guys...good job!  :good:

The Scenery Config Editor does not work with FTX Central very well and I would not recommend anyone try to disable/enable FTX scenery using the SCE. I learned that myself the hard way and had a lot of scenery corruption. I finally was able to get FTX Central working properly again. It's just as easy to enable/disable FTX scenery via their FTX Central utility. I would not use Groups. I tried that once and it does not always work. Make sure you look up in the title bar and the scenery.cfg is being edited and not the New Scenery.cfg. If things do get corrupted, delete the facilities/scenery indexes folders and let them be rebuilt when you restart FSX. If I'm flying over FTX scenery, I'll enable it in the FTX Central and then go into the Scenery Config Editor and make sure any photoscenery I won't be using is disabled.

 

The SCE works great with P3DV2 too.

 

Best regards,

 

 

I'll enable it in the FTX Central and then go into the Scenery Config Editor and make sure any photoscenery I won't be using is disabled.

Jim, do you mean if your flying in NA, example PNW, do you disable Alaska for example in SCE ?

Jim, do you mean if your flying in NA, example PNW, do you disable Alaska for example in SCE ?

Yes. I also have MSE V2 Washington State so that's disabled too and photoscenery will trump out some of the FTX/Orbx stuff. In any case, all photoscenery that you will not be flying over during a session should be disabled as it is eating up your VAS even though you are not using it. That's one of the reasons I highly recommend SCE as it makes it very easy to enable/disable stuff (except Orbx/FTX). You can disable Orbx/FTX scenery in the SCE or Scenery Library but you will eventually have problems as FTX Central thinks all of them are enabled.

 

Best regards,

I have all of the ORBX scenery installed i ignore central altogether , i load a disused scenery config file before adding scenery from Orbx or anybody else as they really do mess with your lay out in that configuration file.

Using the editor a brilliant piece of freeware i manually place all relevant scenery files  into small but usable config files for the flying i expect to do over that area. This eliminates long load times and all the mentioned problems.

My usable scenery is not in the default FSX  folder but copied over to faster drives so the editor points all my scenery to the relevant drives where installed.  Also you will find FSX will be more responsive this way and by the way you can get rid if some of the default scenery files such as Africa Europe USA  as they only show poor modelling of the relevant cities

just keep the base stuff and default as ORBX overwrites certain scenery folders mainly texture if using Global and vectoring . This way you can enjoy custom scenery config files for photo or autogen and custom fsx config file for that part of the world/scenery you want to fly over. I obtain between 38 fps and 55 fps on an SLI-AA GTX 480,s set up . sliders maxed out except for the two scenery sliders set at very dense .

There's new version of the Scenery Config Editor.  It's now at version 1.1.2 and released on 30 Sep.  Might fix some of the problems with setting up groups of scenery to load for a flight.

 

Best regards,

Jim

Jim,

I think that should be v1.1.3 - v1.1.2 has been around for a few years. as per web site

Last Published: 2014-10-30 20:10  | Version: 1.1.3

 

steve

Jim,

I think that should be v1.1.3 - v1.1.2 has been around for a few years. as per web site

Last Published: 2014-10-30 20:10  | Version: 1.1.3

 

steve

Thanks for that Steve. They just updated it on 1 Nov 2014.

 

Best regards,

Scenery Config Editor location.

Have W7 64 bit, C:/FS/Microsoft flight simulator FSX/Orbx FTX Global file folder, Program files, Program files(X86) folders.

Where should the Scenery Configuration Editor v1.1.3 tool be installed ?

John

 

 

Where should the Scenery Configuration Editor v1.1.3 tool be installed ?

 

You can install it anywhere on your computer.  It will find your scenery.cfg by looking in the system registry.

 

Best regards,

Aside from FTX, one of the other side effects of using this is how it plays with AES. When you add/remove scenery from the scenery, AES thinks the scenery is missing. When you reenable the scenery, you have to reactivate the scenery in the cfg, start FSX, shut it down and reactivate in AES help. It is kind of a pain but not a show stopper. 

It has worked well for me in both FSX and FS9, was wondering if it will work with FSX-SE?

It has worked well for me in both FSX and FS9, was wondering if it will work with FSX-SE?

I use it with my stand-alone installation of FSX-SE - works great!

Had no idea they updated in November.  Thought the app was long since dead.  Nice to see it's still up and kickin'.   Did they ever find a work-around so one can use custom groups while also using ORBX?  Orbx would always delete my custom groups from what I understand.