Pete Dowson

Aileron responsiveness varies hugely with aircraft. A stunt plane or jet fighter responds very quickly to slight movements whilst an airliner responds much more sedately and needs quite a bit of initial aileron to get over its huge inertia. If you change the slope to make it steep around the centre area you are losing sensitivity -- there will be less different aileron positions in a given range of movement. You can't have it both ways. Most folks prefer a flattened centre, less responsiveness in terms of aircraft movement, but correspondingly more delicacy, more different positions per amount of movement. If you like you can experiment with reducing the "Delta" value in the axis assignments tab in FSUIPC. That determines the minimum input difference which will be recognised. Too small and it will be jittery, but if the unit has got a good high resolution pot you could halve or quarter it. Realistic in comparison to what? Which aircraft have you flown for real? You presumably know it will be different for different sorts of aircraft? If by "choppy" you mean "jittery", like back and forth or in jumps and spurts, that certainly wouldn't be correct and would indicate something wrong, possibly with the connections or the unit itself -- like dirty pots, poor power supply, that sort of thing. Regards Pete

Okay. Please send me the complete INI file again, then. It is really weird that the flaps lever can have any affect at all, because all that does is send "flaps inc" or "flaps dec" controls -- exactly the same as pressing F7 or F6 on the keyboard. Does that do the same? Flaps inc and flaps dec, depending on which way you press it. Certainly nothing to do with any axis whatsoever. Just a button-type assignment. This is starting to sound like a hardware or firmware problem. So you can't sohw me the one referred to above? Pete

Don't forget that you probably also need to select the "NRZ" ("No Reverse Zone" option), and also the "UseAxisControlsForNRZ=Yes" parameter in the appropriate [JoystickCalibration] section. Also, you can make this change specific to that aircraft. Pete

I don't know. I think so. You'd need to check. As it's freeware it wouldn't cost anything to try in any case. Regards Pete

If you wanted the generic (i.e. all-engine) mixture control, yes. Those are always grayed out if there's an existing assignment. You cannot change the method for an assigned axis. You would have to remove the assignment (the check on the left of it) in order to do that. If the axes don't give stable enough inputs there is something seriously wrong with the hardware. Minor flickering, as shown in the logs, is okay and quite natural. Anything worse indicates something wrong -- bad connection, dirty pot, poor power supply. I can't fix that sort of thing by software. Filtering is a last resort (it was added for a chap in the jungle in Malaysia whose power supply was dreadful! ;-) In the FSUIPC tab for joystick Calibrations. There's a whole chapter on it in the FSUIPC User Guide. It is the main reason most people buy FSUIPC. Please see my previous message, evidently crossing with yours. Now we know what is going on you should be perfectly okay with "direct to FSUIPC" assignments, and that is more efficient. but ONLY calibrate the specific axis you want to use. Regards Pete

FSCommander is the one I'd first think of. It should have a way of positioning your aircraft but whether it is by mouse on the map I don't know. Can you not find out? Other programs which include some sort of map and which may be able to do re-positioning too include FS FlightKeeper and PlanG. PlanG is freeware. Regards Pete

