peterhayes

Hi Jahman I see that you are having issues with your CH controller and assignments. I wrote the appendix (which PeteD generously added to the manual) as a step by step guide to a particular option in FSUIPC4, that a "newbie" could follow - it was really just to enhance and expand in a step-wise fashion PeteD's instructions in the manual. :razz: I myself have a CH Yoke plus pedals and have no problems in FSX/FSUIPC4/CHCM. This is what I do: I do not use CHCM in "MAPPED" mode as I believe that there are some interactions between that and Win 7 calibration and may be with FSUIPC (BobC disagrees with me on that latter point). If I use CHCM I use it in "DIRECT" mode so that I can set the null zone exactly at the detente on the TQ6 and that corresponds nicely with the calibration settings in FSUIPC4 and so you get the reverse thrust occurring exactly at the start of the detente down to the minimum setting, and vice versa. I know that you have said that you did not use the windows calibration - but I would still follow BobC's advice and use the "reset to default" (or the Logitech cleaner) option in FSX joystick calibration, so that all calibration settings in Windows are reset. I would also back up both my fsx.cfg file and the fsuipc.ini file and remove them one by one and then let FSX re-build a new cfg file and FSUIPC re-create the ini file. (Yes, it is a pain but it can resolve lots of issues). I would also check the current in-use standard.xml (in the system disk\user\username\appdata usually) just to make sure there are no issues there? Sometimes you get "greyed out" buttons in FSUIPC when you are not expecting them, so if I see that I just "wiggle" a lever or the yoke and that can fix that problem. The CH game controllers don't alweays make themselves known when in an "idle" state and a "wiggle" wakes them up. :rolleyes: If none of this or Pete's/BobC's advice works try changing the USB port hub (eg lots of USB issues in Win 7) or re-plugging the controllers in after turning off the computer, removing the power cord for several minutes, perhaps with a "clean boot" or suspect a hardware fault. Regards PeterH

John If you are using FSUIPC4 with FSX you should not need the SST software for something like the Baron. You have checked your senitivities and null zone in FSX (Sensitivity full right/null zone full left) Regards PeterH

Hi John It should be in the Program Folder (maybe x86) - I haven't installed it for years so my memory is hazy. But there should be a shortcut to it (probably on the start menu too) and it only affects FSX if you initiated it to do so. You could use Belarc adviser to see what software is installed and it would show up there. If you have win XP 7/vista it will be listed in the "all programs" button. You would remember if you installed it because you have to assign axes and buttons before you can use it. I would say that you do NOT have the SST software installed. Regards PeterH

