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.

RealAir Turbine Duke V1.2 Update Available

Featured Replies

"You have enabled landing lights in FSX haven't you?"Rob - RealAirYes, landing lights are enabled. If anyone has other ideas, please let me know. I don't want to have to do an FSX uninstall, reinstall just to get my landing lights back. There must be an easier way.Update: Problem solved. The Effects folder had been modified that caused the problem. Fortunately, I had a bare basics FSX install on a laptop where I could copy the Effects folder from. Learn from my mishap, and please backup your Effects folder. It can save you from a complex repair or a complete reinstall.

Curt Branch

  • Replies 66
  • Views 13.7k
  • Created
  • Last Reply

Top Posters In This Topic

  • Commercial Member
I'm using a pair of RXP 530s i.e. Unlimited and after some initial teething problems with Crossfill I got it working, you need to put the ini file in the panel folder and not in the same folder as the aircraft.cfg as is done by default by RealAir.
I'm very sorry to read you experienced this problem. It indicates there was a problem with the patch installer (see below).The RXPGNS.ini file located in the panel folder will always override the rxpgns.ini file located in the main Turbine Duke aircraft folder, this is how RXP chose to configure the RXP gauges. The old Turbine Duke config panel placed this ini file in the panel folder whereas the new config panel places it in the main aircraft folder. The RXP configurator places the ini file in the main aircraft folder so we chose to move the RXPGNS.ini file into the main Turbine Duke aircraft folder to make it more compatible with the RXP Configurator. The problem is now, if there is a copy of the RXPGNS.ini file in both folders then only the one in the panel folder will be read, meaning the changes you make in either the T Duke config panel or RXP configurator won't show up when you load the T Duke.Rather than copy the ini file from the main Turbine Duke aircraft folder into the panel folder as you have done, what you need to do is delete the ini file located in the panel folder, that way the ini file in the main aircraft folder will get used. The new T Duke config panel writes to this file so now when you make a change in the config panel your changes will work as desired.The reason there is a copy of the RXPGNS.ini file in your panel folder is simply becasue it was left over from your previous version 1 install. The V1.2 patch installer is supposed to delete the RXPGNS.ini file from your panel folder automatically so you don't experience this problem. For some reason this step didn't take place when you installed the patch. The mostly likely culprit here is the Windows UAC deciding that it knows best, not allowing the patch to delete that file on your system. So just to reiterate - if you experience the problem as described by AndyDigital above - the solution is to delete the RXPGNS.ini file from your panel folder.Sean MoloneyRealAir Simulations

Thanks for the update Sean, but I do not have UAC switched on, I always turn it off the second I have finished installing Windows 7 and its updates on any of my kit. As I said though it is working fine now on my rig at the moment. I'll give it another try maybe tomorrow, I cant make my mind up whether to upgrade my i7 920 to a Sandybridge, if I do then the patch installer will get another test run on the new machine ;)

Cheers, Andy.

Thanks for the feedback Andy. Oddly though, we haven't fiddled with the engine power, props or performance at all, so I'm wondering where this new handling feel you observe is coming from. The update was almost exclusively confined to panel and gauge functions, a few visual things, multiplayer and switches. I can't recall touching anything related to ground or air behaviour.Rob - RealAir
That's funny. I can confirm that I see the same changes in the FDE... Also, I'm a TIR+EZCA user and the option to disable vc click-spots just made my experience with the Turbine Duke a LOT better. Thanks again for this update.

Best regards, Fritz ESSONO

Yes it is strange that the FDE is so much different if you haven't tweaked it in anyway, I'll have to investigate further maybe something strange has happened to my FSUIPC calibrations for the Turbine, although it may have to wait, I did order my Sandybridge upgrade :)

Cheers, Andy.

It may be a bit off topic, but any sign of a paint kit or at the very least blank textures for the Turbine Duke?We have pilots that are asking us to add this to our fleet (we already have the Prop. version)

CXA001-1.jpg

VATSIM: P2 | I1

It may be a bit off topic, but any sign of a paint kit or at the very least blank textures for the Turbine Duke?We have pilots that are asking us to add this to our fleet (we already have the Prop. version)
The paint kit will be available soon and is progressing well.Regards,Rob - RealAir

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

