Scenery Config editor V3 and V4 ?

[Michael Moe 494]

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

 

 

 

[Seat* 53]

https://sourceforge.net/p/fs-sceditor/discussion/1357803/thread/4ac46615/?limit=25#61a5/f0c2

 

Seems like a new version is underway

 

/Thomas

[F16_Driver 25]

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.

[jabloomf1230 2,445]

Thanks. I was wondering  up this utility.

[hawx2k 6]

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

[jetsmell 45]

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?

[F16_Driver 25]

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.

[JacquesBrel 639]

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.

[1st fltsimguy 466]

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.

[jabloomf1230 2,445]

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.

[newtie 533]

Where can I get this?

 

Mark

[jason99vmi 157]

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

[Alvega 2,119]

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?

[jabloomf1230 2,445]

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"?

[Alvega 2,119]

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.