Pete Dowson

Not true. I am using it frequently with FSX and P3D. It interfaces to FSUIPC3 or FSUIPC4. And the same version of FSInterrogate (FSInterrogate2std.exe) has been supplied for a long time. Pete

Some add-on is causing the problem. You would need to go through a process of elimination on the assorted additions to find it. Bear in mind that many add-on aircraft, not just PMDG ones, have their own DLLs loading. Sometimes the order of them is important. You can check this and change it in the DLL.XML file. Pete

Well, as they said, it's something about the way they programmed it. Why not stick something non-slip under the pedals, like Velcro or a rubber pad, or rubber feet even? Pete

Well, assuming that model actually reads and uses FSX values for N2% and doesn't just place them as results of throttle setting, which would be more usual I think,then you can assign your three keys to the FSUIPC offset controls - in this case Offset word set with the value as parameter. On the other hand I would have thought it would really only respond to throttle settings, so Throttle Set or ThrottleN set controls with appropriate parameter values would be more usual. You can experiment with different offsets using FSInterrogate, a useful program included in the FSUIPC SDK. Regards Pete

It sounds like QW have done their own thing with the main flight controls and are intercepting them at a higher priority level in SimConnect. If you've assigned them "direct to FSUIPC calibration" then this will certainly by-pass that level. FSUIPC's calibration does the same thing -- intercepts controls at the higher priority level and feeds them back at the lower (the reverse way would end in an infinite loop). So, try assigning those three axes just to the FS controls, Axis ailerons set, etc. I'm afraid that if this is indeed what QW are doing then you will find calibrating them in FSUIPC will either not do anything, or may even stop them working again -- depending which app intercepts first. You may need to go and press the "reset" button in the three calibration sections. Since the axis assignments are Profile specific, this change should not mess up anything else. Regards Pete

It will be a false positive. Just ignore or bypass the warning. Pete

Sorry, I don't know how to incfluece the colours or fonts in those dialogues. It just uses a facility I happened to find in FS. There may be ways of doing it, but not ones I know. Pete

That makes no sense. If FSUIPC was only detecting "on" and not "off", it would only ever detect it once and never again because it wouldn't see it "off"! If you are referring only to the switches and buttons assignments tab, then, yes, that only shows the change from off to on because that's all it needs to do -- you assign both on and off actions then, on the same page. Pete

Which control are you wanting to calibrate? There's no mapping on the first page for anything other than the throttle. What is it you want to do? Pete

Thanks. I've posted this in the FAQ forum. Pete

It appears that many users have problems with Saitek Quadrant drivers setting up the Registry incorrectly for one or more of the levers, with the result that either only 50% of the range use used or the values you get are only on (max value, 16383) or off (min value 0 or -16384). Here is the way to edit the Registry and fix this, at least until Saitek fixes their installers. (Thanks to a main forum reply by "goaround"): ==================================== Here is our registry calibration guide: One way to re-calibrate your device is to reset the raw data values that are held in Windows registry. To do this: 1. Remove the USB plug for your controller from the PC. 2. Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box. 3. Type regedit and then click ok. For Windows Vista/7/8/8.1 4. The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name. + HKEY_LOCAL_MACHINE + System + CurrentControlSet + Control + Media Properties + Private Properties + Joystick + OEM 5. Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID. 6. Then navigate to the DirectInput folder + HKEY_CURRENT_USER + SYSTEM + CurrentControlSet + Control + Media Properties + Private Properties + DirectInput 7. Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID. 8. Once deleted, close the editor, then plug the USB back into the original port. Move all the axes of the controller through their full range of movement four times. This will rebuild the data range for all axes.

For FS2002 and FS2004 there is a facility in FSUIPC3 to stop the automatic fuelling action at fuel pumps -- "StopAutoFuel=Yes" in the INI file. But I never found how to do this in FSX, and to be honest no one ever asked either. To do it in Lua you'd probably need to have an offset event on the fuel tank values, and if the value increased when it wasn't done by your own code (ie in this Lua) restore the previous value. You can use other Lua facilities to detect a switch, keypress or button and prompt for a fuel value, then load it immediately, or more realistically, slowly increase the value till the requested amount was provided. Pete

As well as what Ian says, please note that version 3.71 is not supported! Only up to date versions are supported -- you nbeed to download and install 3.999z8 or later. Pete