Okay, okay! I've managed to find the explanation for the odd automatic and incorrect assignments. FSUIPC does actually make default assignments to the quadrant axes. It only does this if there are no user assignments -- once proper user assignments are made it doesn't override them. The reason it only happened on one of your axes (17Z) was because at some stage the PFCHid driver was changed to set Quad axes only on joystick #17 but, to my shame, FSUIPC3 was not updated to match it! FSUIPC4 was correctly updated. Obviously i had intended to also update FSUIPC3 but somehow it slipped through undone. I apologise for this. I think it was because it appeared no one was using PFC Hid in any case, judging by the complete lack of feedback I got. Evidently other things came to the foreground. I failed to discover this, even though i have been testing with FSUIPC3 (not FSUIPC4) simply because my own assignments took precedence. The original mapping for the 6 quadrant axes, together with their intended default assignments, was as follows (left to right): Q1 = 16V -- Throttle and Throttle1 Q2 = 17R -- Throttle2 Q3 = 16U -- Prop and Prop1 Q4 = 17Z -- Prop2 Q5 = 16R -- Mixture and Mixture1 Q6 = 17Y -- Mixture2 As you can see, the default assignments were ideally suited to the full twin prop quadrant. However, in the updated PFCHID module the actual joystick axes set by the Quadrant are as follows: Q1 = 17X your carb heat Q2 = 17Y Q3 = 17Z your throttle Q4 = 17R Q5 = 17U your mixture Q6 = 17V and thus your Throttle lever was auto-assigned to Prop2. Neither of your other levers were auto-assigned because they aren't auto-assigned in the incorrect un-updated FSUIPC3! Conclusions None of the above explain your so-called Mixture "spike". I feel sure this is down purely to that bad calibration. It isn't so much a spike as an upper limit of 17% being imposed by that calibration setting. So to get you "underway" I think you should simply either delete the entire FSUIPC.INI file and start again, or delete the Joystick Calibration sections, run FS, retain your newly set assignments (or make new ones -- you can even use the more efficient "direct to FSUIPC calibration" option, now we know it isn't that to blame for anything. But be sure to calibrate the three levers correctly following the numbered steps in the FSUIPC User Guide. I cannot supply a corrected version of FSUIPC3 at this moment as I am part way through preparing the full user release 3.99. I am really very very glad to have had this auto-assignment problem identified so I can fix it before that Release. However, I'm sure you'll be okay with proper calibration. Please, however, do update to 3.99 when it becomes available. Good flying! Pete

Yes. And that doesn't have the [Axes] heading at the end like the one you last posted here. I'm not understanding at all why its contents are changing so much each time you post one. One thing I have noticed. In the calibrations: LeftBrake=-16384,-16384 RightBrake=-16253,-16253 Rudder=-16380,-512,512,16380 Throttle=-16128,16383 Mixture=-14592,-10752 The LeftBrake and RightBrake calibration is set with the Maximum = minimum, so those won't be much good. The Rudder seems to still have default calibration, not anything set by human, and the Mixture calibration has a reasonable minimum but the maximum seems to be set to that 17% you keep seeing. Your Windows-defined joystick numbering is as follows: 0=PFC Cirrus II Pro 1=PFC USB Pedals 2 2=PFC Avionics Adaptor So 1 X will be the rudder, which is evidently showing a little jitter to be picked up automatically. Was there any assignment shown? That must be the elevator on your yoke. Was there no assignment shown? Good. Which options are you referring to as "not greyed out". Sorry, I am not seeing the significance. Hmmm. This is where I don't understand it. There's something very very odd going on there. When you say "options are grayed out though" what do you mean? What options? Okay. Do you only have the three levers on that quadrant? Don't use the filter. The "spiking" is not spiking. Your mixture calibration, as shown above, is setting 17% as the maximum! I still believe, as I advised, that you should simply delete both INI files and start again. There's obviously been some mistakes made which result in bad calibrations and since you don't yet seem to have any feel for how to calibrate I think you should start off, again, and take it step by step. Meanwhile I'll think about how that "Proppitch2" assignment can possibly be generated of its own accord. I may need to add extra logging and ask for some extra tests -- but in such a case I will ask you to save your INI files elsewhere whilst running them. Er. There are lots of FS mixture controls -- Axis mixture set, Axis mixture1 set,. etc to Axis mixture4 set, plus Mixture set, Mixture1 set through to Mixture4 set. The Axis mixture controls are the very same controls you would assign in FS itself, and the ones you've seen in the Log files you made earlier. All FS controls are listed for you in the "List of FS controls" document installed in your Modules\FSUIPC Documents folder. Regards Pete

You can download any of my programs you like. Most of them are fully freeware in any case. And you do not download any from SimMarket -- they only sell the access keys for user facilities and don't supply any downloads at all for anything of mine. You download main products from http://www.schiratti.com/dowson , and updates and assorted other goodies from the Download Links subforum, in this Forum. Ah, you mean you actually bought a key at SimMarket, not downloaded anything there. So your real post should have been "Purchased wrong product" not "Downloaded ..."? I don't deal with any of the sales side. I only do development and support. I can only suggest you throw yourself on SimMarket's mercy, explain your mistake in a Problem Ticket and hope they will be generous. But I must say they are unlikely to be all that sympathetic. After all the headings on their purchase pages are very very explicit and it does warn you you cannot change or expect refunds ("NO REFUNDS GIVEN!"). The problem is if they do grant your wishes you've effectively also got a free copy of WideFS. Regards Pete

