JetStream Designs

Hello Reccio, These look like default taxiway signs, and are not included into our scenery. Maybe you have another AFCAD file for Orly? Are you using France VFR Ile de France? I think there are some LFPO files to switch to OFF as they add default objects on our scenery Best regards, Thomas

Hi Erik, This is indeed related to the number of dynamic lights shown in that Paris area. They will simply disappear when you look towards Charles de Gaulle airport. This is where our "No Ai traffic at LFPG" option gets another point: It solves this disappearing DL issue as it removes the Ai traffic at LFPG (ai Traffic often comes with DL for each aircraft, so that can be a hige number of DL loaded at once). And you also have that solution you share with changing the max number of DL in the P3D CFG file

Glad to know this file solved the issue. It is an "exclude airport boundaries" file, which makes sure to exclude all default airport general boundaries.

Can you try the file enclosed to this message? (please install into Program Files\Lockheed Martin\Prepar3D v4\Prepar3D v4 Add-ons\JetStream Designs Palermo LICJ P3Dv4\Scenery ) cvx_Excl_AP_boundaries_LICJ.BGL

This is very weird. One possibility would be the use of a traffic addon which adds generic afcads to many default airports. Are you using such addon?

Hi Gianluk, Are you using Fs Global?

Hello Ted, it looks like your "scenery.cfg" file has some errors in it. But this won't prevent you from adding the scenery manually with the P3D scenery library tool Best regards, Thomas

Hi, Are you both using the Tomato Shade?

Hello, Performance has indeed always been a problem in the greater Paris area. We have written about this in the user manual (which you can open from the scenery configurator) - check page 6. However, we have put a tremendous effort in making sure the scenery is greatly optimized. On my machine ( I7-4790K, GeForce1070 and 16 Gigs of DDR Ram), it runs great. Performance is also better with the Orly scenery, than with the default one. Just to make sure, can you try to de-activate the scenery and see if it runs better with the default one? There are two settings (among other) you can change in order to improve your FPS: - autogen: set both the vegetation and buildings autogen to Normal (the are is very packed with autogen, and this car greatly harm the performance), and autogen draw distance to Medium. - Use MSAA instead of SSAA in your Display – Image and Texture Quality options. A huge difference in performance has been noticed, and graphical difference is very minimal. Please let me know about your findings Best regards, Thomas

Hi Valentin, If you get these red crosses, there is an issue with SODE for sure Now we have to narrow to understand why. First of all, is your SODE the latest version? Also, is it installed in the default folder (C:\ProgramData\12bPilot\SODE)? Regards, Thomas

Hi, Usualy, when the scenery is not added to the scenery.cfg by our installer, there is an error message saying 'the scenery.cfg file is corrupt". This means there are errors in your scenery.cfg, and the installer does not want to modify the file to avoid any damage. But you can still add it manually via the scenery library tool from the P3D menu. Just make sure to add the "terrain" layer with higher priority than the airport layer.

Hi, Did you install the scenery in the default install folder ? (Lockheed Martin\Prepar3D v4\JetStream Designs ) . If not, the effect files might have been placed elsewhere. Please check that you have the following files in your "effects" folder: - JSD_LFPO_dynamiclight_white_spot.fx - JSD_LFPO_dynamiclight_white_spot_cntrl.fx - JSD_LFPO_dynamiclight_yellow_spot.fx - JSD_LFPO_dynamiclight_yellow_spot_cntrl.fx Best regards, Thomas

Hello Manuel, The Fence thing is very strange. We have of course not placed any fence like this. Does this happen with Ezdok cameras only? We'll add that missing polygon inside the terminal. The very shinny textures is also something we did not get during testing. I have read that the Tomatoshade might not be P3D v4.4 compatible. Is it still the case? Maybe this is a shaders issue? Best regards, Thomas

Hello Jaap, About the JSD_LFPO_taxilights_lights , this will be solved with the next update (1.1) which is currently being completed. Expect release in the next few days. Are you still getting issues with SODE jetways? The above error message should not interfere with moving jetways. Best regards, Thomas

Hi Kai, The scenery was indeed not tested with FranceVFR Ile de France. Thank you for your feedback on how to disable these default buildings. The mis-labelled Runway 02 markings will be changed in the update 1.1 which is currently being completed Best regards, Thomas