Top man Rob! Do us a favour and have a word with Carenado about their C337 and the 206H will you? Show 'em how it's done! :lol:

 

Better yet; RealAir should develop their own version of these aircraft. I would love to see more GA aircraft done right, by a company that can do so much more than just making an aircraft that looks good.

Better yet; RealAir should develop their own version of these aircraft. I would love to see more GA aircraft done right, by a company that can do so much more than just making an aircraft that looks good.

Now you're creeping! :biggrin: You still won't get a freebie.

When I said the turbine is better in every aspect I was not only referring to performance (speed, required runway) but also to the optics and system depth of the addon.

 

When I switch from the turbine to the piston I miss the dirt in the cockpit. The piston looks so steril in direct comparison. Also that you can kill the engines without proper handling. It is more like the whole package, all those little details make the T-Duke more realistic and to my preferred version.

 

Speed alone would not be a reason to prefer one version for me (as I said the T-Duke makes everything almost too easy... :rolleyes: ). What I like about the piston is the more direct and precise handling.´Still, both planes are awesome.

The easy to fly planes end up back there. For me both dukes and the AN2 the latter which is a fixed wing helicopter, no stall = no challenge.

 

I consistently end up flying with the PMGD js41 and the 737ng, they are never in the hanger very long

How, pray tell??

 

I'm really looking forward to updates to this exceptional aircraft!! Thanks RealAir!

 

I was going to second the 'how?', but decided to go have another look around the net to find out how (I couldn't find anything last time I looked)...

 

Editing aircraft.cfg and commenting out the CameraDefinition sections from .1 to .5 is all it takes. You still get the 'Left click for ... Right click to return to main view' tooltips, but clicking there does nothing and effectively removes the click spots.

 

 

The easy to fly planes end up back there.

 

I'm the opposite. If I have to do ten times more reading than flying, I find myself losing interest faster than a F/A-18 Hornet at full afterburner!

We will be soon be updating the Piston Duke to RealAir Legacy sound and visual effects standards, and a slightly revised flight model that enhances what is already there. Then we will work on the Duke Turbine in a similar manner. Our aircraft are made for the long term.

 

Best Wishes,

 

Rob - RealAir

Rob, as has already been said by others in this thread, this is good news.

 

Is it possible for you to give us a rough time table for the Duke updates as well as the new 172 addition?

 

At least, could you please tell us are talking about weeks or months to wait?

 

Thanks for all of your hard work and great products.

I was going to second the 'how?', but decided to go have another look around the net to find out how (I couldn't find anything last time I looked)...

 

Editing aircraft.cfg and commenting out the CameraDefinition sections from .1 to .5 is all it takes. You still get the 'Left click for ... Right click to return to main view' tooltips, but clicking there does nothing and effectively removes the click spots.

 

 

Thanks for posting your findings, Nikki. I guess that is a potential compromise to actually eliminating the click spots and I suppose it has been around for a while. Of course that eliminates each of those views from use completely (unless I am missing something else).

 

I was just hoping Brent ("dcgator29") actually had a method to remove the click spot itself.

 

Guess I will be anxiously awaiting the update.

Of course that eliminates each of those views from use completely (unless I am missing something else).

 

 

Maybe try renaming or renumbering them? I don't know if the click spots reference them by name or number. Personally I use ezdok, so don't care too much about losing views I didn't really use anyway, but I can see how that'd be a problem for people not using ezdok.

 

e: btw, to the realair people if they're watching...

 

On the turbine duke, one very small 'fix' that I found increased my immersion was using wavosaur to put loop points in the starter sound, so that it doesn't do the click, starter-whine, fade-out, click,starter-whine, .... sequence if you need to let Ng rise longer than the sound file. Instead it just clicks, whines and stays whining until you turn off the starter motor.

For lack of a better place to put this question....

 

I was doing my preflight on the Turbine Duke today and accidentally hit a 'de-ice' switch on my Saitek Multiplanel.  Surprise...two enunciator lights came on on the right panel..."L Engine Ice, R Engine Ice".  I had never seen them before and had always assumed that the only deice switches were the ones by the pilot's left knee.  On a lark, I pressed H as a test and, lo and behold, they do come on if you press H along with the other deice switches, but I don't use my keyboard to control anything so I'd never seen them before.  On the preflight I'd always been confused by the entry to check engine ice during the runup and just just turned the Fuel Vent Deice switches on.  *Shrugs*

 

So, my question is...where are the switches in the cabin for Engine Ice?  I don't see them...nothing moves when I flip the Saitek switch.

 

 

urprise...two enunciator lights came on on the right panel..."L Engine Ice, R Engine Ice". I had never seen them before and had always assumed that the only deice switches were the ones by the pilot's left knee. On a lark, I pressed H as a test and, lo and behold, they do come on if you press H along with the other deice switches, but I don't use my keyboard to control anything so I'd never seen them before.

 

Huh!  Well, I'd always just assumed that the inertial separators (ice doors/engine ice) weren't modeled, and hadn't noted those annunciator lights before.  Fired up the T-Duke to test, hit "H" and sure enough - not only does it light the lights, but the correct engine behavior occurs.  Very strange that there are no switches in the VC (at least not that I can find either), but the behavior seems to be properly modeled.

 

Scott

The problem with hitting H is that it also makes the prop ht and surface cycle switches move as well.  Looks like a bug that they should fix for this new version they're cooking up.

 

Speaking of H, maybe they'll fix the thing in the Piston where you have to hit H to stop carb ice from forming, even though their is no carburetor.

 

 

The problem with hitting H is that it also makes the prop ht and surface cycle switches move as well.

 

Yep, it's a big hammer.

 

 

 

Speaking of H, maybe they'll fix the thing in the Piston where you have to hit H to stop carb ice from forming, even though their is no carburetor.

 

The Milviz B55 does this now, which is nice.  Otherwise, I add this to my pre-takeoff checklist for all my fuel-injected piston planes.  There's no performance penalty (as there is in a real carbureted plane), so I just get it out of the way and forget about it.

 

Scott

I don't think it was the intention of the original poster for this to turn into a remaining bugs/wishlist thread, but in light of the fact that there is an update coming and that there is no dedicated Real Air Forum....

 

I happen to have the reality xp radar.  The only plane I know of that natively supports this is the PMDG J41.  Also, I've managed to incorporate this very nicely into the Milviz 310R.  Other than that I have no use for it, and honestly I don't think that it works well with the Active Sky weather mode I use anyway.

 

Still I think the Duke would be the perfect plane for it and I was wondering how much of a major overhaul it would be to provide an additional VC option for both Dukes to natively incorporate the RXP Radar into the 3D panel.  Don't most rw Dukes have a weather radar?  It would be the ultimate cool to have a GNS 530 and 430 in crossfill and a weather radar too.

 

Anyway, just a thought.

I'll have to look and see how that switch does what it does.  It only turns on the engine ice...nothing else.

Hmmm.  I found this in an LUA script...

 

function AntiIce_On ()

        ipc.control(66029)

        end

 

function AntiIce_Off ()

        ipc.control(66030)

        end

 

function AntiIce_Eng_1_2_Toggle ()

        ipc.control(66484)

        ipc.sleep(500)

        ipc.control(66485)

        end

 

Seems like that last function would be the trick.