User4574

Can anyone confirm this issue in FSX for me? It seems to only be happening when I try downloading and trying the addon. The config file seems to come downloaded in a messed up way with the line for the commands all messed up. I think this is somehow causing the issue. Still can't seem to fix it in the notepad program even after I change it and save it.

Tried with DX10 preview both on and off and still nothing. I also tried fixing the aircraft config myself and making the commands as followed; Shift E: main exit Shift + E then 1: window curtains Shift E then 2: front cargo door Shift E then 2: rear cargo door yet nothing works. I think the commands are simply broken for this addon and there's nothing I can do to fix it unless the developer who made the addon stepps in and fixes it.

Well something happened because it no longer works even when I try changing the config. It still won't work even after deleting and reinstalling the addon. Any chance this could be a DirectX 10 issue causing the problem? I know DirectX 10 has given tons of issues to FSX recentily some I've had to use 3rd party addons to fix.

Trying it agin now it won't open anymore. Not sure what happened really. I swear its as if the custom commands for addons are just buggy AF now. I even tried doing another clean uninstall and reinstall of the Honda Jet addon and I still get the same issue. I think the developer may have screwed up the original config file somehow not the window curtains won't work no matter what I do. Really wish FSX had a way for us to add custom commands in the button mapping.

I now have it where rudder yaw right or left won't work in helicopters no matter what button I try mapping it to. For helicopters I perfer a seprate control methood other than turning the stick back & forth. I plan to eventually get rudder pedals so for now I'm ether stuck with the rudder stick control or what eever I have it mapped to. Cpuld it be the control mapping is confusing rudder with tail rotor and treats them as two separate things because of bad programing on Microsofts end?

I wish it were possible. Be cool if there was an addon program that enabled this to be possible. I was considering getting a touch screen monitor for this very reason mainly because using a mouse pointer in some VCs can be very annoying like for example in an Airbus where almost everything is done by knobs and some of the buttons and switches are ether tiny or sometimes in weird locations.

Been having an issue in FSXSE lately where it almost always switches to 'default audio device' instead of my bluetooth headset that I always use with my PC. Anyone have a fix for this? Driving me nuts now because my sound fx volume will get muted out of nowhere when the ATC starts speaking. Is there a way to select my bluetooth headset as the default audio device so the all the sound goes through that?

I'm having this problem as well. Its a real pain in the ass not having the progressive taxi guide arrows because the control tower gives you very vauge taxi instructions. It would have been nice if they made it so the control tower at least told you what direction to turn at what taxi way. Sometimes its hard to tell because a taxi way will go on for miles in ether direction before you know what the next taxi way to turn on is. Not sure how they deal with this in real life but I'm sure the tower gives better taxi instructions than in FSX and they probably use maps sometimes.

I recentily ran into a problem where my Alt keys now activates the Windows start menu. Not sure if it was something I did by mistake or something a Windows update did on its own. Its really annoying how I'll be in full screen then it exits full screen because my alt key now activates the Windows start menu as well as FSX alt menu at the same time. Anyone know how to fix this or is there a way I can custom map the in game menu in FSX? I'd rather it be a different key anyway like Tab or something like that.

So I decided to go ahead and treat myself to the TCA stick and eventually the TCA throttle(had to order them separatly) The stick works great but the throttle is a headache to program properly. So far I got passed programing the X & Y axis to throttle 1 & 2 so that FSX can finally stop reading each notch as a button programed for something else such as landing gear or view change. My biggest issues are I can't seem to get the dead zone down to 0% so if I have the throttle levers all the way down the throttle in FSX won't go as low as 31%. clCalibration program as well as null and sensitivity settings are useless for fixing this. And reverse thrust is seemingly impossible to program onto the throttle. I can only operate that function through button commands. FSX SE made no effort in a programmable reverse thrust option/feature to make this easy. Can anyone help/guide me to getting this setup properly?

I just got both the TCA Airbus stick and throttle quadrant. The quality seems Ok and the stick works great with FSX SE and has a nice hefty Airbus quality feel to it. The programing of the TCA throttle quadrant is a mess though and it could have been better made. It has a light, hollow feeling and is easily moved if you aren't careful not unlike the TCA stick. They also idioticaly programed buttons into each notch level of the throttle levers so null, one, two and three all read as buttons instead of X & Y throttle axis by default. Also its next to impossible to get reverse thrust function to work even though it should have been a standard out of the box feature already programed into the thing. The dead zone of the throttle is about 20% of the throttle so its always stuck at above 20% even though I'll have the levers all the way back even passed the reverse thrust notches. I wound up programing of the red side buttons on the levers as throttle reverse because it was so annoying. Most of these issues are probably just bad programing on both Thrustmasters FSX SEs part. They never ironed out the issues that causes these problems I suppose.