The new engine performance is not down to FSUIPC calibrations or anything like that, I tested it again last night on my old PC Rob. Are you sure you haven't swapped out the FDE by mistake maybe, I've noticed some surging in the engine speeds too which was never a problem with the last version.

Cheers, Andy.

Hi, Andy. Can you give some more details on the circumstances happening there? Maybe a typical situation to experience the changes your are referring to?I flew her in 1.2 for some 2 or 3 hours now and didn't notice any FDE difference at all. I wasn't up to test it though, but she reacted on my bad flying in the same way as with the initial installation before.

It's instantly noticeable and everywhere CoolP, I dont need to point out any circumstances. I fly this bird a lot so I noticed how different she was the moment I started the aircraft and tried to taxi.She is also over weight by 47 kilos now when the tanks are loaded full by default on changing aircraft.

Cheers, Andy.

I'm sorry, I still can't concur there, not from the feeling or the reaction of the plane and engines, but also not from the files.The air file is unchanged, dated from February 2011 and from looking into the flight tuning, weight and balance and engine data in the aircraft.cfg, I can't spot any difference too.Maybe I'm too blind to see/feel though, that's why I was asking for some test scenarios.I'm using the file with the need for differential braking, maybe that adds something here.

  • Commercial Member

I can confirm, without a shadow of a doubt that the air file remains unchanged. There is no air file in the patch installer (it only includes the files that have been modified), so it couldn't possibly be different.Two very minor changes, unrelated to the engines or handling were made to the aircraft.cfg file, we're investigating whether these could have made a difference at the moment, but it seems unlikely.On another topic - I'm uploading the paintkit to our site now so it should be available within minutes.Sean.

It's instantly noticeable and everywhere CoolP, I dont need to point out any circumstances. I fly this bird a lot so I noticed how different she was the moment I started the aircraft and tried to taxi.She is also over weight by 47 kilos now when the tanks are loaded full by default on changing aircraft.
Hi Andy,There is one change in the aircraft cfg file that might affect weight. Previously we had the Turbine Duke running on avgas. Technically this is incorrect and we have changed the fuel designation to Jet fuel type 2 since the Duke has in effect a turbine jet engine. Jet fuel is slightly heavier than Avgas. Now, as far as I know, there should be zero difference in engine handling at all, and I'm unaware of any changes according to the SDK, but the extra weight might possibly make a small difference in feel if you are loaded up with the same amount.Since the only other change was electrical, and the air file is unchanged, it seems extremely unlikely to me that basic handling could be different. If you are unhappy you can always open your aircraft.cfg file (at your own risk) and change the fuel type back to avgas.All the best,Rob - RealAir

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

Hi Andy,There is one change in the aircraft cfg file that might affect weight. Previously we had the Turbine Duke running on avgas. Technically this is incorrect and we have changed the fuel designation to Jet fuel type 2 since the Duke has in effect a turbine jet engine. Jet fuel is slightly heavier than Avgas. Now, as far as I know, there should be zero difference in engine handling at all, and I'm unaware of any changes according to the SDK, but the extra weight might possibly make a small difference in feel if you are loaded up with the same amount.Since the only other change was electrical, and the air file is unchanged, it seems extremely unlikely to me that basic handling could be different. If you are unhappy you can always open your aircraft.cfg file (at your own risk) and change the fuel type back to avgas.All the best,Rob - RealAir
I've been testing it after Sean PM'd me the details of the change required in the aircraft.cfg and there is a difference in feel. Since the update FSX complains that the aircraft is over the MTOW when the tanks are full with the default payload load out. Maybe once you go over the MTOW FSX somehow exaggerates things in the FDE to punish you for not watching for over weight situations and perhaps this is what I am seeing in the ground handling. I'll try and do a little more testing today but I'm supposed to be building a new rig today, its still not arrived yet due to the shipping company being total idiots and using the wrong intercom system (they had the foresight to take a picture of it too) to get in the building and hence they thought no one was home to accept the delivery. They say they are going to come back.

Cheers, Andy.

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.