robpol471

General Platform Updates New Features Added support for FSR2 and DLSS/DLAA. Note: DLSS/DLAA is only available with Nvidia 2000 series cards or above. Added Resolution Scaling support for image upsampling and supersampling. Added screen space reflections (SSR). Added Contrast Adaptive Sharpening (CAS). Current flight plan is now saved and loaded with flight recordings. Updated various tree models to highly detailed 3D versions with wind support. Added LoadFlightPlanAction to SimDirector allowing for flight plan to be loaded for ownship or player objects. Added two-sided thin shading model allowing for greater detail in tree rendering. Rotor wash is now supported on vegetation. Precipitation effects are now supported on vegetation. Improved performance for autogen vegetation including LOD support. Added additional terrain detail textures. Glide path angle is now calculated and available through GPS system. Added runway transition support to arrivals. Updated navdata from the FAA’s Coded Instrument Flight Procedures (CIFP). Fixes and Improvements Improved night vision sensor effect visuals. Additional airport fixes and airport surface improvements. Various updates to global scenery, helipads, and airport building textures. Fixed terrain spike in French southern Antarctic. Fixed several terminal building and parking issues at KDTW and KOAK. Added 2D panel windows for F-16 LMFD, RMFD, and DED panels. Various updates to scenery models in major global cities. Fixed windshield effect for various default aircraft. Fixed flattening polygon issue in Australia and KTEX, and Telluride. Golden gate bridge is now PBR. Improved patch installation times. Fixed detail texture sampling issues when camera is far away from its initial starting point. Added Prepar3D.cfg option to disable blacking out 3D views when entering the UI. Fixed issue where calculating flight plan would override user cruising altitude values. Fixed issue where restoring bypassed legs in flight plan would not reconnect flight plan points. Fixed issue where multiple direct-to calls on procedure points would not set the active waypoint correctly. Improved TAA performance. Opening the Fuel and Payload screen no longer pauses the simulation. Navigation log now updates procedure points. Fixed issue where navigation log wouldn’t update on scenario load. Fixed cases where parts of SIDs and STARS were being skipped with certain transition IDs. Scenery Library layers can now be modified using a numeric text box. Improved Scenery Library drag and drop layer changing performance. Fixed bug preventing runway transitions flagged as both would not load. Fixed bug where runway fix would not load for some approaches. Improved shader compilation handling at runtime. Fixed issue where adding new objects in SimDirector could cause visualization graph to rearrange nodes when automatic graph layout was disabled. Fixed blend mode issue that could cause certain materials to become overly bright. Fixed issue where invalid waypoints in flight plan could prevent remaining valid points from connecting properly. Fixed issue that could cause layering issues with certain add-on airports. Fixed timing issues with Select Airport screen that could cause incorrect airport from being selected in some cases. Improved rendering performance of virtual cockpit only views. Tuned PAPI light intensities. Improvements to bloom appearance when using TAA. Fixed emissive script behavior for legacy PBR materials that could lead to washed out textures at night. Various fixes to ATG radar system including issues with beam heading and FOV settings. Fixes and Improvements (Professional Plus Only) Additional updates to better support Varjo mixed reality headset features. Fixed issue with effects not drawing on multiple displays connected to the same multichannel client. Prepar3D SDK New Features Day/Night, Sun/Moon, Exposure, and Emissive interpolant values are now accessible through the PDK. Added depth of field support through camera configuration and PDK. Added “Camera Facing Normals” flag to PBR material. Added “Has Pixel Movement” flag to PBR material. Added additional GPS variables including: FlightPlanWaypointApproachAltitude2 FlightPlanWaypointArrivalAltitude2 FlightPlanWaypointDepartureAltitude2 FlightPlanWaypointApproachAltitudeDesc FlightPlanWaypointArrivalAltitudeDesc FlightPlanWaypointDepartureAltitudeDesc FlightPlanWaypointApproachGlidePathAngle FlightPlanWaypointArrivalGlidePathAngle FlightPlanWaypointDepartureGlidePathAngle FlightPlanWaypointMagneticVariation FlightPlanApproachWaypointMagneticVariation FlightPlanArrivalWaypointMagneticVariation FlightPlanDepartureWaypointMagneticVariation FlightPlanApproachRemoveLegIndex FlightPlanArrivalRemoveLegIndex FlightPlanDepartureRemoveLegIndex FlightPlanApproachDirectToLegIndex FlightPlanArrivalDirectToLegIndex FlightPlanDepartureDirectToLegIndex FlightPlanApproachDirectFromLegIndex FlightPlanArrivalDirectFromLegIndex FlightPlanDepartureDirectFromLegIndex Fixes and Improvements Adjusted Weather Radar sample scale of precipitation in volume cloud to better align weather radar values between volume clouds and legacy clouds Fixed several typos in Learning Center CIGI, SimConnect, and window plugin documentation. Moved several post processes from core to SDK as samples.