That must be an old version of Actigate. It was a big problem many years ago. I've not heard of any problem like that recently, not till now at least. I don't know how you don't get these access rights. The FSUIPC installer automatically changes the access rights on the Modules folder and all of its contents to full user read/write control. I've never heard of anyone having to mess about like you before. That's weird. It all sounds as if you hadn't really run the Installer. And as I said before you should be registering in the Installer, NOT in FS + FSUIPC Options. That old facility doesn't always work properly in Vista and Win7 and is withdrawn in version 3.99 being released next week. Regards Pete

You can have profiles for whatever selection of differences you wish. They are simply a way of keeping multiple assignments separate for different aircraft. Could be helicopters, jets, turbo, props, gliders, whatever -- whatever needs different assignments or different calibrations, of axes, buttons, or keypresses. Even individual aircraft -- for example Wilco Airbuses need a different way of throttle assignment and calibration to other jets, even other Airbuses. Regards Pete

You are just learning programming? Look at what you have done (I show the relevant lines only): So "heading" is an array of 32 x ints. In other words, 32 x 32bit integers, or 32 x 4 = 128 bytes. The value of "Heading" is the address of this array on the stack. You read the 4 bytes from offset 0580 into the 4 bytes addressed by Heading, so in fact it will go into the first element of that array, i.e. into Heading[0]. But then you print the address of the array, not the contents of its first element! The correct three lines would be: unsigned int Heading; if (!FSUIPC_Read(0x580, 4, &Heading, &dwResult)|| printf("HEADING = %d\n\n",Heading); Since you only need one unsigned int, not 32 of them, you don't need an array. You send FSUIPC_Read the address -- the & preceding the name means "the address of ...". Pete

And did you actually post the entire file? Almost each time you've posted it it seems a little different. The first time had the sections Joynmaes, General, JoystickCalibration, Axes ... and nothing else. The second time the Axes section was completely gone (you deleted it as requested) but there were then Buttons and another JoystickCalibration section specifically for the Cessna 172SP. This last time there were all those plus a sounds section AND the start of an Axes section! It looks like it is being truncated much of the time. Perhaps rather that cut and paste haphazardly, could you plerase ZIP the entire file and email it to me at petedowson@btconnect.com. The problem is, you see, that it really is not possible to match the Logs you are showing me to the INI file you are showing me. . Why don't you say so, then, instead of ignoring suggestions? Here, this is what i suggested, with each action numbered for you: 1. Please just go the the FSUIPC Options 2. Select the Axes tab 3. See what axis arises of its own accord. 4. If none, move each quadrant lever one by one, checking for residual assignments. 5. Press rescan after each. Let me know exactly what you see. Then I said "I think you'd be okay doing correct assignments and calibrations.". I think the best bet for you now is this: 1. Delete the FSUIPC.INI and the PFCHID.INI files. 2. Run FS. 3. Go to FS's own Controls Assignments. If your quadrant axes are recognised there, assign them there. (There's a chance for this because PFC did say they were going to add both routes to their USB sriver). 4. If they are not seen in FS, go to FSUIPC Axes and assign ONE FS control to each lever. Do NOT change anything else. Do NOT set "direct to FSUIPC calibration". 5. Now try them all in FS. Once happy they are working ... 6. ... Go to FSUIPC joystick calibration and calibrate them following the numbered steps in the FSUIPC User Guide. Regards Pete

