Michael Moe

Scenery Config editor V3 and V4 ?

Recommended Posts

Seems like a nightmare since its not compatibel with ORBX and since V4 we now have different entrys outside scenery.cfg.

 

Anyone have suggestions or  should we just think none VAS issue with V4? In the meentime we have to load all of them with V3 i guess

 

Thanks

Michael Moe

 

 

 

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

The latest build seems to work just fine when I tested it now, so a fully compatible release version shouldn't be to far off.

  • Upvote 1

Share this post


Link to post

Thanks. I was wondering  up this utility.

  • Upvote 1

Share this post


Link to post

Interesting. I just tried the 1.1.8 SNAPSHOT version and I got the same error as before ("Can't open the file due to a structural error"). I only even started getting these error messages after I had upgraded and installed all the FTX updates in v4. 

So I'm wondering if @F16_Driver had used it after the FTX upgrades?

Thanks,

Jan

Share this post


Link to post

I had FSX SE, did a clean install with Prepared V4. Installed Scenery Configurator 1.17. When I opened it up every scenery has a path that doesn't exist. Maybe it's not ready for the new Prepared. How can I fix this problem?

Share this post


Link to post

I have used it after FTX being installed, still no errors with the snapshot I am using. Try re-downloading it again. The first snapshot I tried didn't work correctly.

Share this post


Link to post

With the latest snapshot I'm getting the "structural error" message whenever FTX Central has made changes to the scenery.cfg. But not when P3D v4 has made changes.

As far as I can tell, FTX Central saves the scenery.cfg in UTF-16 text format, whereas P3D v4 uses UTF-8. The latest snapshot of 1.1.8 can handle UTF-8 but not UTF-16.

So whenever FTX Central has made changes to scenery.cfg, you can remedy the problem by starting P3D and opening up the Scenery Library, and just unset and set the checkmark for some random entry, which causes P3D to save the scenery.cfg in the correct UTF-8 format which Scenery Config Editor can read. Or you can open scenery.cfg in a text editor like Notepad++ which can convert text encoding formats like UTF-8 and UTF-16 and others.

Hopefully ORBX fixes FTX Central soon so this won't be necessary.

Share this post


Link to post

I'm not the techical guy here but the new scenery.cfg is coded differently than the old cfg, and that configurator does not read it correctly, that software application needs to be rewritten for P3D v4 I believe.

Share this post


Link to post

The version 1.18 Snapshot works properly  with P3d V4 and all previous versions and sims. Make sure that you set the correct default  sim in the app preferences.

Share this post


Link to post

Where can I get this?

 

Mark

Share this post


Link to post

SimStarter NG can do this as well.   A new version is underway over at Aerosoft.  

Share this post


Link to post

I get "Path does not exist" and a red triangle on all my scenery areas, but they are all in the list. It says 130 areas have errors, why is that?

Share this post


Link to post
59 minutes ago, Alvega said:

I get "Path does not exist" and a red triangle on all my scenery areas, but they are all in the list. It says 130 areas have errors, why is that?

Did you set the default sim correctly? And then "open default"?

  • Upvote 2

Share this post


Link to post
4 minutes ago, jabloomf1230 said:

Did you set the default sim correctly? And then "open default"?

 

As i pressed "Find directory in registry" i thought i didn't have to fill the flight simulator directory but it seems like i was wrong. I now filled that and it solved the problem.

Thanks.

 

  • Upvote 1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now