Jump to content

Adjusting older 3rd party airports for P3Dv5


Recommended Posts

22 minutes ago, Ray Proudfoot said:

@Blasb, if it looks okay it will be okay. If there are no elevation issues like signs appearing above the ground it will be fine. Many FSX airports are fine with P3D. Classic example being FSDreamTeam ones. Nothing fancy but fully compatible.

Ah thanks Ray for the confirmation! Yeah there seemed to be no issues so that is nice, and I guess if there would be any issues I can just follow the steps outlined earlier in this thread.

i7 13700K @ 5.3 ghz / DeepCool AK620 Cooler / MSI Z790 Tomahawk WiFi / 32GB Trident DDR5 RAM @ 7200 mhz / 24GB Gainward 3090 Geforce RTX  / 2 TB SSD WD Black SN850X NVMe / 1 TB SSD Samsung 990 Pro series / 2 TB SSD Samsung 980 Pro Series / 500 gb and 250 gb SSD Samsung Evo 850 / RM1000W Corsair PSU - P3Dv5.4, X-Plane 12, X-Plane 11 and FSX

Link to comment
1 hour ago, Blasb said:

can just follow the steps outlined earlier in this thread

If it performs like expected, no further steps are needed. Most common problem is bleeding through of default buildings or height problems. Scenery usually has no coding in 32/64bits which make it unusable in in P3D4 and higher. This is only gauges and the aircraft using them.

  • Like 1

OS=WIN11 Home, Sim=P3D5 5.4 (P3D4 and FSX for install reasons)
Addons=ORBX, ASCA, AS, TOGA and tons of sceneries, aircraft

MB=Gigabyte AORUS Z790 Elite AX, CPU=i13900K, Cooling=Be quiet! Pure Loop II FX
GPU=KFA2 RTX3090 24 GB, RAM=64 GB DDR5-5600, HOTAS=Logitech G Saitek X52 Pro

Visit my website for fixes and addons: https://sites.google.com/view/dans-p3d-mods

Link to comment
2 hours ago, blaunarwal said:

If it performs like expected, no further steps are needed. Most common problem is bleeding through of default buildings or height problems. Scenery usually has no coding in 32/64bits which make it unusable in in P3D4 and higher. This is only gauges and the aircraft using them.

That make sense, thanks for the explanation! Haha, I guess I am being to cautious but following the principle better safe than sorry usually works!

i7 13700K @ 5.3 ghz / DeepCool AK620 Cooler / MSI Z790 Tomahawk WiFi / 32GB Trident DDR5 RAM @ 7200 mhz / 24GB Gainward 3090 Geforce RTX  / 2 TB SSD WD Black SN850X NVMe / 1 TB SSD Samsung 990 Pro series / 2 TB SSD Samsung 980 Pro Series / 500 gb and 250 gb SSD Samsung Evo 850 / RM1000W Corsair PSU - P3Dv5.4, X-Plane 12, X-Plane 11 and FSX

Link to comment

I have to add a new procedure recently developed. 

While trying to adjust Dreamflight-PuertoPlata for FSX, I could not adjust to the altitude given in P3Dv5. The wheels always sunk into ground. I disabled the CVX for the airport flatten and used the flatten given by P3Dv5 with the altitude set to 16.998 which is default in P3Dv5 as described in the tutorial above. The wheels were good, but trees were hanging in the air.

The solution was as follows. I kept the altitude of 15.000 ft which was used in FSX and added a terrain poligon to remove airport backgrounds. This is aimed at the default flatten from P3Dv5. 

The afcad has a revised altitude in regards to P3Dv5. This can be set in the raw data view mode. Also select to create a stub file. CreateStub and RevisedAltitude True.

I added both compiled files into the scenery. Also the airport flatten from Dreamflight needs to be active in the scenery directory. This one for flattening and the new one for the exclude of P3Dv5 flattens from the default scenery.

RDNk9uY.jpg

This is the result.djPt2aS.jpg

OS=WIN11 Home, Sim=P3D5 5.4 (P3D4 and FSX for install reasons)
Addons=ORBX, ASCA, AS, TOGA and tons of sceneries, aircraft

MB=Gigabyte AORUS Z790 Elite AX, CPU=i13900K, Cooling=Be quiet! Pure Loop II FX
GPU=KFA2 RTX3090 24 GB, RAM=64 GB DDR5-5600, HOTAS=Logitech G Saitek X52 Pro

Visit my website for fixes and addons: https://sites.google.com/view/dans-p3d-mods

Link to comment
  • 1 month later...
On 9/22/2023 at 2:07 PM, blaunarwal said:

If it performs like expected, no further steps are needed. Most common problem is bleeding through of default buildings or height problems. Scenery usually has no coding in 32/64bits which make it unusable in in P3D4 and higher. This is only gauges and the aircraft using them.

Ha! It seems as if this is the forum for Airport Design Editor users, together with p3dv5.3 as in your case, or p3dv4.5 as in my case.

You also know the 32b vs 64b problem? Well, I'm so happy that I'm no longer alone here at avsim with the search for an answer.

Not only height problems, which quite often really make me 🤬 .. Today, I have LFML Marseille Intl airport on my table, which with its p3dv4 default version is practically dead and useless, with an airfield elevation of 33 AMSL instead of 70 AMSL .

Or who helps you to jump over this 37 feet (11 meter) high 'wall' when you go along the LFML rwy 13L until the end? This 'wall' of course is only present in p3dv4, not in reality. And not really somebody helps you.

So, what did I do. First of all, I removed the default p3dv4 airport background. That's all! Only with this step, LFML really somehow jumped into the air, and according to the airport properties, it is now situated at a little bit more than 73 AMSL .

Which is good enough for me, also without a real field elevation correction. LFML is sloped on all four ends, so I thought by myself, 73 AMSL is not perfect, but for the LFML 31R the difference is only 3 feet. Good enough for me. So, I added a tailor-made airport background 'flatten exclude autogen', one or two good landclasses for the whole LFML area (!), and a twy layout which better suits the Original.

Dear greetings to Switzerland! ☺️

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...