There are claims that the Duke is compatible with P3Dv2. Others (including RealAir) claim it isn't. Still others claim you have to futz around with the name of the P3D executable to get it to work. I tried to install the Duke using the FSX installer, and while the aircraft "kinda" works I discovered a number of visual anomalies including undesirable transparency in parts of the panel, bright bluish strobes positioned in the air off the ends of either wing and above the tail (at night), high draw latency (on either the panel or the aircraft) when switching between VC and spot views, no RXP 530 support (even though it was presented as an option in the config utility), and missing sounds.

 

I figure someone knows something I don't, someone wasn't terribly observant, or this aircraft really doesn't work in P3D in its present form.

 

Anybody have luck getting this aircraft to work?

Yea its was easy to install the way I did it. create a new folder and install the plane to that folder then simply put the various files and place them in the correct folders like you would a lot of freeware addons. The only issue is that the sound.gau doesn't work in P3D so you don't have the wind noise and the switches in the VC don't make a clicking sound which isn't really that big of a deal to me as I've never heard the wind making a steep turn in a real plane nor can you hear a switch clicking through a headset and engine noise in the real thing.

Good luck David

Thanks David. I'll try your approach next.

 

Do you know anything about this business of renaming prepar3d.exe to fsx.exe so the Duke can hook the executable?

You might try the migration tool its updated to work with V2 now flightsim.ee

I had no problems by simply pointing the installer to the P3D directory. I may also have moved my FSX.exe file to the P3D directory (can't recall). The plane works fine except, as noted, some of the sounds are missing.

It works, but the config app does not have any impact on the aircraft in P3D, but points to my FSX install.

 

FinnJ

Apart from surprisingly low performance in the cockpit, David's method appears to have worked for me barring the already known exceptions with sound and the lack of the RXP 530. I still see quite a bit of redraw latency in the panel/aircraft rendering when I move between Spot and Cockpit views.

You might try the migration tool its updated to work with V2 now flightsim.ee

 

I used the above tool, and the RealAir B60 appears to work perfectly for me.  (I haven't even had any disappearing clickspots!).

 

The FS Estonia Migration Tool is so crazily easy to use, effective, and cheap that it really amazes me how many people aren't using it, and are instead trying all sorts of ways of manually installing FSX add-ons.

 

It's a great little tool - I used it to install all of my Aerosoft and FlyTampa Sceneries;  all done completely painlessly in a few minutes. Worked great with the QW Avros, Airbus Extended and feelThere ERJs too.

I used the above tool, and the RealAir B60 appears to work perfectly for me.  (I haven't even had any disappearing clickspots!).

 

The FS Estonia Migration Tool is so crazily easy to use, effective, and cheap that it really amazes me how many people aren't using it, and are instead trying all sorts of ways of manually installing FSX add-ons.

 

It's a great little tool - I used it to install all of my Aerosoft and FlyTampa Sceneries;  all done completely painlessly in a few minutes. Worked great with the QW Avros, Airbus Extended and feelThere ERJs too.

Have you tried installing any orbx stuff with it?

Have you tried installing any orbx stuff with it?

 

Not yet, as the only Orbx that I've reinstalled so far is FTX Global and that already had a native P3D2 installer.

 

Orbx have indicated they're coming up with a migration solution so I'm just leaving the other Orbx stuff for now, until that solution is delivered.     But for all the other stuff, the migration tool is fantastic.      It doesn't make everything work (Majestic Q400 has no gauges displaying) but most things will migrate over.

I installed Duke 2.0 into P3D v2. Very low FPS in the cockpit. Unusable to fly.

V1.5 works just fine and frames are fine...

I installed Duke 2.0 into P3D v2. Very low FPS in the cockpit. Unusable to fly.

 

Same. 30 FPS (frame-locked) outside, 12-15 inside (even with shadows off). Have a new 780 GTX arriving today, so we'll see how that affects things.

I installed Duke 2.0 into P3D v2. Very low FPS in the cockpit. Unusable to fly.

Strange  :blink:  I get smooth 30FPS in the Duke V2. Outside and Inside.

Strange  :blink:  I get smooth 30FPS in the Duke V2. Outside and Inside.

 

System specs?