fm_weasel

Except that this particular plane doesn't have engine anti ice equipment. If the bug is anything like the icing I encounter in other aircraft, in FSX, it also can't easily be avoided by staying clear of clouds. FSX and Activesky seem to consistently over saturate the air you're flying through. If it's cold enough, you're likely to see icing problems crop up. I guess it's a good thing that the carb heat bind works in the background. It's a minimal impact to realism. Real pilots of the Lancair and similar aircraft would avoid flight above the freezing level into clouds. Doing so should reasonably ensure that they won't encounter induction or aiframe icing which they are incapable of clearing due to the lack of anti/de-ice equipment. Unfortunately doing so in FSX doesn't always ensure that you won't freeze up.

That's good then, at least the fix works in favor of performance.

I hadn't noticed it either, probably because I've flown other GA at lower altitudes mostly. Anyone notice, when you use the Carb Heat Bind, does engine performance decrease like it should? It'd be unfortunate to have to fly around with a slightly derated engine all the time

You can still encounter induction icing in a fuel injected aircraft. Ice can block or partially block the air intake when flying into moisture at temps near and below 0C. I guess the fact that the carb heat bind fixed the issue indicates your situation was related to the FSX bug. Just keep in mind that you may still encounter icing that affects a fuel injected engine if flying into those types of conditions. Absent any type of engine anti-ice system, there's nothing you can do about it except avoid the condition in the first place. I wonder if the ALT AIR knob would affect engine performance in icing conditions. I don't see it mentioned in the manuals.

Are you flying through clouds? It sounds like you're icing up. You need to be lower, in warmer temps, or remain clear of clouds to prevent icing. Your carb heat is missing because the engine in the Lancair doesn't have a carburetor. It is fuel injected. It is not certified for flight into icing conditions.

This aircraft feels ALIVE in every sense. More than any other aircraft in my virtual hangar. After I build up the courage to buy the Reality XP 530 and start flying with more up-to-date navdata, I think this plane will be the perfect cross country GA platform.

This issue is discussed on Flight1's official support forum for the Citation Mustang. They released a fix for it, go check it out.

I expected as much. I intend to read the material cover-to-cover soon. I just had to jump in and start flying. I did manipulate some options in the config utility at first start but clearly I missed the specific option. Figures you guys would think of everything. Thanks. EDIT: Heh, it even says right on the option "For TrackIR users"

Just put 1.5hrs on this plane this evening with a friend who also bought it. Amazing aircraft. I'm really going to enjoy learning how to manager it during the various phases of flight (it's fast and slippery). Also, it worked with all of my Saitek Panels OUT OF THE BOX, utilizing the SPAD driver and default settings. That was a huge relief, normally my Multi Panel (autopilot) needs extensive configuration using mouse macros and the like. But not the Lancair! Everything works, and the panel displays update automatically. The only gripe so far (other than I need to become a much better pilot... it's so fast) is that there are several click spots on the Virtual Cockpit that cause you to change view. I use TrackIR, so I don't necessarily need them, and I've been accidentally hitting them while trying to click on other VC items. I bet there's an easy way to disable this, I just haven't figured it out yet. Great job, RealAir This plane makes me seriously consider adding the RealityXP G530, so I can do true /G IFR. For now I'm gonna keep it /A and maybe cheat with the default GPS occasionally.

Is this patch on the official PMDG website in the download section?

A third party developer made a replacement driver/configuration software for the Saitek Panels called "SPAD."Using SPAD, and user-created .lua files, you can get the panels working with add on aircraft like larger jets. However, if someone hasn't made the .lua script necessary for your particular aircraft, it may not work well. You can use SPAD to assign the knobs/buttons to specific functions as best you can, but the display won't update with the in-game alt/hdg/etc displays unless you have a .lua script made specifically for that plane.I've been able to find such scripts for the PMDG JS41, but I don't have one for the NGX since the developer kit hasn't yet been released. You can also try making your own script files but it's rather difficult if you don't have prior programming experience.Long story short, don't expect the panel to work completely out-of-box with your add on aircraft.

There are two types of MS FFB2 sticks on the market. One with a gray trigger and one with a red trigger.Reports say that the Red Trigger version works with Win 7 64bit. It's also WAY more expensive and difficult to find on eBay than the Gray Trigger model.I have the Gray Trigger model and it does NOT work on Windows 7 64bit.The Thrustmaster stick mentioned above doesn't have Force Feedback so I don't think that will work for the OP either.It's a real shame because the FFB2 is a great stick.

Sorry to resurrect this thread, but has anyone noticed that when utilizing the STBY function from the script, that the FD disappears, but all of the auto panel lights (in the virtual cockpit) light up and remain on until the virtual standby button in the VC is pressed?Going back and re-enabling other autopilot modes like HDG, ALTSEL etc, continue to work, but all the AP panel lights remain illuminated until pressing the virtual cockpit STBY button and starting over.

Do you have a red trigger FFB2? If not, Fsforce will not solve your issues.

When you say press really hard on them.... you mean on the bottoms of the pedals so as to force them back into the off position? If that's the case, just set up the pedals in FSUIPC and set the lower range with your brakes slightly applied. This will make them cut off before your pedals reach the full "no-brake" position. I had to do that when I took mine apart to repair them, and the pots got misaligned on re-assembly.If they're showing "on" when you leave you feet off the pedals, but the brakes go off when you push both forward, then you just need to reverse the axes.

Agreed. It's a manufacturers defect. If you've had it less than 2 years, Saitek will probably help you out. Beyond that, you need to tape over it (like I did, as well). It's not repairable.

Ah, my version is the grey-trigger one. Perhaps that's significant. Either way, I've had to remove it from my setup. I really liked that stick, and I want to continue using FFB since FsForce is such a nice program.The search begins for a new controller. I had the Logitech G940 but I had to replace it 3 times due to overheating issues, so I'm ruling it out.

Did you do anything special to enable it to function? Mine is detected by windows, but FSX locks up when it's plugged in, as does the FsForce profiler. If I unplug the FFB2, everything runs fine again.I guess it's a crapshoot.

The Sidewinder FFB2 does not work in windows 7. I have the registered version of FsForce2 and can confirm that it does not enable the stick to work in Windows 7. Don't purchase FsForce2 thinking it will help, you have to get a newer stick.That said, FsForce2 is an amazing program and I recommend it to anyone who has a compatible FFB joystick. It's a great add on and worth every penny.I used it with much success on my old Vista box. I just upgraded hardware and switched to Windows 7, and now I have to find a new solution for my input. I'll probably need to get rid of my FFB2 and just buy something else.

I've had 2 G940s now that overheat regularly while flying for about an hour. The force feedback cuts out and will not return until I quit the game and let it cool down for a bit. I'm waiting to see if Logitech will suggest yet another replacement product, or if this is just an inherent "feature." Apparently there IS a temperature sensor that will kill FFB if it gets too warm, but it shouldn't be constantly activating when flying for only an hour. Lots of people plan flights that last 10 hours, this sort of failure is unacceptable.If I can't get my hands on a working G940, there's no way I'll recommend this system to anyone.

Hey, I'd like to know something specifically about this system before I make a decision to buy it.Allowing for expected variance in the "realism" of the feel of this, since it is a PC game peripheral, does the force feedback allow you to feel the resistance on the stick decrease when adjusting elevator trim? The ability to feel yourself trimming the pressure off the controls is something I really would love to experience, and I want to make sure that the FF on this stick behaves in that manner.Thanks