Sorry, but really none of that is really of any relevance. I don't need and didn't ask for that information. What is "wideclient CFG"? The only configuration file for Wideclient is Wideclient.INI. Sorry, I have no idea what you are talking about there. If you cannot find Wideclient.INI how on Earth are you adding any parameters to it? That's completely irrelevant. None of the files any of my programs use are hidden. Sorry, but you are losing me, going off at a tangent? As I said right at the beginning of this ever-lengthening thread, the problem you really have is simple. The two PCs are not in the same workgroup. Fixing that might be a lot quicker than adding two lines to a file you don't seem to be able to even find. did you ever even check the workgroup names on each PC? If you've no idea how, it is like this: On XP, right click on "My Computer", select Properties, then Computer Name. There you will see your computer name AND your workgroup name. And you can change either using the Change button. On Vista and Win7 you right click "Computer" and select properties, and the details are shown where it says "computer name ...", and you can change them by using the Change Settings button. Regards Pete

I see in the log you are back to having both MIXTURE and MIXTURE1 assigned. I think you are not actually finding the real INI file. Are you running Explore by right-clicking and selecting "Run as administrator"? Are you sure you are actually looking in the real modules folder of the actual FS9 installation you are running? And did you try what I suggested at all, checking and re-establishing proper single assignments and calibrating? The variation causing what you call "spikes" are minor, just 1 point change in that assigned axis. If it were properly under control and a single assignment I think you'll be fine. If you don't actually follow suggestions we won't get anywhere. Pete

If you reinstall Windows it is like going to a new PC, you do need to re-register. You must register via the Installer. Er, how many were there? There's only FSUIPC.DLL. The latest is actually 3.989z, but that will be replaced by 3.99 next week. Recent updates are available in the Download Links subforum. That means FS9 is not properly installed,. There should be an install path in the Registry. But the Installer can fix that for you. It's nothing to do with how you download it. Internet Explorer is the custodian of the trusts on different software publishers. It is only in IE you can find the list of those who are trusted and those not. You must let the Installer complete. That is not a full Install log. I don't know what you are trying to access, but there's no way any text file will give you access denied. i suspect you are trying to access it whilst it is still in the middle of being written. Also, because you installed FS in Program files, which Vista protects against users, you might not see the real Modules folder. Re-run the Installer, let it complete, answering any messages. Then run Windows Explorer by right-clicking it and selecting "Run as administrator". That should enable you to see and access the real Modules folder. FSUIPC will not run if it has a signature error. Either it is corrupted or it is listed an untrusted, or you have a Windows problem, such as missing cryptographic services. Is your vista up to date? Make sure it is at least up to SP2 level. There were problems in the early versions. You'd be best updating to Winnows 7. Try right-clicking on the FSUIPC.DLL and selecting Properties. Look at the Digital Signature. Select it and check details If it is okay, it will say so. Regards Pete

You can't have different axes assigned to the same controls unless the ones out of use are completely quiescent, which means parking them in a dead zone -- one you have to calibrate at either extreme of the throttle movement. Far better to make assignments to specific aircraft, or better, switch to Profiles and make two profiles, one for each way of assigning things. Then calibrate in the profiles too, making each calibration suit the specific control and aircraft type. Regards Pete

The maximum tiller speed is a parameter, defaulting to 60 knots. This isn't a sudden changeover though. At 0 knots it's 100% tiller 0% rudder. At 30 it's 50:50. at 60 and over, or off the ground at any speed, its 100% rudder 0% tiller. Pete

I don't think there's any difference in use or principle between Saitek throttles or any other throttles. What specific Saitek-ness are you concerned about? I think with any Wilco Airbus you have to either assign throttles in FS, or assign in FSUIPC only to the FS controls, not "direct to calibration", because it needs to see the normal FS controls in order to operate its thrust mode selection. If also calibrating in FSUIPC you probably need to select the "NRZ" ("No Reverse Zone" option), and also the "UseAxisControlsForNRZ=Yes" parameter in the appropriate [JoystickCalibration] section. As noted in the History document for FSUIPC, that option was specifically added way back in January 2010 for the Wilco A320. Regards Pete

