Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Blacksquare Dukes update 1.2 (incl MSFS2024)

Featured Replies

Lots of thanks to Ryan and Tim for updating their paints. Aces!🤩

--Mike MacKuen
MikeM_AVSIM.png?dl=1

 

  • Replies 64
  • Views 8.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I've updated four of my liveries 🙂 https://flightsim.to/profile/TimHH

  • Such incredible addons... so nice to have both Dukes back in 2024!  With GTNxi bezels and headphone simulation - icing on the cake!    

  • Finally had a chance to fly the Grand Duke today to try out the new update.  Nice to have a few niggles cleaned up, like the oil viscosity in the left engine mirroring the right which messed up pre-oi

Deviate or penetrate? 🙂

image.png?ex=68cdff43&is=68ccadc3&hm=f41

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

24 minutes ago, sd_flyer said:

Deviate or penetrate? 🙂

image.png?ex=68cdff43&is=68ccadc3&hm=f41

Always penetrate LOL

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

26 minutes ago, MM said:

Lots of thanks to Ryan and Tim for updating their paints. Aces!🤩

You're Welcome!

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

15 hours ago, ryanbatc said:

I meant to ask you... what's the procedure for flight into the teens in this thing?  I think the power settings in my pic are too high (I wanted to go fast).  What would be more suitable for 75% power?  Like 30 / 2700pm?  And then with the turbochargers do you still lean out at 17,500 to the 75% power range on the fuel flow gauge?

Yep, those power settings look high at ANY altitude! 🙂  IRL, you'll pay for that in engine costs and longevity.  Don't know what Black Square's algorithms will make of them though.

Remember that in a turbocharged airplane with an automatic wastegate, the settings for x% power will be roughly the same regardless of altitude up to the critical altitude (with some small variations).  So, for example, on an ISA standard day, the book gives recommended power settings of 31.9 inches of mp and 2750 RPM for 75% from sea level up to around FL220.  That's what I typically use, with some adjustments if temps are dramatically warmer or colder.  Note, I rarely fly the piston duke above FL240 due to diminishing returns and the limitations in cabin pressurization.  I fly even lower mid-summer.  My passengers don't want to hear that they have to don oxygen masks!

As for leaning, I don't use fuel flow.  With the JPI EDM-760 and it's "Lean Find" mode, accurate leaning based on EGT is a breeze and far better than the approximation you get with FF.  I've never found detailed info on leaning for the Grand Duke (if anyone knows of a source for the Grand Duke POH, I'd love to know about it) so I lean about 25d ROP once I reach cruise.  And again, up to the critical altitude, FF should be mostly unchanged at those settings.

 

Scott

Does anyone happen to know if these are compatible with SU4 beta?

23 hours ago, ryanbatc said:

I've updated all of my liveries now - please note this was a pain in the rear.... probably took a good 8-10 hours to update all of them.

Thanks for updating your paints!   paintin' ain't easy, but it sure is fun. 👌

Rhett

7800X3D 96 GB G.Skill Flare  Gigabyte 4090  Crucial P5 Plus 2TB

On 9/18/2025 at 7:50 PM, ryanbatc said:

I meant to ask you... what's the procedure for flight into the teens in this thing?  I think the power settings in my pic are too high (I wanted to go fast).  What would be more suitable for 75% power?  Like 30 / 2700pm?  And then with the turbochargers do you still lean out at 17,500 to the 75% power range on the fuel flow gauge?

54795959452_6006609673_o.png

 

Hi Ryan,

 From sea level up to FL200 75% power is 31.9 In MP at 2750 RPM. Fuel flow should be 133 PPH per Engine which should net you 241 KTAS in the Grand Duke, and 225 KTAS in the stock Duke.  Same settings lower will give you 217 KTAS in the Grand at 10,000 feet and 198 KTAS at sea level again in the  Grand.

Climb to FL 240, and increase the throttle to 34.1 in MP with the same 2750 RPM for the same fuel flow of 133 PPH per engine but at 250 KTAS in the Grand or 234 in the stock Duke. 

Above FL240 you loose ground, so avoid it unless you are climbing above weather. FL300 at 29.3 in MP and 2750 RPM will save fuel, at only 104 PPH per engine but your TAS drops to 243 in the Grand and 227 in the stock Duke.

