I have just got P3D V4 on my pc and in my scenery.cfg ftx creates a Area.000 line with openlc and it causes the game loading to stop ay 6%. When i remove it the game starts working but then when I reload ftx central it will automatically create that line again. I installed scenery configrator which said theres a duplicate index and when i fix it using the scenry config tool p3d will not load the orbx scenery eventhough it shows in the scenery library in p3d. I also installed  free mesh x but i dont know what order to put it in because when i add them and put the patch file at the top it says that there is something wrong with Scenery order and then when it rebuilds it all my free mesh x disappears! 

I would contact OBRX directly (in their forums) for support for this.

Best wishes.

 

I have found that manually adding/deleting anything in the P3D scenery.cfg using the SceneryConfigEditor will corrupt the scenery.cfg as it has to be in the proper format.  I would rename the scenery.cfg to scenery.cfg.off, restart P3D and let it rebuild.  Close P3D and try again to use FTX Central.  Rebuilding the scenery.cfg is the only way I have found to code the config properly in the format P3DV4 likes (UTF-8).

 

4 minutes ago, Jim Young said:

I have found that manually adding/deleting anything in the P3D scenery.cfg using the SceneryConfigEditor will corrupt the scenery.cfg as it has to be in the proper format.  I would rename the scenery.cfg to scenery.cfg.off, restart P3D and let it rebuild.  Close P3D and try again to use FTX Central.  Rebuilding the scenery.cfg is the only way I have found to code the config properly in the format P3DV4 likes (UTF-8).

 

SCE is V4 compatible. 

I can add , delete or modify the library and no issues...

10 minutes ago, Jim Young said:

I have found that manually adding/deleting anything in the P3D scenery.cfg using the SceneryConfigEditor will corrupt the scenery.cfg as it has to be in the proper format.  I would rename the scenery.cfg to scenery.cfg.off, restart P3D and let it rebuild.  Close P3D and try again to use FTX Central.  Rebuilding the scenery.cfg is the only way I have found to code the config properly in the format P3DV4 likes (UTF-8).

 

utf-8 is for xml

ucs2-le is for cfg files

PMDG have it wrong too, all their cfg files are in utf-8 and the ops center corrupts your cfg if you change to the correct encoding

It has messed up my P3D.cfg everytime I used it.  If you go to Lorby_Si's Organizer program, he has button to check for encoding problems.  My P3D.cfg has shown up every time I opened it in SCE and the only way I could fix it was via what I stated above.  Certainly, your config will work occasionally as it did for me.  But, if you have startup problems or scenery not showing, then suspect the encoding issues. 

I purchased EditPad Pro to replace what I had been using (Notepad++ free but tricky to use with UTF-16, and UltraEdit which just got too expensive).  EditPad is great, didn't cost much, and easily handles various code formats and pages.

1 hour ago, Jim Young said:

It has messed up my P3D.cfg everytime I used it.  If you go to Lorby_Si's Organizer program, he has button to check for encoding problems.  My P3D.cfg has shown up every time I opened it in SCE and the only way I could fix it was via what I stated above.  Certainly, your config will work occasionally as it did for me.  But, if you have startup problems or scenery not showing, then suspect the encoding issues. 

Which version of SCE do you use Jim ? I use version 1.1.9 ..

https://sourceforge.net/projects/fs-sceditor/files/

I am using the latest and greatest.  Have since P3DV4 came out.  In fact, I'm the one who informed everyone about this update to SCE as I wanted to be sure the latest was in the AVSIM FSX Configuration Guide.  I do not know for sure it is the fault of SCE, just that I got these problems when I was adding or editing the P3D.cfg.  I have since gone to Lorby_Si's Addon Organizer and have no need for the P3D.cfg anymore (other than to add Orbx or UTX2 entries).  I do know that when DD installed Washington X (first version), it corrupted my P3D.cfg and you couldn't even read it.  Many others complained too and DD updated the program for compatibility with P3DV4 (where Addon.xml's were used instead).  I do not want to blame the SCE as it is a great tool for this hobby but, since I don't need it for P3D anymore, I no longer use it to edit my P3D.cfg.  Could it be the Java script? 

Hi,

Since ensuring Prepar3D.cfg, scenery.cfg and terrain.cfg are ALL encoded as UCS-2 LE BOM it has been plain sailing here without any issues. The sim likes it, FTX Central 3 likes it and my virtual world is a much happier place

Notepad++ is your friend.

Mike

Doesn't LE mean there's no BOM? Doesn't Notepad Win10 do it OK? Check it's set to Unicode by doing a 'Save As' and the dropdown list at the bottom shows Unicode, if not then the file is already altered.