Ah, you don't use the menus? Obviously I was talking about the Options entry in the same Menu bar in which you find FSUIPC. That's a step forward then. So, what does the Log show? Could you please also post your entire FSUIPC.INI file. I'm almost 100% positive you still have at least one axis assigned. The earlier log you posted showed that the AXIS_MIXTURE1_SET control is only posted to FS after the offset 3BAC changes: 515567 WRITEex 3BAC, 2 bytes: 69 00 515583 *** AXIS: Cntrl= 66422 (0x00010376), Param= -10496 (0xffffd700) AXIS_MIXTURE1_SET .... 515770 WRITEex 3BAC, 2 bytes: 6A 00 515786 *** AXIS: Cntrl= 66422 (0x00010376), Param= -10752 (0xffffd600) AXIS_MIXTURE1_SET Now 3BAC is only linked into any FS control by assignment to joystick 16, axis R. In your originally posted INI you had this assigned as follows: [Axes] 3=16R,256,D,6,13,0,0 = Mixture AND Mixture1 I've checked, and there's really no way any Mixture, Throttle or PropPitch control can arise without an assignment. The only automatic assignments for the HID devices are the ones which don't change from aircraft toaircraft or quadrant to quadrant. The quadrant ones MUST remain assignable because the levers are arranged differently on each. If you cannot find the correct copy of the INI file, please just go the the FSUIPC Options, select the Axes tab, and see why axis arises of its own accord. If none, move each quadrant lever one by one, checking for residual assignments. Press rescan after each. Note that of all of the offsets written for the 6 quadrant levers (3BAC, 3BAE, 3BB0, 3BB4 and 3BBC) only one, 3BAC, seems to have a jitter of its own. It is only varying by 1 point (105-1060 so it wouldn't do any harm provided is was calibrated in FSUIPC and wasn't competing for control of the Mixture with two other inputs, as was the case with your original assignment set. In other words I think you'd be okay going in a doing correct assignments and calibrations. It just concerns me that you still have at least one assignment and don't appear to know about it. Regards Pete

Yes. If both PCs are in the same workgroup you only have one workgroup so broadcasts will work between them. If both PCs are in the same workgroup you shouldn't need to make any changes to any files. The default Wideclient.ini should work. You can do both but it is overkill. Regards Pete

There's no image posted, but I don't understand. We are talking about FS9 aren't we? When I click Options then Controls I get this: Enable joystick Calibrate Joystick ... (grayed out) Assignments ... Sensitivities ... Joystick Forces ... (grayed out) If I click the "Enable joystick" it changes to "Disable joystick" and enables the Calibrate option. Can you use it, then, please? That last log you showed was definitely from 3.98a. You need to actually put the new DLL into the FS Modules folder. If you think you've done that double-check. Maybe you need to run Windows Explorer "as administrator" in order to write to the FS folders -- I see your FS is installed in the default Program Files folders which might be write-protected by Windows. Okay, that's good. Pete

Actually there's one easier way you could try first. I never thought of it before, but with the one rudder pedal input, in FSUIPC's axis assignments, select "Direct to FSUIPC calibration", then assign the axis to both Rudder AND Steering Tiller in the first two assignment dropdowns below. You should then be able to calibrate them separately. FSUIPC will gradually switch between the two calibrations as you accelerate or decelerate, and it might feel rather odd, but it should be gentle enough to cope with. Worth a try, anyway, and really not much different to using two pots on the same physical axis when really you want a separate lever for each. (I use a steering tiller by my left hand in my 737NG cockpit). If you do add a "steering" pot, best make it a more sensitive (i.e. lower impedence? I think) one, or possibly a log-type rather than linear so you can get that fiercer correction with less pressure. You'd need to experiement. Regards Pete

Different axes assigned "Direct to FSUIPC calibration" via FSUIPC's Axis Assignments dialogue. Pete

More important in this case is the Workgroup -- if you make sure all your computers are in the same workgroup you should have no problem in any case. It is the name of your computer, as shown in WindowsExplorer from the other PC, or in the Properties of "My Computer" -- right click on "My Computer", select Properties, then, on WinXP, Computer Name. There you will see your computer name AND your workgroup name. And you can change either using the Change button. On Vista and Win7 you right click "Computer" and select properties, and the details are shown where it says "computer name ...", and you can change them by using the Change Settings button. More or less. You don't need both "ServerName" and "ServerIPAddr". If you give the IPAddr the Name is ignored. I still think your first step should be to try to put both PCs in the same workgroup. Pete