Andydigital

Try turning down the key repeat rate in Windows itself, it helps some people. Another tip is to press the buttons harder otherwise you can get button bounce. If you don't know where to look in Windows just type "keyboard" in the Start button search box.

Precisely so it's not free at all.

If Windows can see your devices in the bog standard game controllers/calibration software then Linda can deal with any joystick, yoke or throttle, it doesn't matter who manufactured them, but it only processes the buttons and dials on those devices, it has nothing to do with axes.

FSBuild is ancient, ugly and a million miles away from being user friendly though. In its day it was awsome, but that day has long since passed in my opinion.

It's probably easier to list the ones that cant, and I cant think of any, certainly not any that are worth bothering with anyway. To be honest the only flight planner I would recommend now is PFPX and that most certainly can load FP's into the NGX.

Not going to happen in the near future that's is for sure, FS9 doesn't need its weather engine hacking so much to get it to behave properly, Pete Dowson already fixed it for the most part in FSUIPC. It's FSX that has serious bugs in its weather engine not FS9.

Three islands not just one or part of one, but three. B)

The easiest way to clear key assignments it to reassign them to a cleared item at the beginning of the list. I always use one of the ADF functions at the start of the list that has nothing assigned to it whatsoever. So assign the key you want to free up to this ADF function, you will then get a warning if its already assigned and it will tell you what its assigned to, if you click on OK it will remove the old assignment and reassign it to the new ADF function you just chose. Now simply delete the assignment from the ADF function and voila you are done. It takes a lot longer to explain than it does to actually do it, lol.

Actually the weather engine can easily fix the problem with runways changing when the wind direction is close to 90 degrees to the runway and variable, you simply lock the wind direction and set a minimum wind speed of 6 knots, AS2012 already does this perfectly, its called ATC Wind Lock.

So there is no terrain feature like there is in the RXP GNS devices, hmmm so this isn't the saviour I was hoping for for P3D, oh well its getting there I suppose.

The button that is activated at the bottom of the levers action on Saitek Quads is not actually a real button inside the hardware, it is a virtual button in the firmware that is activated when the throttle handle gets below a certain value in its range, this range is not visible to Windows either. If the potentiometer for that throttle lever is getting old or dirty due to extended use then the signal from it starts to become erratic and noisy, so it appears to jump around even though the lever itself is not moving. This jittery motion can take the stick out of this virtual button range in firmware and this makes it look like the switch is been turned on and off. And this ultimately is why LINDA switches to this button all the time because it thinks you are pressing the button. There are tutorials on Youtube that show you how to take the throttle apart and clean the potentiometer with Contact Cleaner, I did this a couple of months ago and my two quads are now working as good as new again.

I'm not 100% sure no, perhaps it was just a fond memory, lol. It may even be that I just got used to the better frame rates in the 777 and the other GA aircraft I have been flying lately and that contributed to a better overall performance from the sim. The NGX is a bit of a pig performance wise now, it's especially noticeable how unstable the frame rate is compared to the 777. With the 777 it's pretty much always constant, with the NGX its varies as much as 30% almost all the time even with a locked frame rate. Thanks again.

That's more or less perfect now Artem, not quite as fast as it used to be, but still very good. Thanks.

DME 1 is now OK, but DME 2 is worse now and doesn't update at all until about 2 seconds after the CRS has been set in the VC view. Oh yes and by the way it still says Powered By Linda 1.1 on the radio panel at startup rather than 1.13 ^_^

I'm having problems adjusting CRS on the DME part of the radio in the MCP2 with the latest version of LINDA (1.13) the display on the MCP2 lags behind the aircraft sometimes so it makes selecting the correct course really difficult, you have to look at the panel in the VC to adjust it effectively. This was never a problem in the past.

I've no idea about the F1 King Air as I do not own it, so I cannot really advise what should work and what wont. A module being included in Linda just means that someone has gone to the trouble of adding support for an aircraft that wouldn't work with the default FSX controls in Linda. It doesn't automatically mean that if your aircraft has no module that it should just work with LINDA, it's not that easy, sometimes its a case try it and see. Other times you need to read the manuals and do more research of your own at the forums for the aircraft in question, there is also tonne of information in this forum area too.

Yes that is what the FSX default profile is for in Linda. Make any assignments you want to work with all aircraft in the FSX default profile, then add specific assignments for special aircraft too their own individual profile.

Actually I didn't realise we had had the original Duke for that long, I suppose I was a little harsh for the small upgrade fee involved. I still think its a plane only its mother could love, it just looks like it shouldn't fly properly to me, lol.

To be honest I do not see the point of this upgrade, its sound more like Duke 1.5 to me and I am a big RealAir fan, I own the majority of their products. I suppose they will do the same thing with the Turbine in a couple of months and charge for that too. Please don't turn into Carenado, I hate them for doing this kind of rehash thing and simply voted with my wallet, I'm sorry to say I'm doing the same with this I am afraid.

All the documents are in the FSUIPC Documents folder, the path would be something like the below depending on where your FSX is installed. c:\FSX\Modules\FSUIPC Documents\

The most important thing is to make sure that your fans are designed to work in close proximity to a radiator, if they aren't designed for it the blades will stall and become inefficient when blowing into a radiator, its the same when sucking the air through but its not quite as inefficient. I have my Apaches sucking air through the rad at the top of my 800D case.

Which aircraft? I may be able to help. I use two of my levers as the fuel controls on the PMDG NGX and 777, but I do it directly in FSUIPC via key commands in the Axis Assignment tab. So when the lever is in the top half of travel it sends one key combination and when in the bottom half another key command, there is no reason why you could not fire an L:Var, FS Control or a Mouse macro instead. There are examples in the FSUIPC Advanced manual I think, I must have used them myself at some point. You wont be able to do it in Linda though as it doesn't process Axes at all.

That g3d.dll error has got absolutely nothing to do with the problems discussed in this thread, that is caused by faulty scenery or corruption of data on disk and nothing to do with the menu interaction crashes.

A touch screen monitor beats it, lol, costs you nothing if you already have one, I still prefer my VRinsight CDU2 though.

I cleaned the pots on my pair of 3 year old Saitek quads a month or two ago, took me about 2 hours in total and they are like new now, I'm sure I'll get another 3 years out of them before they need another clean. Even if the pots need replacing then it wont be a major job to do it.