Pete Dowson

First of all, please ALWAYS state the version number of your FSUIPC. And if it isn't 3.98a or later, please update first and try again. It might be worth your while actually updating to 3.989z (from the Download Links subforum here), in case the issue you have is a known one which is already fixed. After that, I expect Tim will be able to help you, but he may ask you for more information, such a logging form FSUIPC. Because FSUIPC offers ways for application programs like Plan-G to do all sorts of things inside FS it is possible for them to cause a crash too. Tim will be more knowledgeable about what Plan-G is doing. I'm sure he will contact me if he needs help with the FSUIPC side of it. Regards Pete

So it now says "enable joystick"? If it says "disable joystick" it is enabled. The label states the action which occurs when you click it. Well I certainly cannot get anything sent to FS from any axis whatsoever with no assignments anywhere. I don't understand what is going on with your system. I will have to wait till you test with the same version of FSUIPC as me. Incidentally, why did you post a tidy section from your FS9.CFG file, showing keypress assignments? The only parts of relevance would be the "joysticks=" line and the actual Joystick device sections, if any. Pete

Yes. So? I naturally assumed that the inquirer was wanting a different calibration for operating the nose wheel -- i.e. steering on the ground -- to that used for rudder operation at higher speeds. If both rudder and tiller are assigned in FSUIPC "direct to calibration" then FSUIPC gradually switches control from the tiller input to the rudder input as speed increases between 0 and 60 knots (defalut setting), and vice versa on slowing down after landing. Pete

You have Windows set to hide known file types from you. The filetype "INI" is short for "INITIALISATION SETTINGS", which is another term for configuration settings, so Windows reference to 'cfg settings' should certainly suggest such! That IS the "wideclient.ini" file! Please tell me, how did you manage, as you confirmed, to add those parameter lines as instructed to a file you couldn't find? Something isn't making any sense here! If you want to see filenames correctly, and I recommend you do, please open the Folder Options in Windows Explorer and uncheck the option to hide known filetypes from you. Pete

Okay. The log shows FS seeing MIXTURE1 controls even with no FSUIPC assignments, so it simply MUST be that you have not disabled joysticks in FS. You could prove that to yourself by simply removing FSUIPC.DLL temporarily from the FS Modules folder before running FS. Maybe you thought you had disabled FS joysticks but have since reconnected a joystick device which will probably make FS re-enable them. It is a bit quirky like that. Please check in the Options-Controls menu that the first option listed there is "Enable joystick", not "Disable joystick". If it says "Disable" then the inputs direct to FS are enabled. (Of course, if you prefer, you can actually use FS's assignment facilities for those PFC axes which it does see. You can still calibrate in FSUIPC, just don't assign things in both places). Note that there is no sign of anything else untoward in that log, only the occasional appearance of the AXIS_MIXTURE1.SET control detected and logged by FSUIPC. If you are not sure what you've done in FS, I can look at your FS9.CFG file if you wish. Finally, it might be worth updating your FSUIPC to the very latest, 3.989z, available in the Download Links subforum, because then you are on the same version as I when comparing resluts. Verion 3.99 is due for release within a couple of weeks -- 3.98a is now a year old. Regards Pete

The client PC is not receiving broadcasts from the Server, so it cannot identify that Server. This almost always means that your two PCs are in different workgroups. If you've never changed the workgroup names it is important to note that Vista and Win7 use a different default workgroup name to XP. Please check the Installation section of the WideFS User Guide, and in particular the part headed: Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! Pete

Sorry, no idea. It's a question for Eaglesoft support I think. The reverser facilitiy in FSUIPC merely makes use of the fact that the older throttle axis controls (called "THROTTLEn_SET" instead of "AXIS_THROTTLEn_SET") operate with negative values giving reverse thrust with idle at 0 and full forward thrust at +16383. The throttle axis controls normally assigned in FS, the "AXIS_THROTTLEn_SET" controls, provide only forward thrust, -163984 being idle and +16383 being full. It sounds like the Eaglesoft aircraft is not programmed to provide reverse thrust by axis, only by use of the "Throttle Decr" command (F2 key with a default assignment in FS). But this is something to check with Eaglesoft. Regards Pete

