29 minutes ago, Poppet said:

Nobody likes a show off Ed :)  

Ed,

Were talking about .exe programs that modify's .cfg files through an Add On control panel yes ? 

What about manually adding entries to .cfg files ?    

Our experience is that Notepad++ gets the coding correct based on the original file being edited.

23 minutes ago, MarkW said:

I posted this question/issue on the SimStarter forums and Pero is very confident that SimstarterNG is setup to use the correct format and will not cause this problem.

Thanks for raising this question. The big advantage of the SIMSTARTER NG platform is to support multi file Codecs.  It was always a bit difficult because nearly all platforms from FSX to P3Dv4 had their own files with different file Codecs.  NG can handle this because each file has its own codec definition. 

So SIMstarter NG works like a charm. My older freeware won't be able to work but I think most of the users have been switched to NG already.

But there are so many third party tools and installers out that I recommend making backups of all configuration files.

Maybe SIMconfigBackup  (FREEWARE) suites for you. Free download on my website.

http://aviation.pero-online.de

+1 for SimStarter....love that product

If Pete D. decides to not do FSUIPC5, SimStarter will the best way to do dissimilar control assignments based on aircraft.

 

19 hours ago, vgbaron said:

One of the changes in V4 is that LM changed the simulators CFG files to Unicode to support universal character sets in the future.

This will present problems to any program that modifies the sim cfg files. There is potential to destroy the formatting which will destroy such configuration files requiring a complete uninstall/flush/reinstall of P3Dv4.

Any product that does the following could potentially destroy your configuration files.   This includes things like:

• Add, edit or delete texture or autogen entries to TERRAIN.CFG
• Add, edit or delete scenery layers for you
• Edit simulator settings settings outside of the simulator (like traffic, graphics settings, etc)

Products that do this will need to be updated before use, so be aware.

We'll all be tempted to see if our favorite addon will work but just be aware that if does not have official word from the vendor that it is compatible with V4, you could run a risk of having to reinstall. So before any USER posts that xyz is compatible, please be sure that there are no hidden side effects.

Vic

Simple solution could be to take a backup of any CFG files before running said add-on installer?

Perhaps I'm missing a key point in this "molehill" of a thread. Unicode is not an encoding. Unicode can be mapped into a byte (UTF-8, which ingeniously matches the simpler 7 bit ASCII coding) or it can be mapped into a word or larger data structures. Is LM using something other than UTF-8? Is LM providing default cfg files with something other than the characters that are represented in ASCII? Seriously, I hope not.

They are now supporting extended character sets because the world uses them.

On 5/25/2017 at 4:43 AM, Poppet said:

What about manually adding entries to .cfg files ?  

Depends on what editor you use, a more modern good editor will not change the format.  An older editor might.  I use UltraEdit (IDM) as it will indicate format and variants within a specification.

Cheers, Rob.

On 5/25/2017 at 2:02 PM, jabloomf1230 said:

Is LM providing default cfg files with something other than the characters that are represented in ASCII? Seriously, I hope not.

Multi-language support is the reason for UTF-16 ... that and it's the native format for .NET.  For example the current Orbx FTX Central will change the scenery.cfg from UTF-16 to ANSI Latin I or more accurately Windows-1252 (locale associate to my OS).  P3D V4 will still read and write to the converted Windows-1252 scenery.cfg.

I don't know if Orbx (or other 3rd party) plan to change all their installers and/or configuration tools to support UTF-16 ... wait and see.

UTF-16 is a good idea since I'm sure LM reach out to international support based on what I saw at ITEC 2017 held in Europe. 

Cheers, Rob.

UTF-16 is the default format for inline memory strings in .NET. UTF-8 is the default  format for saving files in .NET.

On 25/05/2017 at 5:21 AM, jabloomf1230 said:

Vic,

It is not the format of the text file but rather how each individual character  is mapped into an 8 bit byte. ASCII uses only 7 bits of each byte to map all its characters. Unicode uses the 8th bit to map a large number of additional  characters, most of which are hardly ever used in written English. Hence, most often the two character sets are interchangeable. However my guess is that LM  wants P3d to be suitable for other languages  that use special characters  qualified  with accents like umlaut, for example.

Jay

 

 

 

On 25/05/2017 at 4:22 AM, vgbaron said:

As I understand it, the problem could come if the cfg file format is not maintained by the program making the edits. This could make it unreadable by P3D which could then result in either a reinstall or deleting all created content and letting P3D rebuild them. This would initially result in addons being disabled.

Until there is clarification from LM I would still suggest being aware and making an informed decision.

Vic

theres some very clever people on here.....

i'm not one of them..

 

 steve

I've been using notepad as per previous to make any changes to the P3D & aircraft cfg files & can report that doing so doesn't seem to have caused any issues to date. So at least that still seems to work OK. Doing it with an external .exe could be another kettle of fish as reported I suppose.

10 minutes ago, Rossco said:

I've been using notepad as per previous to make any changes to the P3D & aircraft cfg files & can report that doing so doesn't seem to have caused any issues to date. So at least that still seems to work OK. Doing it with an external .exe could be another kettle of fish as reported I suppose.

Is this on V4? I know Notepad++ works but regular notepad........ P3D V3 doesn't have a problem.

Vic

Yes Vic.

I have added the Affinity Mask lines in main cfg to test & also turned off optimized parts to test the XP Lear25 using regular notepad. Have also played around with the flight model settings for the F16 with no apparent issues.

Thanx Ross - good to know!

Vic

There will be no problems until somebody decides to use funny characters (like äöüß) in the scenery titles and paths.

So it easy to say "I never had problems".

If the file contains anything besides plain ASCII you better take care of the encoding.

People are creative and will add special characters. Think about paths containing Chinese characters.

A warning about Notepad++: White it is a great editor (I use it a lot when I have to dive the Windows swamp) it does not detect the encoding properly when loading files. You better set it manually after loading.

Alex