John Saitek have 2 pieces of software: 1) Drivers (see Ian P's reply above) [in Win 7 I have found these to be unnecessary] 2) SST programming software - when I wrote the appendix I found thet there seemed to be issues if used with FSX and FSUIPC4 and as the latter is excellent at assigning and calibrating axes etc, I uninstalled the SST programming software. I didn't notice any issues with the drivers. However the SST P S is now a later version so things may have changed. Regards PeterH

John Are you assigning in FSX or FSUIPC4? Just make sure in either case that the axes are not assigned (duplicate) in both FSX and FSUIPC4 and if you are running the SST software (not drivers) that can interact with FSX/FSUIPC4 wrt to duplicate assignments. In fact, always check for duplicate axes as FSX can be sneaky and assign axes in any of your controllers including the mouse. PeterH

Pete Thanks for taking the time to reply. Regards PeterH

Hi Pete Hope you are well - just a question: Just a thought on the updating of your various modules. You, quite rightly, extol us to use the latest versions of your software but the actual process of seeing if there is an update can be quite confusing. On the modules sub-forums tab: the "Download links" shows a date of 17 January 2011 for FSUIP client dll for .NET. Click on download links and under 'Updated Modules' the date is 25 January 2011for FSUIPC 4.657 and 3.989 w . . . , but on the 'Last Post Info' the date is Oct 19 2010. Is there any easy way to flag on the modules sub-forum download links a date that is for the latest of any download? With regard to the 'Updated Modules' tab could this be changed to 'Updated FSUIPC/4, Wide Client, PFC /FSX Modules'? Just a thought these changes might make it easier to update the module at the correct time. I fully understand if this is quite difficult to achieve under the new system. :???: Regards PeterH

Pete & Andy Thanks - I did remove the Logitech software - should have said that and rebuilt all the appropriate ini and xml files. I had to remove the G940 as I couldn't fly the VRS bug with any degree of accuracy. PeteD - I will reinstall the G940 in the next day or so and send the logging files. Thanks for all of your help. Regards PeterH

Pete Recently whilst you were away I had purchased a Logitech G940 system Initially I use the Logitech software and FSX to set up the controls in FSX. However, I experienced a lot of issues in terms of controller settings and sensitivities, so I decided not to use the Logitech software (disabled it) but instead use a mixture of FSX and FSUIPC 4 (4626) to assign and calibrate the various axes, keys and buttons. No problems in any of this in FSX. I then started FSX and then opened FSUIPC4 and went to "Axis Assignment" just to make sure that I hadn't any duplicate assignments. However, when I moved any of the G940 axes (eg ailerons, elevator, rudder, throttle) it changed the FSUIPC4 menus ie it moved randomly away from "Axis assignment" to another menu: eg it moved to "Winds" or "Visibility" in fact any of the menu choices but it would not stay on the Assignment page and show any details. No matter how many times that I re-chose axis assignment and "rescan", any axis movement changed the FSUIPC4 menu. (Rebuilding the FSX.cfg, standard.xml or FSUIPC.ini made no difference). In FSUIPC 4 calibration the axes assigned in FSX were recognised and I could set all the 'normal' calibration values and movement of the axis did not change the menu. As you were away and I had a lot of other issues with the G940, I removed it from my system and reverted back to my Saitek X-52 joystick which performs flawlessly and doesn't change the menus in "Axis Assignment" in FSUIPC4. Unfortunately, I did not keep any log files, etc. Really my question is - Have you seen behaviour like this before? Is there a simple explanation as to why it might have happened? Thanks PeterH

Brad You do NOT need to use the SST (programming) software just FSX, and FSUIPC(4) if you need the extra extensive commands. The Saitek driver software is useful to have as it gives quite a bit of info if you want to initially calibrate in Windows. If you do use the SST programming software try to make sure that you do not have any duplicate assignments in it and FSUIPC. I just use the driver software, FSX and FSUIPC4. Regards PeterH :rolleyes:

BA1 Just a thought Pete is NOT the trusted publisher it's actually "Simflight", so you usually check that to get rid of that error. viewtopic.php?f=54&t=78080&p=475732&hilit=PeterH#p475732 Regards PeterH

Garry One thing that I forgot is that you may have an overwritten and now corrupt dll.xml file due to installed software. Pete Dowson can help you with that. Regards Peter

Garry It should work OK but it might be worthwhile posting on Pete Dowson's (the developer of FSUIPC4) forum. viewforum.php?f=54 You may have a "simconnect" issue. Regards PeterH

Gary You may need a little more info, FSUIPC X when it installs into FSX it installs a FSUIPC4.dll in the main Microsoft Flight Simulator X\Modules folder You will also find there: FSUIPC4.ini, FSUIPC4.key, FSUIPC4.log, FSUIPC4 Install.log plus FSUIPC documents. If the FSUIPC4.dll is present and it has installed correctly then it should show as an addon in the FSX menus. As Burkhard says the dll.xml file in the System drive C:\Yourusername\Appdata\Roaming\Microsoft\FSX\dll.xml It should have a fairly recent date. It should have an entry similar to: - FSUIPC4 False Modules\FSUIPC4.dll The dll.xml will be in a different directory and folder to the FSUIPC4.dll As Far as I understand it neither the dll.xml and FSUIPC4.dll have anything to do with DIRECTX Good luck :D PeterH

Scott Check in FSUIPC that you do NOT have checked "Keep FS Clock Synchronised" pp 22-23 FSUIPC4 manual. May help Regards PeterH

PeteD Sorry to interrupt but didn't Bob Church explain this behaviour in viewtopic.php?f=54&t=70574&p=438683#p438683 and I think viewtopic.php?f=54&t=71912&p=445130&hilit=bob+church#p445130 as well. Bob said: "When FS first starts, it's apparently defaulting everything to zero or whatever. FS has no data until an axis or button on the controller changes value/state and it sends a report. It should only take movement by one control on each controller, and in a lot of cases one of the values will be bobbling (127, 128, 127, 128, .....) anyway and that's enough. You're feet are on the pedals and your hands are on the yoke, it would be very unlikely that they wouldn't move by at least a count. OTOH, with the Quad, if the levers are in the detents they're dead stable because they're in deadzone, and it's likely that the endpoints are stable too so no data goes to FS and you're running on the default value until something moves. The pedals will do that too about half the time if your feet aren't on them." Apologies if this is a different problem PeterH

Pete This may totally irrelevant but on one of my systems I used to get these regular stutters if "Pause on Task Switch" was ticked FSX. The other time that I saw it (without the message bar about re-loading textures) was if "Keep FS Clock synchronised" was checked in FSUIPC via the SIM. As I say, they may have nothing to do with the problem, but are just a couple of lateral thoughts. Regards PeterH

John Just check in FSX that you haven't the same button assigned in FSX the same as in FSUIPC or to another function. Quite frankly you would be better setting the button FSX as there is no advantage setting it in FSUIPC4 (unless you have disabled the joysticks - in which case my answer above does not apply). :D Regards PeterH

Pete Thanks for the response. I did think that it would be a major undertaking - even if it could have been achieved. Regards PeterH

Hi Pete This is just a general question about FSUIPC4 and FSX: I don't know if this has been asked before but using FSX/FSUIPC4 is the following possible? In FSX when you assign an axis (and/or a button/key) in Settings, Controls/Axis i.e via Change assignments- if you choose an axis (key, button) that has already been assigned - FSX has a pop-up window that states : "This event is currently assigned to the "XXXX axis" action". Is there any way that this type of functionality could be incorporated into FSUIPC4? That is to say that if an axis (key. button) was being assigned in FSUIPC4 but was already assigned in FSX, FSUIPC4 would give you an indication that this axis had already been assigned in FSX. Another bonus would be an option on a course of action to take eg remove axis, etc assignment in FSX before proceeding. This would remove the problem of an axis being assigned in both FSX and FSUIPC4! :) Thanks PeterH

Mike You said in your first post: "I have a Logitech Force 3D Pro since a couple of weeks, it needs power in addition to a USB connection. I do not always have its power on and so the joystick is not "connected" to my computer all the time, I think." I'm not sure if Pete addressed this but every time that FS9 starts and the joystick is not connected and then re-connected it is seen as a "change" and the SIM resets all the values for that controller and it may assign spurious duplicate assignments. I use a G940 (needs a power supply) which uses similar Logitech software, so I do 2 things and I keep it powered on at all times. 1) Any assignments in the Logitech software I make sure that they are exactly the same in FS9 and I clear any duplicate assignments. 2) Any assignments that I make in FSUIPC - I make sure that those assignments are not also made in FSX and/or the Logitech software. My G940 works perfectly in FS9/FSX using the logitech software with FSX and FSUIPC/FSUIPC4, selectively as described. Pete is correct for the joystick to work optimally you must have ALL axes (some are hidden in the drop down box) Sensitivity - full right - (100%) and Null Zone full left (0%). These can be changed but I wouldn't advise it - the realism settings in the SIM work much better in this configuration. When you are setting up the joystick make sure that your realsim settings in FS9 are all full left ie "Simple", you can then increase the complexity as you get more proficient. This probably won't help but it does give you another POV. Regards PeterH

Hi Bob These points come to mind: If you are using CHCM in "mapped mode" wouldn't you say that there is little point in assigning the same axis or button on FSUIPC (unless you can't do it in CHCM) as you have already assigned/calibrated in CHCM? If you then assign in FSUIPC4 won't you have a "double assignment" and won't that cause the issues we are discussing here? Can you assign, calibrate some axes, etc in a CHCM map and also assign/calibrate different (non-duplicate) axes in FSUIPC4? If you have assigned/calibrated all of your axes via a CHCM "map" can you still "fine tune" those axes in FSUIPC4? If you have assigned/calibrated all of your axes via a CHCM "map", if you open FSX and delete say a particular axis, etc assignment, can you then assign that axis, etc in FSUIPC4 without any issues? Now if we are using CHCM in Direct Mode as long as there are no duplicate axes in FSX and FSUIPC4 then everything should be OK? Regards PeterH