Recommended climb speeds gettin you up there are 140 KIAS from sea level through FL200, 130 KIAS through FL250 and 120 KIAS through FL300

 

 

Power setting charts can be found on Page 74, 75 of the  Piston Duke Manual.

Kerry W. Gipe
Savannah Georgia, USA
US FAA A&P / Commercial Pilot Multi Engine Land IFR

Your talent is a gift from God. How you use your talent is your gift back to God.

29 minutes ago, GACSavannah said:

Hi Ryan,

 From sea level up to FL200 75% power is 31.9 In MP at 2750 RPM. Fuel flow should be 133 PPH per Engine which should net you 241 KTAS in the Grand Duke, and 225 KTAS in the stock Duke.  Same settings lower will give you 217 KTAS in the Grand at 10,000 feet and 198 KTAS at sea level again in the  Grand.

Climb to FL 240, and increase the throttle to 34.1 in MP with the same 2750 RPM for the same fuel flow of 133 PPH per engine but at 250 KTAS in the Grand or 234 in the stock Duke. 

Above FL240 you loose ground, so avoid it unless you are climbing above weather. FL300 at 29.3 in MP and 2750 RPM will save fuel, at only 104 PPH per engine but your TAS drops to 243 in the Grand and 227 in the stock Duke.

Recommended climb speeds gettin you up there are 140 KIAS from sea level through FL200, 130 KIAS through FL250 and 120 KIAS through FL300

 

 

Power setting charts can be found on Page 74, 75 of the  Piston Duke Manual.

Thanks for the detailed response.. I guess I had forgotten this 😂 

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

4 hours ago, pobee10 said:

Does anyone happen to know if these are compatible with SU4 beta?

I haven’t tested every function and feature, but the turbo Duke at least seemed to behave normally when I used it yesterday. 

9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen

  • Commercial Member

I just hopped in the Turbine Duke for the first time since the update yesterday and enjoyed it once I got up in the air. Getting set up for the flight reminded me of why I sometimes get tired of Black Square products, though: the checklist is so mind-numbingly long. Especially for a multi-leg flight (e.g., land, shut down, walk to the FBO for lunch, then start up again and fly somewhere else), I suspect that it wouldn't be realistic to run through the entire list of pre-takeoff checks for every single leg of the flight. 

What would be a realistic way to handle this which is true to life? I know there are checklists out there on flightsim.to which label the essential items for just getting going, but are there any that give guidance on how often each systems check should be done?

Personally I try to memorize pre-takeoff checks into groups.  For example (piston Duke), run up to 2000 rpm and do the electrical stuff (mags, generators) and props.  2500 pressurization tests, then back down to 1500 for the rest (de-icing switches).  This way I don’t have to memorize each specific checklist item, and I can fly through everything in maybe 5 minutes or less.

Gary

 

i9-13900K, Asus RTX 4080, Asus Z790 Plus Wi-Fi, 32 GB Ram, Seasonic GX-1000W, LG C1 48” OLED 4K monitor, Quest 3 VR

 

Does the free PMS50 GTN 750 work? I've downloaded it and extracted to community folder. But I can't get it to show up using the tablet. Default GNS530 works.

Edited by Nemo

- Harry 

9800x3D (Strix x870e-E)  -  64GB RAM (DDR5 6000, CL 30)  -  RTX 5090, 34'' 1440p OLED HDR  -  Windows 11 Pro (1TB M.2)  -  MSFS 2024 (MS Store, 4TB M.2).

2 minutes ago, Nemo said:

Does the free PMS50 GTN 750 work? I've downloaded it and extracted to community folder. But I can't get it to show up using the tablet. Default GNS530 works.

Yes, it should work fine.

Ryzen 9800X3D, RTX 5090, 64GB, Win 11. MSFS2020. Moza, MFG, Fulcrum & Virpil controllers. Quest 3 for VR.

Hmm, does not here. Anything else what I have to do? I open the tablet, choose the GTN 750 as primary. Confirm. But nothing happens.

Edited by Nemo

- Harry 

9800x3D (Strix x870e-E)  -  64GB RAM (DDR5 6000, CL 30)  -  RTX 5090, 34'' 1440p OLED HDR  -  Windows 11 Pro (1TB M.2)  -  MSFS 2024 (MS Store, 4TB M.2).

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.