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 Beech Duke 60 version 1.5 released

Featured Replies

I believe the following four settings are the only ones available in FSX.pitotdeicecarb heatpropeller deicethey should have key presses assigned to them.If I missed something then jump in.

  • Replies 121
  • Views 20.1k
  • Created
  • Last Reply

Top Posters In This Topic

Without having to audit this thread front to back, is there something I should do to prevent or correct the problems mentioned? I went ahead and changed my REX light settings to the Duke selection. Anything else?Stephen

PITOT HEAT POSSIBLE FIX=======================Hello chaps,A bright spark amongst our customers, Mr. Frederico Bellato, observed that reducing the voltage of the Pitot heat fixed this problem. I would be interested if anyone not seeing pitot heat working would be kind enough to do the following edit of their Duke aircraft cfg thus:Please make a BACKUP safety copy of your Duke aircraft cfg file. Open the file in Notepad then scroll down to the ELECTRICAL section. You will see pitot heat is assigned to Buss no.4. The third value is currently 24, meaning 24 volts. For some reason FSX does not like this voltage. Mr Bellato reports that reducing this value to 12 Volts results in the pitot heat working again.My grateful thanks to Frederico for this tip and apologies to all those who were inconvenienced. If a few users could post here that it worked for them, I will post a new thread with the fix and as soon as we do the next website update we will post the fix there. Thank you all very much, and again, sorry for any inconvenience.Best Wishes,Rob Young - RealAir Simulations

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

For some reason FSX does not like this voltage. Mr Bellato reports that reducing this value to 12 Volts results in the pitot heat working again.
Thanks for that Rob, I'll give it a shot. I actually tried increasing the amperage, but it did not work. Another workaround (albeit not ideal!) is by saving the flight and reloading.No apologies Rob. RealAir is a first class developer with support to match.

Well I've been in thick cloud now for 15 minutes at -1c and the pitot has yet to freeze, so I'd say that has fixed it, thanks to Mr bellato for the tip.

Cheers, Andy.

Well I've been in thick cloud now for 15 minutes at -1c and the pitot has yet to freeze, so I'd say that has fixed it, thanks to Mr bellato for the tip.
Hi Andy,I'm not sure, but I think you might also have mentioned nav lights not working until engines are live. It is likely that the nav lights might also need a voltage reduction, or even mapping to a different buss, to fix this. It seems that FSX only likes to function with a limit of 12 volts, but I didn't see anything about this in the SDK. So, that might be a solution and if so we'll include this in the fix.Kind Regards,Rob Young - RealAir Simulations

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

I actually just had something weird happen at the end of that flight when I shut everything down and switched the batteries off I went outside and looked around the aircraft and the nav lights and beacon were still lit, I had forgotten to switch them off but even so they should have been off because the battery was. I then loaded the default 172 and switched everything on and off again then reloaded the Duke but I was still able to turn all lights on even with the batteries off. Surely just changing the pitot to 12 volts should not effect all the other systems should it? or do we just put this down to FSX being buggy as hell again.Do you have any recommendations for these other edits you mention? or should we wait for a patch?

Cheers, Andy.

I actually just had something weird happen at the end of that flight when I shut everything down and switched the batteries off I went outside and looked around the aircraft and the nav lights and beacon were still lit, I had forgotten to switch them off but even so they should have been off because the battery was. I then loaded the default 172 and switched everything on and off again then reloaded the Duke but I was still able to turn all lights on even with the batteries off. Surely just changing the pitot to 12 volts should not effect all the other systems should it? or do we just put this down to FSX being buggy as hell again.Do you have any recommendations for these other edits you mention? or should we wait for a patch?
Hi Andy,I think we probably need to re-assign some busses, which I will be doing over the weekend. The main goal for now was to fix the pitot heat which seems to have been successful. The lights are not so serious, so I'm going to take my time doing this, but we should have an answer Sunday or Monday.Kind Regards,Rob

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

  • 3 weeks later...

Up :( Any news about this problem with the pitots ?

Up :( Any news about this problem with the pitots ?
Can you please e-mail me and I'll give the solution. It takes us quite a time to do official updates as there are new installers to make and test, different for all affiliates. Rob - RealAir

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

  • 2 months later...

Hi guys!I'm reading about this pilot heat problem with interest. I got the Duke about a month ago and found the update two weeks later. During flight, I'm getting power loss and it seems to be happening at around 10,000 feet. A few early flights at higher altitude I was getting the same thing, but learned how to use the cabin pressure and thought that was my problem. Last night, cruising at 10,000, got the power loss. Checked to see what it could be and tried fiddling with pilot heat. I did notice it was about 30 degrees outside. Power would come back around 6,000 ft. If I tried to get back to 10,000, I'd again lose power.So, is this pilot heat issue causing my problem? I could easily adjust the config file as Robert suggests (Electrical, Bus 4, change third value from 24 to 12) but I see Robert suggests to e-mail him for the solution. I guess I'll send him an e-mail, but hate to bother him if the answer is right here.Thanks.

So, is this pilot heat issue causing my problem?
No, if the pitot freezes, your airspeed indicator will drop to zero, but the plane will fly fine.Are you leaning the fuel mixture as you climb?Assuming that you are leaning the mixture properly, some users have suggested using the FSX carburator heat (H key). I know, it isn't supposed to be necessary in the Duke, but if it works ...
No, if the pitot freezes, your airspeed indicator will drop to zero, but the plane will fly fine.Are you leaning the fuel mixture as you climb?Assuming that you are leaning the mixture properly, some users have suggested using the FSX carburator heat (H key). I know, it isn't supposed to be necessary in the Duke, but if it works ...
Yes, I'm leaning the mixture properly. The airspeed indicator does go to zero as well. It's as if the engine just slowly starts to die, then dies. After a drop to about 6000 ft, I'm back to full power. I might be missing something else, been trying to cover all the bases.Carburator heat, hmmmm.....well, I'll try that, but don't understand why that would be causing the engine failure. Thanks for the reply!

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.