If you have installed Orbx Libraries in P3D v6 you need to make this change to view the trees on P3D v6: ...\Orbx Library (or whatever you called it)\p3dv5\Orbx Libraries\Orbx\Scripts\custom.gb_base Rename AutogenDescriptions.spb to AutogenDescriptions original.spb Make a copy of AutogenDescriptions_Legacy.spb and rename it to AutogenDescriptions.spb If you also use this Orbx library for other P3D v5.x, after this change you will see fewer trees displayed on P3D v5.x while on P3D v6 they will be displayed regularly.

On 7/17/2023 I published a post to install the Orbx si P3D v6 products with this procedure: " Orbx products can be installed by entering C:\ProgramData\Lochkedd Martin\Prepar3D v6\add-ons [DiscoveryPath.0] Path=C:\Orbx LIBRARY\p3dv5 Title=Orbx My Library Active=TRUE Then the add-ons in C:\ProgramData\Lochkedd Martin\Prepar3D v6\ will become: [Package.0] Path=C:\Program Files\Lockheed Martin\Prepar3D v6\Development Tools\Visual FX Tool Active=TRUE Required=FALSE [Package.1] Path=C:\Program Files\Lockheed Martin\Prepar3D v6\Development Tools\Traffic Toolbox Active=TRUE Required=FALSE [DiscoveryPath.0] Path=C:\Orbx LIBRARY\p3dv5 Title=Orbx My Library Active=TRUE On Path=C:\ "LIBRARY Orbx" should be replaced with the name of your Orbx library for P3d v5. If your Orbx library is not located in C:\ it must be replaced with the letter where the Orbx library is installed. When you start Prepar3D v6 you will be asked to activate every single product in the Orbx library, as is done on P3D v5. Obviously it is possible to install only the Orbx products present in the library and not those installed directly in the Main program of P3D v5." After installing FTX Global Base, the trees were not present in the scenario but with this procedure they return to the same as on P3D 5.x: in ...\Orbx Library\p3dv5\Orbx Libraries\Orbx\Scripts\custom.gb_base Rename AutogenDescriptions.spb to AutogenDescriptions original.spb Make a copy of AutogenDescriptions_Legacy.spb and rename it to AutogenDescriptions.spb Two warnings: if this Orbx library is also used for P3D 5.x, after this change, the trees will be displayed to a lesser extent on P3D 5.x. I f you install P3D v6 without the presence of other P3D 5.x. you need a copy/paste from where P3D 5.x is installed, of the Prepar3D v5 folder in ...\ProgramData\Lockheed Martin\ which must be copied where P3D v6 is installed again in ...\ProgramData\Lockheed Martin\ if this is missing folder together with that of P3D v6, even if installed with the procedure described at the beginning, Orbx ObjectFlow does not work.

"Delete generated files" I've never used it, but I think it only deletes the installed scenarios. You can check with Lorby AddonOrganizer free or in P3D v6 - Options - Scenery Library which scenarios are present and reinstall the missing ones and in P3D v6 - Vehicle if there is the aircraft you installed.

I reported this problem to LM on P3D v6: Here we are at YMML airport by day with P3D v6 setting Options - Lighting - Brightness Adjustment at 0.00 https://imgbox.com/zNgidDhl Here at night with setting 0.00 https://imgbox.com/BUSgyaHt Here at night with setting 0.50 https://imgbox.com/Amta4AsQ This is LM Rob McCarty's answer on this issue: "We are working to improve lighting conditions in these cases."

