October 5, 20178 yr Can someone confirm if FSDT DFW works with P3dV4? If so, is it an easy install? Thanks Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU 32GB G.Skill Performance DDR4 SDRAM 3600MHz Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System 2TB Western Digital, NVMe M.2 Solid State Drive
October 5, 20178 yr as far as i know all fsdt airports are p3d v4 compatible, you can download the installer from here https://www.fsdreamteam.com/products_kdfw.html and then try it, you have 5 minutes to try it out :)
October 5, 20178 yr I have it installed in p3dv4 works great and good FPS. Tom Davis I7 6700k 4.7 ghz, gtx 1080ti , 16gb 3400 ram, 32’’ 2k monitor, 1TB ssd, 500gb ssd, 250gb ssd, h115 water cooler
October 5, 20178 yr Author Thanks Guys Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU 32GB G.Skill Performance DDR4 SDRAM 3600MHz Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System 2TB Western Digital, NVMe M.2 Solid State Drive
October 5, 20178 yr all fsdreamteam and flightbeam airports work, flightbeam airports are being charged upgrade prices to be compatible with there own flight beam manager as they are upgraded, it's a really nice feature.
October 5, 20178 yr Commercial Member 4 minutes ago, Patriot3810 said: all fsdreamteam and flightbeam airports work, flightbeam airports are being charged upgrade prices to be compatible with there own flight beam manager as they are upgraded, it's a really nice feature. No they aren't, KSFOHD v2 was free to existing customers.
October 5, 20178 yr Looks very poor texture wise. They need to seriously update this to P3DV4 standards. Or another developer should recreate this airport.
October 5, 20178 yr Im missing aircraft shadows at fsdt and fb airports but i think the culprit is ftx global. greg
October 5, 20178 yr I dont know what the culprit is at DFW, but in p3dv4 the runway is 50+ feet below the surface. Completely unusable. Lennie, Henderson, North Carolina. Piper Warrior II pilot; Volairsim cockpit; Corsair 750D case; Corsair 850W PS; Maximus IX MoBo; Samsung EVO 850 SSD; Toshiba 3TB ExtHD; 3-ASUS Proart 24" monitors; 2-GTX 1080ti video cards; I7-7700k CPU; Saitek instruments and panels - SPAD, MFG Crosswind rudder pedals; Brunner CLS-E yoke and Virtual Fly throttle; Win10 Pro; MSFS.
October 5, 20178 yr 1 minute ago, lennie said: I dont know what the culprit is at DFW, but in p3dv4 the runway is 50+ feet below the surface. Completely unusable. You probably need to use the elevation correction tool in ORBX Vector. Thomas Derbyshire
October 5, 20178 yr Yep i did that at least 3 times, nothing changed!!! Lennie, Henderson, North Carolina. Piper Warrior II pilot; Volairsim cockpit; Corsair 750D case; Corsair 850W PS; Maximus IX MoBo; Samsung EVO 850 SSD; Toshiba 3TB ExtHD; 3-ASUS Proart 24" monitors; 2-GTX 1080ti video cards; I7-7700k CPU; Saitek instruments and panels - SPAD, MFG Crosswind rudder pedals; Brunner CLS-E yoke and Virtual Fly throttle; Win10 Pro; MSFS.
October 5, 20178 yr 49 minutes ago, lennie said: I dont know what the culprit is at DFW, but in p3dv4 the runway is 50+ feet below the surface. Completely unusable. I'm not having any trouble. I use Vector. Make sure that DFW is above all your Orbx sceneries. Mine has a priority of 2 or 3. Double check to make sure that DFW is in your exclude list. It may have to placed there manually. blaustern I Earned My Spurs in Vietnam
October 5, 20178 yr Ok will try that, thanks!!! Lennie, Henderson, North Carolina. Piper Warrior II pilot; Volairsim cockpit; Corsair 750D case; Corsair 850W PS; Maximus IX MoBo; Samsung EVO 850 SSD; Toshiba 3TB ExtHD; 3-ASUS Proart 24" monitors; 2-GTX 1080ti video cards; I7-7700k CPU; Saitek instruments and panels - SPAD, MFG Crosswind rudder pedals; Brunner CLS-E yoke and Virtual Fly throttle; Win10 Pro; MSFS.
October 5, 20178 yr Can't blame FSDT for elevation issues in a scenery and that came out years before the ORBX products that actually caused those elevation issues. i7-13700KF, 32gb DDR4 3200, RTX 4080, Win 11, MSFS 2024
Archived
This topic is now archived and is closed to further replies.