You posted exactly the same question in the same thread twice. Why? Please don't. It only makes extra work to no avail. If there is no WideClient.INI file in the folder on the Client PC where you placed WideClient.EXE, then 1. You could never have run WideClient, because it always makes an INI file as well as a LOG file. AND 2. You could not possibly have added the two parameters as instructed to the file because it doesn't exist! So why say you did? Now this really seems very unlikely because you actually showed me a Log from WideClient -- the INI file would be right next to it, in the same folder. So, all I can think is that you are not looking in the right place. Maybe you've forgotten where you put wideClient? If so, check the properties of the short-cut I assume you are using to start it. I can see this is going to take a long time. It's getting late here now so it'll be sometime tomorrow now .... Pete

You replace the # with your __int64 value. And use floating point, because obviously 90/(10001750*65536*65536) will be a lot less than 1 and not expressable as an integer. To make the compiler use floating point simply use numbers in floating point format, like 90.0 , 65536.0 etc. And the variable receiving the result should be floating point ("double") too unless you only want the number of degrees and no fractions. Pete

1. The INI file is not a LOG file, it is the option settings. I don't need to see those again. 2. Sorry, but there's no point logging when there's no problem! I wanted to see the log with no assignments in FSUIPC and with joysticks disabled in FS. Because I cannot understand how any changes arise for anything not assigned. Please show a log WITH the problems. I think you'd better also enable IPC write logging as well as Event and Axis logging in FSUIPC Logging. That will show everything going into FS through FSUIPC and well as anything getting into FS by axis controls from wherever. Pete

Oh dear. As you can see (did you look at all?) it is still doing the same thing. Seems you didn't actually edit the WideClient INI file as instructed! Please go back and check it. If you really think you've edited it correctly, please show me that file so i can see. BTW did you not bother to see if you could put both your PCs in the same workgroup, so you wouldn't need to edit any file in the first place? Pete

Well the mixture and prop pitch control changes must be coming from somewhere else then. They are not assigned in FSUIPC and no joysticks are enabled in FS, so some other add-on may be responsible. Do you get the same without the Cirrus (or other joysticks) physically connected? I think you need to be reasonably sure it's to do with the PFC equipment before expecting them to be able to help. Have you re-enabled the event and axis logging in FSUIPC and checked the log? In the previous log you posted there were no signs at all of any spurious entries that I noticed. The only odds things were the two different MIXTURE axis controls conflicting -- and those were most certainly shown to be assigned in your [Axes] section of the FSUIPC.INI file. Regards Pete

Please show me the WideClient log file. It will no longer be waiting for a Broadcast from the Server, so there will be another reason your Server is not seen. Possibly a firewall? Pete