You could use with CMD, Tracert to know where the route hangs but you need to know the address that Orbx Central uses.

You have to bear in mind that Patch 3 is basically a complete fresh install of P3D v6 and therefore you can delete the shaders after installation. I remind you that more than 100 GB of free space is needed on the media for the download and subsequently for the complete installation of P3D v6.

Hi Rod, my problem, and I don't think I'm the only one, is this displayed by these 3 screenshots: here we are at YMML airport Orbx by day with P3D v6 setting Options - Lighting - Brightness Adjustment at 0.00 https://imgbox.com/zNgidDhl Here at night with setting 0.00 https://imgbox.com/BUSgyaHt Here at night with setting 0.50 https://imgbox.com/Amta4AsQ

Unfortunately, at least for me, this patch did not solve the day/night light problem. If during the day in P3D v6 Options - Lighting - Brightness Adjustment is at 0.00 during the day, I have to set it to 0.50 if I want to see the airports correctly lit at night.

Attention. This download and install is taking me over 100 GB of memory and before downloading the patch, it's best to check the available GBs.

Hi Rod, I also hope they solved the light problem between day and night but I will know after the long download of 34 GB and installation.

It's basically a reinstall of full P3D v6 and its upload is 34GB. The Prepar3D v6.0 Patch 3 contains the following changes: All fixes and updates from previous patches. Rendering system performance improvements. Slight reduction to cloud scatter to make bottom of clouds less dark. Fixed texture UV wrapping issues at sloped airports. Various model texture fixes including the Piper, Tornado, CRJ 700, Ohio Class Sub, commercial airliners, countermeasures, ground vehicles, water helipads, and shacks. Fixed various autogen textures that were too dark. Fixed various water elevation issues. Fixed issue preventing custom weather themes from saving correctly. Fixed issue where legacy FailureActions would not load correctly due to missing ObjectReferences. Various scenery updates including KLAX, PACV, DC, Rome, North America, Europe, and Oceania. Fixed various water issues including European and Alaskan lakes. Fixed various issues with building density and generalization. Improved collision detection performance. Improved bullet collision fidelity. Added Camera Control UI in Views menu to allow for easier camera manipulation and saving. Reduced default bloom values (requires deleting Prepar3D.cfg in %appdata% directory or running “Delete generated files” in the application directory). Fixed issue with flight plan file path being saved as absolute path in fxml files. The flight planner UI is now available in SimDirector. Fixed issue where add-on text to speech voices would not select properly with dialog actions. Added separate day/night intensity control to dynamic lighting PDK. Added scalar for dynamic lights using legacy light PDK versions to increase intensity during the day

Thank you Anna and...ciao from Italy!

If you're referring to my post, I agree and in fact I didn't explain which registry keys need to be changed, but my post was just a stimulus to those of Orbx who should give us information if they are working on P3D v6, not forgetting that we are "Customers" or tell us that for Orbx products on P3D v6, we have to find the solutions to make them work.

What I can say about Orbx Central is that if the main folders of Prepar3D v6 are renamed to Prepar3D v5 and the same operation is done on the registry keys and the relative Paths with Regedit, I have verified that Orbx Central regularly installs the products present on the Orbx library and, if desired, also installs the Orbx products in P3D v6 renamed v5. If P3D v5 is present on the same disk, all related Prepar3D v5 main folders should be renamed so that Orbx Central only sees one Prepar3D v5, but that is in fact it is Prepar3D v6. At the end obviously all the keys and the relative Paths must be restored and the Prepar3D v6 folders correctly renamed and, if installed, those of Prepar3D v5. I don't describe the procedure in detail because when you have to change registry keys a small mistake can create big problems, but I can say, IMHO, that if Orbx Central recognized P3D v6, there shouldn't be any problems. So far the only difference I've noticed in P3D v6, after the installations made with Orbx Central or with the DiscoveryPath.0 procedure, is the very little presence in the scenarios, but outside the airport ones, of trees.