Search the Community

OK, so this happens with my brand new CS 767 and also on trying to run the 4.6 upgrade for my CS 757 (which was already installed, I removed it to fault-find and it now won't install back in at all). Essentially, I run the installer and it goes through the activation point to the point where you can select the directory and can press "install." Except, the install button is gray, non-clickable and if I try and change the directory it still remains gray.I have reinstalled FSX with Acceleration. I have run the free FSX registry tool from Flight1. I have used CCleaner to clean out any reference of captainsim to try and allow a fresh install to occur. Stumped, I then searched Google and found nothing on this issue except a thread at sim-outhouse that stated that someone over at the REX forums had found a fix. FUrther research showed that REX changed forum software since then and the thread is at the bottom of the internet ocean. So, moving towards asking CS for help, I then searched Captainsim's knowledgebase to make sure I wasn't burdening them unnecessarily and I found a vague article that tells me I must not have enough HDD space to install, or to try a complete FSX reinstall. Having over 300GB of free space, I knew it wasn't that so I did a reinstall. So after doing everything it says to do and with the issue still occurring, I open a support ticket with CS and they reply after 2 days with a cookie cutter answer to go and check the knowledgebase article I'd already found (and had stated in the ticket that I had followed it already and the issue still occurred). Now they essentially refuse to help, but of course they gladly took my money. I could get a refund, but what's the point in that? I want this aircraft that I've paid for to work like the PMDG, IRIS, Aerosoft, ORBX, and many other addons I have paid good money for. So if anyone knows what might be the cause, or can remember the fix on the REX forum, I certainly appreciate any help you have to offer.

Hi, I've just installed FS2crew for the Airbus extended X and I've installed everything it tells me to. However when I go into fsx and select the panel, the Voice button never stays in the on position. There for I cannot speak to the crew. Please help because I'm desperate to get this addon working as it's my first FS2Crew addon I have, Thank you Conner

Hi all, I've been trying to figure out how to program a button for the Go Around button. Can't seem to figure it out. Anybody have a successful way of doing that using FSUIPC? Thanks, Gregg

I just thought I'd throw this out there to people who develop complex aircraft for FSX (and other platforms, I guess). A lot of people have external devices to control stuff. Lights, flaps, deicing, prop controls, autopilots. They use a button or a switch to control stuff you create on an airplane. As RealAir points out in at least one of their manuals, most accidents happen when the airplane is 'low and slow' and you don't want to mess around with a VC or bringing up a panel to do something critical so you program it into a button or a switch. So you program it into a button so you can keep from getting disoriented, even momentarily. So I progam my controls to keep my looking at my instruments or outside. After spending many hours trying to program my panel for a few buttons, I have realized that some things just can't be safely done due to the APIs provided. Here's my thoughts: Some things aren't modeled at all even though they are critical. Engine icing is an example. Flying along at 1500 feet in the soup, I have to turn my 'head' and physically click the button. There's, apparently, no API for this particular aircraft. Toggles. Critical things that are 'toggle' commands can be dangerous. If the effect of the switch can't be seen without turning your head (landing light toggles) then the toggle event may do the opposite. In small aircraft this is often simple because the switch is in front of the pilot...landing light...carb heat. In big aircraft, it's actually bad. You click the button you created on your control but you don't know if you turned it off or on. Thing is, turning your head (or glancing up) in a simulator is a lot more complex than in real life and, even though it's simpler in real life, that's what tends to kill a lot of pilots. So, if it's critical, create an API. Create an on and an off (and, sometimes, a toggle) if it's not visible to a pilot looking forward, don't make it a toggle. If you have to make it a toggle, flash a message on the screen..."engine ice on" "landing light on". It's more realistic since a pilot who flips a switch can feel it on their fingers. Just my two cents. I don't know how many folks have hardware with switches, maybe it's a lot, maybe not. It's at least something to consider when building a complex aircraft. Just one more blasted thing to think about.

Because the ThrustMaster HOTAS Warthog is such a wonderful control platform, and certainly the last I will ever buy, I thought we should share our config files and ideas, and suggestions for interoperability between P3d and the great add-ons that work with the pair. What do you think? Chas

I'm spending a small fortune trying to do the NGX justice. I just upgraded my joystick to a CH Eclipse Yoke (Happy Birthday to ME), and I can't believe I actually used the joystick for so long. The eclipse has a gazillion possible button combinations (240 is the real number), and I've been scrambling my brain for the last few days trying to map (get it?) a strategy for assigning the buttons to the proper operations. I've investigated the options in FSX (direct, but too restrictive), FSUIPC (Good Lord, what a monster), and the CH Manager (might be a good compromise). I would like a few opinions about this process', strategies, pitfalls, etc. Is it a good idea to combine the programs? I know the first thing you should be concerned about is double mapping a single button. I've read (heavily skimmed) the FSUIPC document, and been to the CH forums. FSX is pretty much self explanatory. Sorry to be so long-winded, but I think this is important. As always, TIA. D