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.

Real Air Duke v2.0 Released

Featured Replies

I can't speak for RA but if it is a tiny bit off it may have been a tradeoff to get the std rate turn working perfectly.

 

Yes, that is what Real Air (Rob) confirmed as the reason they made changes to the yaw behavior, earlier in the thread, when I initially wondered if there was something to this "impression" of mine.  I don't know if it is "off", and I didn't use that word, only just my impression that the older version felt more "fluid" in the yaw axis in my very subjective point of view.  After flying the older version this morning, the only thing I can say more definitely is that the rudder is a lot more sensitive than before.  Whether that greater sensitivity is more accurate to the rw Duke, I haven't a clue!  Maybe it is, or maybe it isn't, but I'm definitely not as comfortable with the feel of it in the lateral axis as I was with Ver 1, despite it's new abilities to do a rate one turn at the correct indices of the instrument.

 

Notice I use a lot of (air) quotes above. :lol: I'm finding it difficult to find the right adjectives to describe what is more of a subconsious nag, since we tend to use our feet on the rudder without thinking about it too much, and then when we go to describe it, it's hard to find the best words.  As you go into the turn, what's your gut feeling, Ryan?

  • Replies 893
  • Views 130.1k
  • Created
  • Last Reply

I removed the traffic file on my PC that was injecting Piper Archers and Cessnas to the small Orkney airfields. Some of them were flying through stone walls when departing, because the runways simply aren't long enough for them! In addition, it's hard enough landing on a 1500 feet runway without some posh git in a Piper getting in the way.

Christopher Low

AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme

UK2000 Beta Tester

great now look what you guys did, made me go buy another plane   :t0115:

 

 

Can't wait for the TDuke upgrade.  My fav plane of all time!

There's an update planned for the turbine?

I just took my first night flight in this plane, and there seems to be something very strange going on with the Dome lights.  The dome lights illuminate the yoke, the throttles and the window frames, but the instrument panel itself remains a black hole.  It's very unnatural.  The Panel Lights illuminate the gauges, but so too should the Dome lights.

 

A direct comparison can be made with the Turbine Duke's Dome and Panel lights.  I hesistate to call out a bug, but when seeing how the Turbine Duke's internal lights work, it sure looks like it might be.  The Ver 1.5 Piston Duke's Dome lights also work well, although the panel lights only provide backlighting, and no flood lighting,so that's a little bit different.  I'm thinking that the guys at Real Air ought to give this a second look and see if it's working as they intended, because based on the T. Duke's internal lighting, it certainly appears that there might be some problems with the areas of illumination being covered by the respective lights, dome and panel.

I think they chose a different lighting scheme...

 

At night, best is to turn the dome light off and fly with panel lights only, I find..

Bert

I think they chose a different lighting scheme...

 

At night, best is to turn the dome light off and fly with panel lights only, I find..

 

Of course I turn the dome light off when flying, but what I'm saying is that compared to both the Piston 1 and Turbine Duke's dome light, the Piston Version 2 leaves a very odd looking dark area on the entirety of the instrument panel that common sense indicates should be lit by the ambient light, and in fact was in previous versions.  Let's just say I'm hoping its a bug and not a design choice, because if it's intentional, it would be a step in the wrong direction in my opinion.  Maybe it is intentional and they have their reasons why they must now do it this way, I don't know.

 

You really have to do the visual comparison between the 3 version of Dukes out there (Piston 1, Turbine 1, and Piston 2) to see what I'm talking about, and then it becomes fairly clear.  We are just talking about a stupid light afterall, but I think it's worth bringing up with the developers certainly, because I can't imagine why they would re-do the internal lighting like this when it was so very wonderful before.

There's an update planned for the turbine?

 

Yeah, I think there is. 

 

Hopefully customers who got V2 of the piston will get a discount? 

 

Just finished my first flight, and although it struggled to get up to 15k more then I expected ( I was 1000lbs below MGW, and had 40% fuel) at 11k I was getting 230 knots ground speed, which is pretty darn good for a piston! I was not in the winglet version as the wood looked too good to pass up.

 

Would it be possible to have a wingleted model with the walnut interior?

 

Anyway, it is a great aircraft, we are lucky as it is just pouring with superb aircraft recently, and I am very much looking forward to the turbine V2.

 

$40 well spent IMHO

 

Lee 

 

 

I kind of went over board. Have a look at my screen shots of the Duke in the Screen Shots forum. :unsure:

 

Would it be possible to have a wingleted model with the walnut interior?

 

You can edit the texture.cfg in your preferred exterior texture folder to insert the fallback path to the cockpit scheme of your choice.  For example, if you want G-REAL to be walnut instead of grey, you will change the first line of G-REAL's texture.cfg to read "fallback.1 = ..\Panel_Walnut". 

Yeah, I think there is. 

 

Hopefully customers who got V2 of the piston will get a discount? 

 

Just finished my first flight, and although it struggled to get up to 15k more then I expected ( I was 1000lbs below MGW, and had 40% fuel) at 11k I was getting 230 knots ground speed, which is pretty darn good for a piston! I was not in the winglet version as the wood looked too good to pass up.

 

Would it be possible to have a wingleted model with the walnut interior?

 

Anyway, it is a great aircraft, we are lucky as it is just pouring with superb aircraft recently, and I am very much looking forward to the turbine V2.

 

$40 well spent IMHO

 

Lee 

 

You can have Winglets with any repaint and any interior.  All simple selections in the aircraft.cfg.

 

Ray

When Pigs Fly . Ray Marshall .

Thanks guys I forgot about that, I'll take a look.

 

 

Of course I turn the dome light off when flying, but what I'm saying is that compared to both the Piston 1 and Turbine Duke's dome light, the Piston Version 2 leaves a very odd looking dark area on the entirety of the instrument panel that common sense indicates should be lit by the ambient light, and in fact was in previous versions.  Let's just say I'm hoping its a bug and not a design choice, because if it's intentional, it would be a step in the wrong direction in my opinion.  Maybe it is intentional and they have their reasons why they must now do it this way, I don't know.

 

You really have to do the visual comparison between the 3 version of Dukes out there (Piston 1, Turbine 1, and Piston 2) to see what I'm talking about, and then it becomes fairly clear.  We are just talking about a stupid light afterall, but I think it's worth bringing up with the developers certainly, because I can't imagine why they would re-do the internal lighting like this when it was so very wonderful before.

 

Best thing is to email Sean for his reasoning behind all of the above, or perhaps he might post about it here.

Robert Young - retired full time developer - see my Nexus Mod Page and my GitHub Mod page

Archived

This topic is now archived and is closed to further replies.

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.