I assume this is all about the range assignment facilities in the Axes tab. That facility, to have different controls sent for different parts of an axis range is rather specialised. The control actions you are trying to assign are almost always implemented by switches or buttons and direct assignment there, not using levers. However, that said, you simply do there what you want. Normally set the options first, then the positions. No, there should be no interaction at all between different assignments on different axes. Each assignment results in different lines which are first placed in an internal table and written out to the INI file when you OK out of the dialogue. If this doesn't appear to work for you I'll need to know the exact sequence of your actions so I can see what is going on. Pete

I've never heard of any issue with brakes like this before. Assignment in FSUIPC to brakes just uses the standard FS brakes controls -- left brake, right brake for differential and "brakes2 for both (same as the . key with default FS assignments. But why does it matter much? Surely if you have brake pedals they are used for all braking purposes except parking brake? When are you needing the default brakes button? Pete

Two points: First, these problems seem only to happen with Saitek stuff. You need to check their drivers -- go to Saitek support, see what they might have said about them. Second, there is no way installing an aircraft add-on can interfere with FSUIPC's axis detection unless it is capable of doing something to the Windows system itself and/or Saiterk's drivers, because FSUIPCX detects axes for assignment directly through Windows facilities, not via FS or any add-ons. Maybe you are confusing the detection of FS controls (in the Calibration tab) with true axis detection which only occurs in the Axes tab? Pete

Thank you for your very nice message! I am glad FSUIPC is so useful to you. Regards Pete

Sounds like you are assigning it in a way not compatible with whatever add-on you are using, and some other control is interfering or countermanding its input. However, nothing like that could possibly occur with no changes to hardware or software -- obviously something has changed. You'd need to track it down. If you are assigning in FSUIPC (is that what you mean by "mapping"?) and not simply calibrating in FSUIPC (the two actions are separate and independent), then you MUST disable controllers altogether in FS itself or it will occasionally automatically re-assign axes and this causes conflicts of the type you describe. Of course you do not NEED to assign in FSUIPC -- calibration works however you choose to assign. Pete

If you do post it I will put it as an item in the FAQ subforum. Thanks, Pete

This is an often reported problem which is caused by a bad Saitek install action in the Registry. It can only be corrected by a registry edit. You should find help on the Saitek forum, or else ask their support. I think it is because the axis is defined as a "digital" one, meaning it only has two values -- off and on! Pete

Well this must surely be down to poor programming in the JS4100. The full range of your throttle control should go from full idle one end to full thrust the other. If it is reaching full thrust after only a small movement then either your throttle is simply not calibrated properly or there's a bug in the aircraft programming. The only way sensitivity can be reduced over the complete range of thgrottle movement is by editing the FSUIPC INI file and changing the max calibrated value for it in the calibration section. For instance doubling it 9eg from 16000 to 32000) would halve the sensitivity. but the result would be that when the throttle is full forward you only get 50% thrust That is, unless the JS4100 is programmed that badly that 50% thrust input gives 100% output! You can of course change the sensitivity over part of the lever movement by using the "slopes" option in FSUIPC calibration. You can make it less sensitive at the lower end, but that's at the cost of making it more sensitive at the upper end. You can't have one without the other if you are going to be able to have the full range. Well in that case you've never used a throttle axis for separate engines. The only other controls are Throttle set (all engines) and axs throttle set (all engines).. FSX assignment uses Axis throttle set or Axis throttleN set (N=engine number). For revere zones FSUIPC uses ThrottleN set because you can't get reverse on Axis ... controls. You have already been using ThrottleN set if you've been using the 4 throttles calibration. How many throttle levers do you have. If just the one, and you are not using a reverse zone, just assign tothe normal axis throttle set and calibrate on the first page, for all engines. Pete

Well 44 should work, but it may be getting intercepted before Teamspeak sees it, depending on how it reads the keyboard. But the ability to distinguish between the two shift and control keys needs a different way of programming in FSUIPC. I'm not sure how to do it offhand. Why do you need to change? If it works as it was, why not let it be? Pete

Sorry, I think this must be a question for iFly support. FSUIPC just passes the result of your assignments on. What happens then is another matter. Pete

;-) I wouldn't be surprised! They'll have three weeks this time -- I'm not back till 26th. Pete

No, sorry. I rarely had any problems with sudden wind changes. I think they happened mainly in specific areas of the world where the triangulation system used for weather interpolation went wrong -- I seem to remember the area around Chicago fairly prone, and somewher in south Holland (Rotterdam) where one station in the triangle appeared to be down in Africa! With ASN all those problems have gone in any case. Pete