First of all- thanks for the great sceneries (I have Reunion and Bremen so far)!
However there is a couple of things that need your attention. In Reunion scenery the configurator doesn't provide an option of removing the static jetways- I had to do it manually in the scenery folder.
Also the manual states the compatibility with FSGlobal, which is not the case- FS Global Ultimate 2020 causes some of the Reunion autogen buildings float in the air.
Finally the contents of add-on.xml files in these two sceneries are not recognized by P3Dv4.5, so that the sceneries are not activated in the sim. I had to change the full paths like <Path>C:\Users\Сергей\Documents\Prepar3D v4 Add-ons\FSDG-Reunion\FSDG-Reunion</Path> for the scenery to <Path>FSDG-Reunion</Path> (with similat changes to Effects, Simobjects and autogen Texture) to make it work. Maybe it's related to a Cyrillic part of the full path, but add-on.xml file for JustSim Autogen Library works fine with a full path to the same folder.
Reunion- some issues
- horst18519
- Posts: 2444
- Joined: Thu Dec 15, 2011 4:28 pm
- FS-Version: MSFS
Re: Reunion- some issues
Thanks for your feedback and sorry for the delayed reply.
- Yes, Reunion only offered the choice between static jetways and default AFD-style animated jetways. We later abandoned that option in our other sceneries. (More information in the manual)
- It looks like FS Global increased the resolution for Reunion in their 2020 version. There were no issues with the old version when we created Reunion.
- That should not have happened. It might indeed be related to Cyrillic letters but we never had that issue before. Sorry for the inconvenience.
- Yes, Reunion only offered the choice between static jetways and default AFD-style animated jetways. We later abandoned that option in our other sceneries. (More information in the manual)
- It looks like FS Global increased the resolution for Reunion in their 2020 version. There were no issues with the old version when we created Reunion.
- That should not have happened. It might indeed be related to Cyrillic letters but we never had that issue before. Sorry for the inconvenience.