Sounds like you've got some pretty old stuff there. The current and correct user guide is actually supplied inside the very same Zip file as the versions of WideFS you are using, so how could you have got some really old ones mixed up? It tells you what parameters to add to the INI file in Wideclient if you need to tell it to link to the Server explicitly. Please tell me what there is to not understand. I really wouldn't know any way to desdcribe it clearer, that's why it is written there. Please explain, then, what it is you do not understand. The instructions are there in black and white (below the red bit). Look, here is the EXACT information extracted from that section: I cannot actually edit your INI file, you need to do that! If you don't know the name of your Server PC you can see it in the Server log you posted: How much more explicit can it be? And how is it you never saw any such suggestions in all the other threads you said you viewed? :-( Pete

Did you try disabling joysticks in FS first? Pete

Only the banner asking you to read what follows is in red. it is so highlighted so you cannot miss it! So how on Earth do you manage to do just that? The document is obscurely named, perhaps, "WideFS User Guide"? The part so headed is in a section called "configuring your network" which is part of the Installation section, and occurs on the 4th page. How could it be in such an appropriately named place in an appropriately named document and still have escaped your attention so completely? :-( Pete

I thought you said you'd checked other threads? This is the most common symptom, often mentioned and resolved, where the Server is sending broadcasts which the client never sees. It is because the server and client PCs are in different workgroups. This has occurred innumerable times since Microsoft released Vista and Win 7, because those two systems set a different Workgroup name to WinXP. Did you think to check the supplied documentation? Please read the part where there's a RED notice asking you to at least read some of it. It isn't very far down, in the User guide. It tells you how you can override the automatic connection, if you don't want to name your workgroups the same. Pete

How are you identifying those if nothing is assigned? I am not really following you. Where are you looking? No, I have got the same console here working fine. With no assignments in FSUIPC nothing happens from the quadrant. I'm suspecting that the firmware level in your Cirrus is different to mine, and that they (PFC) have found a way to add the quadrant axes to the normal joystick axes which are assignable in FS itself. There's really no other way you can get any conflicts with no FSUIPC assignments to those axes. Please try disabling the joysticks completely in FS -- I think it's a simple menu option. Yes, no assignments. You are coming to a point where I think you have to go back to PFC for explanations. Regards Pete

You posted into the FAQ subforum, which is the permanent repository for ANSWERS to Frequently Asked Questions. It is NOT the Support forum, so I moved your question here. Please use the Support Forum in future. There's no way I can help with no information. When reading all those other threads didn't you notice that things like version numbers and Logs are needed? Please always state the version numbers of the FSUIPC, WideServer and WideClient you are using. Close FS and WideClient down. Then find the log files: FSUIPC.LOG and WideServer.Log in the FS9 modules folder, and WideClient.log in the same folder as your Wideclient.exe on the client PC. Paste them into a message in this thread. Internet connection is irrelevant. Regards Pete

Nothing to do with the INI file. But if merely registering FSUIPC makes things stop working there are only three possible reasons: 1. The key was purchased in 2010 or 2011 and you are using an old version of FSUIPC. You must use version 3.98 or later for FS2004, or 4.60 or later for FSX. OR 2. The PC's system date is incorrect and is set to some date before your purchase date of the FSUIPC key. OR 3. The key you are using is an illegally pirated one which should certainly not be used. In this case I'd like to know where you got it, please. Regards Pete

Yes, and these are the Quadrant assignments: [Axes] 3=16R,256,D,6,13,0,0 = Mixture AND Mixture1 4=16U,256,D,5,17,0,0 = Prop Pitch AND Prop Pitch1 5=16V,256,D,4,9,0,0 = Throttle AND Throttle 1 6=17Y,256,D,14,0,0,0 = Mixture 2 7=17Z,256,D,4,0,0,0 = Throttle AGAIN 8=17R,256,D,10,0,0,0 = Throttle2 9=17U,1,D,6,0,0,0 = Mixture AGAIN, and with a "hair trigger" (even a single unit change on the input from this axis will change FS). So, for some reason (care to explain?) you have assigned TWO separate axes to TWO different mixture controls, where the Generic "Mixture" will control both Mixture 1 and 2. And you've also done the same with the Throttle! So there are triple assignment each to both Mixture and Throttle, and also a double assignment to Prop Pitch. Why, oh why? I'm surprised you've not got a lot more problems that the one you state! What will be happening is that the axis you aren't using is interfering with the one you are! The likely reason it is only affecting the Mixture is that you've told FSUIPC to handle any change, even the smallest possible, from that "hair trigger" axis -- I expect changing flaps is causing a minor jitter on that axis. The number '1' there is from the Delta value in the FSUIPC axis assignments tab. You shouldn't need to change that from its default. Since I don't know which ones you want and which you don't, I suggest you delete that entire [Axes] section in the INI file, and start again. Only assign ONE axis to ONE control at a time! Also it appears that you've not actually calibrated any of the ones you have assigned. Regards Pete

The problem I see is that you appear to have two different controls assigned to your Mixture lever: 54195 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -10496 (0xffffd700) AXIS_MIXTURE_SET 54195 *** AXIS: Cntrl= 66422 (0x00010376), Param= -10496 (0xffffd700) AXIS_MIXTURE1_SET The quadrant axes are assigned in FSUIPC. You need to check that and correct it. Generally you should only assign each lever to one control. Certainly you can assign one Mixture lever to all of Mixtures 1-4, if you want, but that's really what the generic "AXIS_MIXTURE_SET" does. You never want both the generic and the specific controls assigned at the same time. If you think you've done it correctly please show me your FSUIPC.INI file and I'll check that. This is probably the sole cause of your mysterious 17%. The glitch appears to occur because the "MIXTURE1" control operates infrequently, for some reason I don't fathom, and seems to 'stick' at your 17% point like this: 58672 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16383 (0x00003fff) AXIS_MIXTURE_SET 60107 *** AXIS: Cntrl= 66422 (0x00010376), Param= -10496 (0xffffd700) AXIS_MIXTURE1_SET I can't see any interaction between flaps and mixture. I think that may simply be occurring because the internal scanning rereads the levers when something else changes. I may be wrong there but in order to delve any deeper I'd need to add more code to get more logging information. So: 1. Please show me your FSUIPC.INI file 2. Please update your PFCHID.DLL to the version 1.21 I posted in the Download Links subforum recently. Then at least i know we are looking at the same program! ;-) Incidentally, you would be better off assigning "direct to FSUIPC calibration" in FSUIPC. The FS controls you are using are less efficient and probably more prone to interference from other things in FS. Regards Pete

Ah, I have one of those consoles. I think that, at least with the firmware I have in the device, the 6 quadrant axes are assignable in FSUIPC, so calibratable there, but the main flight controls aren't normal joystick axes and are calibrated by PFC software (or automatically by the firmware, maybe), and my PFCHID driver reads the calibration values from the firmware, does the calibration, and sends the results direct to FS. How strange. First thing to do would be to get some logging. In the PFCHID.INI enable LogDecode and LogIPCWrites. Load up FS and in FSUIPC's logging page enable Event and Axis logging (two checkmarks).Don't run FS too long, only operate mixture and flaps and stop as soon as you can repro the problem. Note down what you did at each stage. Then paste the logs (they'll be in the FS Modules folder) in a message here (or at least the latter part, where the error happened) so I can see what might be going on. Note that I just recently posted an update to PFCHID.DLL -- see the Download Links subforum. It fixes a few things, mostly to do with macro overrides to the switches and knobs. Odd that I wrote the PFCHID driver two years ago and have had no feedback or questions on it at all until this week, and then I get two, one after the other! It would be worth your while installing the later driver (1.21). Regards Pete

