Jump to content

robpol471

Members
  • Posts

    389
  • Joined

  • Last visited

Everything posted by robpol471

  1. 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.
  2. 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.
  3. 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.
  4. "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.
  5. 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."
  6. You could use with CMD, Tracert to know where the route hangs but you need to know the address that Orbx Central uses.
  7. 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.
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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
  13. Thank you Anna and...ciao from Italy!
  14. 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.
  15. 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.
  16. Given that your situation is different because I'm referring to a P3D v6 installed in C:\ without other P3D v5.x while you, if I understand correctly, from C:\ see and start P3D v6 on H:\ but from what I see in your LOG it seems that ObjectFlow is installed but in the LOG there should be references to Orbx products that I don't see, for example like these: Are you sure that in Options - Scenery Library of P3D v6 there are Orbx products installed? If on Options - Scenery Library of P3D v6 there is no Orbx product and Orbx Library or as you called it is on C:\ try to go to: H:\ProgramData\Lochkeed Martin\Prepar3D v6 and in add-ons enter [DiscoveryPath.0] Path=C:\Orbx LIBRARY\p3dv5 Title=Orbx My Library Active=TRUE then add-ons will become: [Package.0] Path=H:\Program Files\Lockheed Martin\Prepar3D v6\Development Tools\Visual FX Tool Active=TRUE Required=FALSE [Package.1] Path=H:\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 In Path=C:\ replace Orbx LIBRARY with the name of your folder that you have on C:\ After launching P3D v6 you should be asked to enable the Orbx products in the library to then be displayed. Obviously not being able to check here because I installed P3D v6 on C:\ and not on another disk, mine is just a test you can do and I hope it works for you.
  17. Hi Timmo32, it is I who thank you for what you have written, but I have always thought that if I have received help here from other forum members to solve the problems I have had, it is right in my turn, obviously as far as I have been able to verify, to help those who have problems with P3D v6 here. Regarding your question about how to know if ObjectFlow is working, as I wrote in the post to install ObjectFlow when only P3D v6 is installed on C:\, you have to go to: C:\User\Name\AppData\Roaming\Orbx\ObjectFlow and with notepad open ObjectFlow. If ObjectFlow has been installed correctly on P3D v6 you will need to find at the beginning of the LOG: [LOG] ObjectFlow for Prepar3D v5 [DEBUG] Loaded Plugins [LOG] P3D is at C:\Program Files\Lockheed Martin\Prepar3D v6 [LOG] Core thread started! Again in this LOG ObjectFlow is noted to be doing a lot of activity both on P3D v6 files and on installed Orbx products and this further indicates that ObjectFlow is running properly on P3D v6. As for Orbx YMML I made a quick comparison between the one installed on P3D v5.4 and the same one installed on P3D v6 and from what I saw I didn't detect any differences or blurry images.
  18. Excuse me Aguiar, where I wrote: "" Once the Prepar3D v5 folder has been copied to C:\ProgramData\Lockheed Martin\ open add-ons and verify that in : [Package.xx] Path=C:\Orbx LIBRARY\p3dv5\Orbx ObjectFlow Active=TRUE Required=FALSE let Path=C:\.... and if the letter is different change it to C:\.... "" the letter on Path= should be replaced by putting the letter that your C:\ currently sees where Orbx Library is. For example, if the Orbx library is seen in D:\ the Path must be Path=D:\Orbx LIBRARY\p3dv5\Orbx ObjectFlow My error is derived that I have Orbx library on C:\ and hence all my Paths refer to C:\
  19. Hi Aguiar, Assuming that I have not found any problems with P3D v6 enabling of ObjectFlow and other Orbx products with the DiscoveryPath.0 procedure in add-ons that I described above, there is a "not working" problem with ObjectFlow enabled in P3D v6 that occurs if "only" Prepar3D v6 is installed in C:\. In this case the solution is the following: go to where P3D v5.x is installed and in ...\ProgramData\Lockheed Martin\ first check that in the Prepar3D v5 folder in add-ons there is: [Package.xx] Path=C:\Orbx LIBRARY\p3dv5\Orbx ObjectFlow Active=TRUE Required=FALSE obviously the name of the library will be the one you chose. so you need to copy this "folder" Prepar3D v5 in : C:\ProgramData\Lockheed Martin\ so in C:\ProgramData\Lochkeed Martin\ there will be folders Prepar3D v5 and Prepar3D v6. Once the Prepar3D v5 folder has been copied to C:\ProgramData\Lockheed Martin\ open add-ons and verify that in : [Package.xx] Path=C:\Orbx LIBRARY\p3dv5\Orbx ObjectFlow Active=TRUE Required=FALSE let Path=C:\.... and if the letter is different change it to C:\.... The other [Package.xx] present in add-ons must not be modified because in this procedure it concerns only ObjectFlow. Before doing this copy/paste the Prepar3D v5 folder, if ObjectFlow is not working even if it is enabled in P3D v6, it can be checked in C:\User\Name\AppData\Roaming\Orbx\ObjectFlow and with notepad open ObjecFlow. Here in the Log, if ObjectFlow fails, it will report the error that the add-ons file was not found in C:\ProgramData\Lockheed Martin\Prepar3D v5. Therefore the ObjectFlow procedure expects that in C:\ProgramData\Lockheed there is the folder Prepar3D v5. If ObjectFlow works in this LOG you will find: [LOG] ObjectFlow for Prepar3D v5 [DEBUG] Loaded Plugins [LOG] P3D is at C:\Program Files\Lockheed Martin\Prepar3D v6 [LOG] Core thread started!
  20. Hi Aussie, As explained in my previous post using DiscoveryPath is that everything in the library, including ObjectFlow, is installed. So far I have found only one problem but that could depend on P3D v6, it concerns the poor display of trees even if Orbx Global Trees and Global TerraFlora are regularly installed. Global Base textures and scenarios such as ESSA-KSAN-KBOS-KJAC and LIEO are displayed correctly while only in LOWI but depends on P3D v6, there is a visualization of an artifact (a small mound with a helicopter pad) between the airport buildings and the river flowing behind the apt.
  21. To one of my questions about reinstalling P3D v6 and deactivating the YES/NO license as when the Client is uninstalled in previous P3Ds, Rob McCarthy of LM gave me the following answer which I report for the uninitiated: assuming that after installing P3D v6 in the Windows Control Panel in Programs and Features two Prepar3D v6 Personal appear but of different GB, in my case the larger one is 111 GB and the other smaller 76.4 GB , if you uninstall Prepar3D v6 Personal with less GB you are asked, as for the previous P3D Client, if you want to deactivate the license YES/NO while if you uninstall Prepar3D v6 Personal with more GB nothing is asked but then, if you reinstall P3D v6, you need to activate your license online just like the first time you install P3D v6.
  22. 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 So 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:\ "Orbx LIBRARY" 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 each single product of the Orbx library, as happens on P3D v5. Obviously you can only install the Orbx products present in the library and not those installed directly in the Main program of P3D v5.
  23. I point out two artifacts that exist on P3D v6 and with this change are also displayed on P3D v5.4. The first is to the right of runway 28 of LIME where you see a large parallelepiped in the shape of a mountain and the second is in LOWI where between the airport buildings and the river there is a small hill not present in the original scenario of Orbx. I did a tour of the apt scenarios and I didn't seem to see other artifacts, however I point out that on the forum LM P3D was asked to report any anomalies of the P3D v6 scenarios where I saw the reporting of LIME and others. I also point out that with the same P3D v5.4 configuration, after this modification the fps do not drop below 40 fps in all pay scenarios.
  24. Sorry for the forgetfulness but it should be added that the same thing must be done on the Texture\Scenery and P3D v6 Texture folder by "Copying/Pasting" the files from Texture\Scenery and Texture from P3D v5.4 and then deleting the P3D v5.4 Texture folder and copy the folder modified Texture of P3D v6.
  25. Yesterday was a long day for me and the previous posts made late at night were synthetic, and I want to better clarify the steps I have done and which made my P3D v5.4, at least as regards the visualization of the scenarios, similar to P3D v6. Assuming that my hardware has an MB Asus Z590 F that supports 4 X SSD M2 and I have 2X Samsung 980 PRO that both have W11, P3D v5.4 and P3D v6 installed, (practically they are 2 clones) and that, if necessary, boot from bios. Calling the two M2 SSD M2s A and B, I boot from bios A (Master) for current use, while I boot from bios B (Slave) if I have to safely run the tests. This specific test had the following procedure which, to be precise, initially concerned a test on P3D v6 : I started B (Slave) and did a test by opening the P3D v6 Scenery\World\Scenery and Texture folders and with Copy/Paste I installed all the files from P3D v5.4 Scenery\World\Scenery and Texture folders. The test that concerned and made P3D v5.4 similar to the visualization of P3D v6 scenarios for me was to "delete" the Scenery and Texture folders of P3D v5.4 in B (Slave) and then copy the folders, previously modified, Scenery and Textures of P3D v6. As I did before, if this change doesn't give me problems on B (Slave), I will update P3D v5.4 on A (Master) which I will use for current use.
×
×
  • Create New...