In my opinion, NO addon should be doing "global changes" to the FSX halo.bmp or spotlight.bmp files. This is a disaster waiting to happen, especially if someone uses a widescreen Surround Gaming setup like a TH2G. I've lost track of how many times something like REX overwrote my halo.bmp and spotlight.bmp files and caused my runway and other lights to turn into "beach ball" sized lights on my 3-wide monitor setup. Those of us who use something like the TH2G have installed smaller halo.bmp and spotlight.bmp files and changed the fsx.cfg files settings for the runway lights surface scaler, VASI, Approach, and runway strobes to settings that make it all work. No addon should be re-writing these files with their own versions of the file. I don't know if there is a "simple" solution to that...maybe an aircraft developer could make their own lighting system for the aircraft that doesn't mess with the halo.bmp and spotlight.bmp files...I don't know. But there are just too many addons for FSX that mess with these two files, and cause all kinds of grief for folks who have set up FSX to run on things like the TH2G.Rant over. :(

In my opinion, NO addon should be doing "global changes" to the FSX halo.bmp or spotlight.bmp files. This is a disaster waiting to happen, especially if someone uses a widescreen Surround Gaming setup like a TH2G. I've lost track of how many times something like REX overwrote my halo.bmp and spotlight.bmp files and caused my runway and other lights to turn into "beach ball" sized lights on my 3-wide monitor setup. Those of us who use something like the TH2G have installed smaller halo.bmp and spotlight.bmp files and changed the fsx.cfg files settings for the runway lights surface scaler, VASI, Approach, and runway strobes to settings that make it all work. No addon should be re-writing these files with their own versions of the file. I don't know if there is a "simple" solution to that...maybe an aircraft developer could make their own lighting system for the aircraft that doesn't mess with the halo.bmp and spotlight.bmp files...I don't know. But there are just too many addons for FSX that mess with these two files, and cause all kinds of grief for folks who have set up FSX to run on things like the TH2G.Rant over. :(

Hi Falcon,I agree about this, but to be fair to REX 2 developers, and indeed the X-graphics people, they did contact us to acknowledge the problem and quickly posted fixes. I think the key thing is for developers to give detailed information to their customers about exactly what their software does, before the user takes the plunge and installs anything.We adjust the landing beams ONLY for our aircraft and do so by tweaking the beam within our 3d models, NOT by altering any default FSX files. In other words we never, ever alter any standard files within FSX and our work never alters the state of other addons. I think this whole issue could be solved by developers making sure they inform users exactly what they are doing and by giving them a choice, in addition to providing backups for any file or folders which are altered, edited or deleted, and such editing should be clearly stated before the user gets to the point of installing.Kind Regards,Rob - RealAir

Anyone else having inop RMI issues?

FalconAF, perhaps learn how to use the REX options manager... it dictates what does get installed.Cheers.

Anyone else having inop RMI issues?

RMI operation appears normal on my setup.

My green RMI Needle seems to be tied to nav2 should be nav 1.

FalconAF, perhaps learn how to use the REX options manager... it dictates what does get installed.Cheers.

I wasn't trying to take a cheap shot at anybody, including REX. And I know how to use the REX options manager. But...How many less experienced users of FSX or FS9 would UNDERSTAND WHAT the option to install or not install new runway lights actually does? It's one thing to say something like, "This option will install new lights for your runways...", but if the user doesn't know that means the halo.bmp is going to get overwritten (and the possible consequences of that depending on their FSX configuration), then there is a distinct possibility that something is going to get "hosed". We've all seen too many forum posts from "inexperienced users" who end up just clicking "Yes, install them!", only to have to start answering the "fix" questions that ultimately result from that ("Hey! All my runway lights in FSX are way too big now! What happened?").And just having the addon make a "backup" of the "default FSX" files it replaces doesn't necessarily solve the problem. All to many times, the user has ALREADY installed some other addon that has replaced those default textures or files, so the new "default" backup isn't really backing up default files anymore. It can be a cascading effect, and the user can hose it up so badly that NONE of their "default backups" contain ANY original FSX files anymore.I was just offering an observation. There are so many duplicate type addons that replace FSX files now, an inexperienced user can very easily screw up their entire FSX installation as far as "default" files are concerned. Including a list of the files any addon is going to replace would make sense, so at least the user could review it first. I'm not suggesting a complete list of "cloud texture files" in something like REX would be required, but for other files like a halo.bmp or spotlight.bmp, it might be beneficial to include in the "instructions" PRIOR to overwriting them a little warning of sorts..."If you have already replaced these files in FSX with resized files (etc), be aware the files we replace may adversely affect your display of the lights." I agree with Rob...REX jumped on the bandwagon and immediately helped solve the problem with the Duke when it was recognized, and that is a reflection of great customer support and follow-on. I didn't intend to take a cheap shot at REX. Heck...I didn't spend all that time writing that tutorial you "stickyed" in the REX forum about making sure FSX would use the 4096 cloud textures in REX because I HATED you guys. :( Rick

My green RMI Needle seems to be tied to nav2 should be nav 1.

Hi BigSky,Sean is travelling at the moment but if you drop him an e-mail at RealAir maybe he can shed light on this.Kind Regards,Rob - RealAir

edit... I think there are variations of RMI's - this one is setup properly from what I've read on the net (if you read it on the net it's gotta be correct ;) )I've seen some where the smaller needle is NAV2 and others where the outlined needle is NAV2, and others where the small one is ADF, and some gauges you can switch the operation to slave to NAV1 or 2....

In my opinion, NO addon should be doing "global changes" to the FSX halo.bmp or spotlight.bmp files. This is a disaster waiting to happen, especially if someone uses a widescreen Surround Gaming setup like a TH2G. I've lost track of how many times something like REX overwrote my halo.bmp and spotlight.bmp files and caused my runway and other lights to turn into "beach ball" sized lights on my 3-wide monitor setup. Those of us who use something like the TH2G have installed smaller halo.bmp and spotlight.bmp files and changed the fsx.cfg files settings for the runway lights surface scaler, VASI, Approach, and runway strobes to settings that make it all work. No addon should be re-writing these files with their own versions of the file. I don't know if there is a "simple" solution to that...maybe an aircraft developer could make their own lighting system for the aircraft that doesn't mess with the halo.bmp and spotlight.bmp files...I don't know. But there are just too many addons for FSX that mess with these two files, and cause all kinds of grief for folks who have set up FSX to run on things like the TH2G.Rant over. :(

Ditto on his rant!

I wonder if this could be configured for single green(nav1) and double for nav 2

does anyone else find the mousewheel implementation is still not logical. you scroll up and the switch goes down ... :(

does anyone else find the mousewheel implementation is still not logical. you scroll up and the switch goes down ... :(

Hmmm, all switches behave properly as best I can tell. Have you selected the right/left option in the configurator? If yes, the mouse-wheeloperates as I would expect. :(

does anyone else find the mousewheel implementation is still not logical. you scroll up and the switch goes down ... :(

Well, you have more options throwing switches, tuning radios, and tuning navs in the Duke than at any time before, using mouse buttons, mouse dragging, keys, controllers, joystick buttons. The combinations of the options in the config panel give just about the most flexible options you could wish for. The circular motion of any control wheel does not have an "up" or "down".... that's why it is circular!Rob - RealAir

Rob,I have been using the (great!) Duke without any issues. Yet since I updated to V1.5 I cannot start engines unless I use CTRL+E.I am doing probably something wrong but I cannot figure out what. Can you please provide some suggestions of things I should be looking at to solve this problem?ThanksEdmundo