Ian P

If you are using individual throttles per engine then yes, the commands would be "Throttle # Decr" using the button commands. Personally, I use "Throttle # Decr Fast" (the exact wording may be slightly different, I'm not on my FS PC to check), but both should work. The only addition I have, as I said above, is that on button release, I have "Throttle # Idle" set without the repeat box ticked. Without that, I sometimes needed a lot of forward throttle movement to get FSX out of reverse thrust. Once you hit the idle detent on a Saitek quad then there is no further analogue movement detected - below that, the lever only activates a button. This is different from the CH TQ, where the rotary movement continues in addition to activating a button at idle plus a button in the reverse detent. All the best, Ian P.

If you do decide to follow the option of using "Decrease throttle fast" with repeat to get reverse thrust, in my experience, it's worth setting the "On release" option to be "Throttle Idle" as well, because FSX sometimes doesn't seem to see the throttle moving out of the reverse detent until you are actually applying quite a lot of forward thrust instead. It seems to be an FSX thing rather than the throttle quad itself, because a similar arrangement works fine on other sims. By setting the "on release" function to be F1, the moment you move the throttle(s) out of the reverse detent, the engine is returned to idle thrust and then recognises forward movement correctly. Ian P.

Moved to Pete's Support Forum. Ian P.

I would have thought this could possibly be done using profiles? If you keep both connected, or allocate specific IDs to the controllers, then you should be able to allocate the controls independently. Take a look at the manual section about aircraft profiles and see if that helps. Best of luck! Ian P.

No, they don't. We need a lot more information from Shaun to be able to offer any sensible advice. The buttons are "tags". If you press them, in theory, you get a list of other posts which have the same tags. It may be a useful tool, but most people don't use it, so it's a little bit wasted. Ian P.

Immediately below the thread title: I've asked Miguel to take a look at it and talk to technical. Ian P.

He's put "FSUIPC The weather Fsx PMDG Aircraft" as tags at the top, Pete. They're not very clear. I'll ask Miguel to speak to the tech types about that. Ian P.

It's in your simMarket account history. If you can no longer access simMarket because of your change of e-mail address then you will need to speak to them about that, unfortunately. Apart from at the very top, in the form of the boss, simMarket and simFlight have totally different staff. Ian P.

If you log in to your account at simMarket, which you used to get your license in the first place, all the details required will be in your order history there. Cheers, Ian P.

As much as I love the flags, I think I'll look into the programs that Pete has suggested. The ultimate plan is to try and backdate as much of the UK as possible to its pre-1960s condition, so multiple scenery.cfg files are just part of the problem. It'll also need a couple of other files (autogen, vehicles) to be modified as well. Plans don't always go as, well, planned. Having multiple scenery sets that allow use of the UK2000 Xtreme sceneries, the ACG Duxford and suchlike in a modern setting, but then drop back to my WW2 sceneries without the modern ones when that's preferred, is a good start though. Anyway, that's getting off topic, so I'll shut up for a bit. Ian P.

Yes, that is something that has been bugging me for some time as well. I wonder if one of the umpteen developers who make little programs that do useful things could make us one that allows us to save, restore, create blank and copy scenery.cfg files in a controlled way? (It's not a problem for those of us who know our way around Windows, but a lot of people don't show file extensions, let alone know how to change them safely.) Hmm... I might prod a few people about that. Ian P.

Odd. <_< I've just sent you an e-mail via my webhost's mail server rather than simFlight. Can you let me know if you get it, please? Cheers, Ian P.

Thanks Paul - that makes more sense. VB is one of the few programming languages I have ever used to create something that actually worked, so have poked into its use with FS8/9/X on a few occasions. Pete: I've replied to your e-mail (twice, in fact - once before and once after a lot of searching on the support forum). Cheers gents. Ian P.

It's a Visual Basic Script, Pete - but I didn't think FS recognised VB Scripts, either, Paul? Don't they have to be compiled? Ian P.

Microsoft Flight is... more rumours than fact at the moment. They've announced it, they're putting up the odd pic or video (all only showing Hawaii and GA aircraft, which leads to more conjecture) but they're saying next to nothing about it. From talking to a lot of FS developers, the answer seems to be that whatever Flight turns out to be, FSX is far from dead - although FS9 support is now starting to die out because it simply cannot do what FSX can. That doesn't make it a bad simulator, or mean that people should stop using or developing for it, though. As you pointed out above, it can be a lot smoother performing sim for many people and in some areas (particularly airliner flying) it is probably still better for many people than FSX is, because of the range of add-ons available. Personally, after using FSX, I've tried to go back to FS9 several times and every time I've uninstalled it, but that's my personal preference. The important bit is that my rig is a lot slower than yours (i7 at 2.40GHz, albeit overclocked by the mobo when a load is put on it), but I'm flying over the US in heavy clouds generated by Active Sky Evolution (meaning multiple layers), in a very complex aircraft (A2A Accu-Sim B-17G) and I'm getting almost 40fps. I find FSX perfectly flyable down to around 15fps personally. Below that, it starts getting very choppy and difficult to control accurately. Cheers, Ian P.

FSX was developed (a mistake, as the developers later accepted) as a single core application, assuming that core speeds would get faster rather than multiple cores become the norm. It was patched to use multiple cores, although really not very well and will never be a true multi-core application. You should still get a lot more peformance from your rig than you are. Can I suggest running your FSX.cfg through Jesus Bojote's tweaking tool (http://www.venetubo.com/fsx.html) and seeing what that achieves? Ian P.

Hi gents. I am presuming here that you are only trying them inside the sim, not using Windows calibration, as I had exactly the same problem and it was caused by FS, not Windows driver, settings. Inside the FS Settings/Controls page, check the "sensitivity and null zone" options. If it is set to "Simple Controls", change it to "Advanced Controls" and then for each of the six settings below, set Sensitivity to maximum (slider fully right) and Null Zone to minimum (sliders fully left) - remember that you'll need to scroll the section down using the bar immediately adjacent to Null Zone to set all six. I don't believe FSUIPC should look at these settings at all - Pete would have to confirm that - but that was the fix that I had to use to get the CH quad to calibrate correctly in FSX. You don't mention which version of Windows (or FSUIPC - Pete will need an exact version number) you are using, but Windows 7 detects them all as non-centering. With earlier versions of Windows, you may well need to install the CH driver software to use the device correctly, as certainly Windows XP (I can't remember on Vista, but can test to find out, as this notebook is Vista 64-bit) does not recognise the device correctly. Ian P.

