September 15, 20232 yr 1 hour ago, Christopher Low said: The XML method never worked properly for me with scenery addons in P3Dv4, so I have all of my scenery installed the old fashioned way. What didn't work?
September 15, 20232 yr 10 minutes ago, newtie said: What didn't work? There are some sceneries that have hard-coded paths in their configurations, in which case moving them out of the P3D root folder breaks stuff. Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
September 15, 20232 yr Is this the aforementioned "XML" method? Add-ons (prepar3d.com) Add-on Packages (prepar3d.com) Edited September 15, 20232 yr by jcomm Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
September 15, 20232 yr 12 hours ago, BostonJeremy77 said: Now that v6 has VERY limited backwards compatibility with old 3rd party stuff It does? Odd, 95% of my P3D V5 add-ons work in P3D V6 ... even more so after 6.0.34.31011 update (patch 5 or is it 6). P3D's primary problem has always been (even before MSFS) getting 3rd party developers to actually use the new features in P3D versions like Dynamic Lighting, PBR, slopped runway native support, windshield effects, and more. Most used FSX as the base because they could sell more since their FSX products worked in P3D. If you look at how many PBR aircraft and airports exist for P3D, it's probably less than 5%. In many ways, 3rd party lack of support for these features is what kept P3D from realizing a larger audience/base. The vendor claim is not enough ROI for going the extra mile to support these features ... can't really debate the vendor since we don't have their sales data. Moving to a new engine like UE5 would be welcome but with zero existing product support. LM have a few different simulations groups and some of those development teams have already moved to UE5 so it's certainly a possibility for future P3D versions. Given that P3D supports CIGI (complete replacement of the graphics pipeline) it might be easier to shift to something like UE5. However, a few things would need to happen to gain 3rd party support: 1. It needs to be visually stunning (which UE5 is) 2. Come with enough out of box content to keep users interested 3. Flexible enough to support every aspect of flight Fortunately UE5 already has a free to use SDK built in which keeps improving over time and asset creation is very easy.
September 15, 20232 yr 10 hours ago, BostonJeremy77 said: That's not good enough. v6 is all PBR etc... If ORBX doesn't update their assets to utilize the new P3D tech? I don't want it. PBR was available in P3D V4.4 onwards, they didn't update existing assets several years ago. They used PBR on some of the newer airports they released, but my understanding is ORBX were prepared to walk away from P3D completely if LM had "required" PBR support. Guessing that legacy PBR conversion, wasn't done for P3D because of ROI. Only thing that has me somewhat puzzled is that ORBX must have a large volume of FSX/P3D assets that could be retro fitted but aren't willing to release them to devs willing to convert them to PBR for free. If ORBX aren't interested in P3D anymore and it's not making them any money, I don't understand why they wouldn't release the assets unless those same assets are being used in MSFS? Or perhaps they would rather just have everyone on one platform and only one platform MSFS? From a business perspective, platform diversity seems like a safer long term option.
Archived
This topic is now archived and is closed to further replies.