Simobubs

Yep , I have the same issue in London.

Any news on the new driver?

Great shots! As someone who holidays there nearly every year , and as one who has spent considerable time watching the aircraft take off from the taverna behind the threshold, the 74 would wipe out those folk in the penultimate shot. .I nearly sh*t myself when a heavy old MD80 held onto it's brakes for about 10 seconds to get up to full power. My windscreen was busted and my son ran away crying! If you get a chance to see it for yourself, do. You wont see/feel anything like it anywhere...(there are some bits on youtube). The scenery of this Aerosoft airport and indeed the whole island is outstanding. Probably my best FSX scenery purchase ever( and believe me I have made a few). I just feel Majestic's Q400 may be a more sensible ship to use ?..........

Hi there. This can be a bit tricky and lots of people give up on this but it is really good once it is working. Are you using Windows 7? If so, plug it in, go to control panel, Hardware and sound, Devices and Printers. It should be shown in this section. Right click it and go to game controllers settings: highlight the trim wheel and click properties. You should then be able to see that the wheel is being "seen" and be able to test the movement.. If this is not happening, there is something wrong with the hardware. If it is working, there is a problem with the way it is set up in FSX. I use FSUIPC for all my axis.

Thanks for letting us know Noel. I am sure that they wouldn't bother fixing these things unless people like you made the proper case for it. I for one will be very grateful for new driver if it does the right thing! As my set up is very similar to yours I expect we can both hope for a similar result. Cheers

Hi Wayne. I'm jealous. Any suggestions for us then? Do you use the Saitek driver?

No I don't use the SST software as I feel it is really not necessary, especially for the trim wheel which is just a single axis. To be honest, you may have to spin that wheel quite a few times before it gets recognised ( spin the wheel in one direction say 10 times and then the the other way). You'll hear the windows ding when it's found. Annoying as Hell but just becomes part of the startup routine. To be honest, it's probably just a quick if not quicker to unplug and plug it in again if that works for you.....Let me know how you get on.

I have exactly the same issue. I deal with it by spinning the wheel a few times when I am in fsx and windows will then "find" the wheel. I would point out that I have it connected in fsx via FSUIPC registered. As for why this happens, I am clueless. All my other Saitek items, yoke,rudder, throttle quadrants, X52, do not display this behaviour. Guess it must be to do with internal components making the wheel passive until moved.

Haven't created a profile for the trim wheel, nor have I for the Saitek pedals and X52 that I use, just use FSX controls settings to bind axis and buttons.All work perfectly well APART from the trim wheel. In the meantime, until I can find an answer, using A and B buttons to control trim. Don't like the idea of using the FMC settings; can't see how this would work at all with a wheel that has a 9 revolution limit...Anyone else?Sim.

Hi,I have the same hardware and have not been able to get it to function properly with NGX. Have same problems as ViperXBR. I don't have registered FSUIPC so can't blame that. I have installed saitek driver and calibrated from their control panel but to no avail. Works ok on other addons so guess must be an incompatibility with NGX. Shame, just bought it....and really nice to have such sensitive control for manual flying, which I love to do on occasion.Might have a look on the saitek site see if there is a forum there..?PS: have Sp1 and all looking good apart from above issue so far