Hello, I can't help directly as I no longer use FS9/FSUIPC3 - however I do have a Saitek Cyborg X stick, which I have successfully used with Windows 7 and FSX/FSUIPC4, so I don't think this is a general problem with Win7 and the CyborgX. Pete is currentlt away, but will respond as soon as possible when he returns. Best regards, Ian P. sF Forum Admin Team.

Hi Bob, You have, unfortunately, purchased an FS9 license key for WideFS6, not the FSX version. WideFS6 (http://secure.simmarket.com/pete-dowson-widefs6.phtml) goes with FSUIPC3 for FS9. As it says on the product page: REQUIREMENTS FS2000 FS2002 FS2004 FSUIPC3 WITH KEY ISSUED TO THE SAME NAME IS REQUIRED &gt;THIS VERSION IS NOT FOR FSX NO REFUNDS GIVEN! FSX VERSION AVAILABLE SEPARATELY HERE The version you should have purhcased is WideFS7: http://secure.simmarket.com/pete-dowson-widefs7.phtml All I can suggest is that you raise a support ticket with simMarket and see what they can do. Unfortunately although simMarket funds simFlight, below the top level our staff are different, so you will need to contact them directly. There's nothing I (or Pete for that matter) can do personally to help. A Support Ticket for simMarket can be raised using the "Contact Us" button at the very top right of sM's pages. Ian P.

Have you confirmed that you purchased the correct version of WideFS for your version of FSUIPC? Not saying you haven't, but it is worth checking! Also, please try copying and paste all the details, rather than just the key and let us know how you get on. Cheers, Ian P.

Hi Michel, If you log into your account at simMarket and look at the the order you placed for FSUIPC, it should give you an order status. If that status is "delivered", opening the order should include your software key in the details. Best regards, Ian P.

That will only apply to the LDS767, though. It won't help with any other model. I've just thought of another example that you'll have problems with - FeelThere/Wilco also use their own FMS code. Sorry! :neutral: Ian P.

The problem is that a lot of complex aircraft - such as PMDG, LDS, Captain Sim - do not use the default autopilot. To be fair to them, this is because the default FSX autopilot is pretty diabolical compared to modern Flight Management Systems. What they do instead is code their own autopilots from scratch, which are then activated using their own autopilot switch - the FSX autopilot is not called or used in any way, which is why the offset cannot detect when the autopilot is on. Some developers, such as Level D Simulations, provide SDKs that give out the information as to what is needed to engage/disengage/change settings on aircraft functions. Others (CS, PMDG) do not. In those instances, the only way I am aware of that you will be able to detect or change the setting of an autopilot is to find out which LVar (Local VARiable) setting is used by the developer and directly read from that. Ian P.

I'm sure the simMarket system used to e-mail you the code with the order confirmation - can you check that, please, and let me know if it is there as well or not? If it isn't, I'll check with someone from simMarket whether that's intentional or not. Glad you've got it anyway. All the best, Ian P.

Check your account at simMarket - the order for FSUIPC will have the registration number in the order details. Ian P.