Sounds like normal prop wash effect -- this increases with prop RPM. When I was flying in a real Cessna 152 i was surprised how much rudder you need and not just for countering wind effects. The prop effectively creates a crosswind pressure on the tailfin because of its rotation. You can reduce these effects (propwash and torque) quite substantially in the FS aircraft realism settings. For light GA aircraft like the Cessna I found the centre values best for more of those settings. FSUIPC supplies a separate assignment and calibration option for a steering tiller axis. You'd need a separate axis for the tiller. maybe a separate lever on your quadrant? The only alternative is to use the "slopes" facility in FSUIPC to flatter the response near centre, to give your rudder control nice gentle effects in the normal flying range but with really effective angles when pressed firmly. But this is really what you say you are needing to do in any case. Regards Pete

Why "somehow"? The Installer automatically puts it into the Modules folder. there is no way to get hold of 4.60 except by running the Installer, and that puts it into the Modules folder along with other stuff including full documentation in a sub-folder. Sorry, I've no idea what any of that means! :-( What does "didn't go well" mean? That your unzip operation failed? And how is there "no change" in the second case which you said was "successful". How can "successful" not be a change from "didn't go well"? If 4.669 was never installed how did you remove it? Why start over with 4.5 which is way out of date and unsupportable? Why did you post further logs? I summarised where you are at in my last message. There's nothing else I can glean from any of this -- we've simply proven that SP2 SimConnect is installed okay and works okay. If you want more diagnosis, you could uninstall SP2 (or Acceleration if that's what you installed), then rerun the 4.60 installer and see if its log says SP1 SimConnect is okay. If not then FSUIPC 4.60 won't work, but 4.669 probably will because it links to Simconnect differently. Really, you need to resort to support for the products concerned. They should be able to tell you which version of SimConnect they depend upon. If it isn't SP2 you probably have your answer -- a SimConnect corruption and a probably Windows re-install. Pete