Hello,

 

I'm just testing SimLauncherX in combination with P3Dv2, and I think I've found a problem when editing the scenery.cfg of P3Dv2 in SimLauncherX.

I have changed my scenery.cfg (deactivated an area) by using SimLauncherX. Then I started P3Dv2, everything looked fine. But I have got an error if I want to open the scenery library within P3Dv2. The simulator wasn't able to read all areas of the scenery.cfg.

 

So I've compared the original P3Dv2 and the SLX-modified scenery.cfg.

 

Here is an entry of the original P3Dv2-scenery.cfg:

 

[Area.001]
Title=Default Terrain
Texture_ID=1
Local=Scenery\World
Layer=1
Active=TRUE
Required=TRUE

 

And now the same entry after the modification by SimLauncherX:

 

[Area.001]
Title = Default Terrain
Texture_ID = 1
Local = Scenery\World
Layer = 1
Active = TRUE
Required = TRUE

 

After deleting the spaces before and behind the values P3Dv2 started with an error at [Area002]. So it seems linke P3Dv2 has a problem with reading the scenery.cfg if there is a space before and behind the equal sign.

 

It would be great if SLX would not change the format of the scenery.cfg.

 

Patric

Hi Patric,

 

I will have a look at it, but it would really surprise me if this was an issue: the same .ini file format is used for lots of other files (prepar3d.cfg, aircraft.cfg etc.).

 

thanks, Maarten

Hello Maarten,

 

thanks for looking into this. BTW, I use P3Dv2.4.

 

Patric

Hi Patric,

 

I can confirm this is indeed an issue. It will be fixed in the next version. I do however believe this is a bug in Prepar3D, because the simulator itself apparently has no problems reading the scenery.cfg file or any other .cfg file with spaces around the equals signs. Although there's no formal specification of the ini-file format, every implementation I know of ignores whitespace around keys and values.

 

Thanks for pointing this out,

 

Maarten

Hello Maarten,

 

thanks for the really quick support. So I will looking forward to the next version.

 

Patric