Hi Pete Thanks. In vista I used certmgr.msc and now under publisher simflight is now added. Regards PeterH

Hi Pete Thanks for the reply. In my Vista 64 install you are already set as a "trusted publisher" in Vista\Internet Options\Publishers . . . Eaglesoft are also there but if I load one of their new planes, I know that I will be asked by FSX to "trust" the gauges in the plane. There must be another setting somewhere that I haven't found. I shall keep digging and report back if I find something. Thanks for your help Regards PeterH

Hi Pete If the publisher details are added to the Trusted list in Windows (not in FSX.CFG) then you never again get that prompt. The publishers are listed in one of Internet Explorer's menus -- there's a "trusted" list and an "untrusted" list there. In the Internet Explorer's security tab there is a choice for "trusted" sites (and untrusted) but what would you put in the trusted site to cover FSUIPC4.dll? I couldn't find one for trusted publishers. Where would we find the publisher's name? In Vista interestingly if you right click the FSUIPC4.dll Properties and under "Digital Signatures" you get Simflight GmbH as the name of the signer, so if we added http://www.simflight.com to the "trusted" site in IE would that do it? Under the "Security" tab I had already set up full permissions, ownership, etc for FSUIPC4.dll, but you still get the request for trusted status when you open FSX after you have changed the FSUIPC4.dll file (for an update, etc). So I wonder what you have to set in that security tab to stop the message appearing. You also get this with new planes (its usually the .gau file) and it can be a real pain when you have 20 gauges like in some of the Eaglesoft planes. (yes with Vista SP2 that drop down choice for trusted status seems to have disappeared). I am going to add http://www.eaglesoft.com to my trusted sites and see what that does. I will have to some more research into this as it should be easy to "fix" it, as I don't fancy setting the security options for every individual gauge I have in my virtual hangar :D . Thanks again for the support. Regards PeterH EDIT Ah! I see how to do it in XP using the local group settings and including dll and gau as "trusted" extensions. However, in Vista it looks like you can't do it in Vista HP as there doesn't seem to be a way of editing the group policy to include dll and gau files. there is a hack on the Acrronis site but I'm too chicken to test it out. :D