Pete Dowson

Sounds like jitter. Are the changes up and down, or all it one direction til they get to an extreme and stop? Jitter (up and down jumpiness) is caused by bad power supply, humidity, heat, worn components or, just possibly, a faulty USB connection. For the latter try another, a USB socket on the PC not on a hub. If using a hub, use a powered one. Hmmm. I don't know of any "FSUIPC problem" which would by itself have caused input figures to change on their own. Hmmm. Good luck. If they were okay then suddenly went "weird" it does sound like something failed though, doesn't it? Regards Pete

I'm sure the answer is in several threads here already. You must assign either in FS or in FSUIPC4 to the Axis throttle controls, then if you want to calibrate in FSUIPC set the NRZ option (no reverse zone) and the UseAxisControlsForNRZ=Yes parameter in the relevant [JoystickCalibration] section of FSUIPC4.INI. This is explained in the Advanced User's guide -- just search on "Wilco". Pete

Evidently not.! "readlast" and the Hid facilities were all added this year, since April 2011. From this: I see you are using the current main release. As you will see from the interim update notes in Download Links subforum we are now up to version 4.734 with lots of new facilities, all listed there. There are also updated Lua documents in one of the threads there. Regards Pete

Esound? Sorry, that's not been supported for many many years. I'd no idea it was even possible to use it with FS9. There are good sound playing facilities now provided in the FSUIPC Lua plug-in facilities. All of the Lua library functions are fully supported and work well. Regards Pete

Tim has found and fixed the problem internally. i will be building a revised FSUIPC4 with Installer for v1.2 and will release it soon. i'd like really to wait until LH release the patch including this fix, but that might be a while. Not sure. I don't want a big support load telling folks why P3D crashes on exit with FSUIPC installed. Regards Pete

I can't do that. It wouldn't find FSX or ESP either then, as it is just one piece of code using tabulated names. I need more information then so I can fix it. It certainly doesn't crash here on a system from which I removed P3D a while ago. There's no reason I can see in the code that it will crash there. Without more information I cannot fix it, so please provide more -- specifically the Log or the partial log so far. Correct, but I can fix the problem if I can identify it, and I cannot without more information. Pete

Sorry, I have no idea what F/A-18E Superbug (which I assume is ann FSX add-on aircraft?) does or wants with FSUIPC4, and you provide no information whatsoever about what you've done with FSUIPC4 after downloading it -- where from, which version, what did you do with it? Is it needed by this 2Superbug", and if so, is FSUIPC4 installed correctly? Check the documentation and look at the menu entry. There will also be an install log and hopefully a run-time log in the Modules folder. I didn't know Amazon made FS add-ons, but if they are not the makers you need to go to the maker's support forum, wherever that it. (BTW I can't see how anything to do with errors in Microsoft Word relate to any of my software!) Regards Pete

Without sight of the actual Lua program you are using I haven't any way to comment meaningfully I'm afraid, except to point out that this is an obvious error which you need to correct: Whatever 'readlast' is it isn't defined as a field to whatever precedes it. Check your line 34. Pete

Sounds like it needs calibrating and it's buttons assigning. Such things aren't automatic. What disk? If you are loading other software you need their support. You shouldn't need anything loading. Pete

What exact "latest" version? 3.99, or 3.998d, or something in between? Re-assigned from what sort of assignment, and how assigned in FSUIPC? Sorry, I don't see anything there relating to anything here? If you've actually assigned things in FSUIPC those assignments will be in a section called [Axes], or [Axes... with aircraft or profile names if specific. Pete

All forms of the Run ... command in WideClient also have Close ... equivalents. Regards Pete

That's nothing to do with FSUIPC. You have something else wrong. Even a registered install of FSUIPC doesn't touch any controls unless you configure it to. Regards Pete

That's correct with an unregistered installation. FSUIPC will be acting in its prime role as an interface for applications. If you want to access the User Facilities you have to pay for a registration key, then re-run the Installer and enter the details. Please do refer to the Installing and Registering guide accompanying the installer in the ZIP, and the user documentation installed for you in the Modules \ FSUIPC Documents folder. Regards Pete

Jopysticks aren't made for one program only. they have a general interface supported by many programs. Why does it "seem not", and why won't they work in FSX? That makes no sense. But you can't change OS from winXP to WinXP, you just said you already used XP for FS9. FSX won't work in anything before XP in any case. Pete

I don't know. I have a version which installs okay and works okay whilst P3D is running, but appears to cause P3D to hang/crash on termination. I'm in discussion with LH about this, and I'm unwilling to make a release until it's resolved, really. Trouble is they've got a lot else on. Pete

I'm not talking about axis assignment, only calibration. But if the OUT values shown in the assignment don't match the IN values in calibration, you have something odd going on, because the result of assignment is what you are calibrating. Sorry, I don't understand. Are you really saying that pressing the brake gives no changing values at all, only one fixed at 0? If you don't get a range of values your pedals are broken, defunct. And if the OUT value there changes much from the IN value, then you either have "RAW" set (don't), or you've set a large Delta value. The default Delta is 256 which means FSUIPC ignores changes smaller than 256. The OUT value may then differ from the IN value by up to 256, but it will often be the same. Yes, if the axis values are always 0 you couldn't possibly use them let alone calibrate them. i think you are reading something very wrongly indeed. In any case nothing of what I've been asking you was in any way related to what's on the assignments tab. I have only been trying to extract from you 4 simple values sen on the Calibrations tab -- the range of IN values for each pedal, and the MIN and MAX values you've personally set by pressing the relevant SET buttons -- not the default values which might still be there if you've not calibrated. All this is on the calibrations tab. But I'm giving up asking you now. I think you seem to be happy with what you've got even if I don't understand what you've done through lack of information. Good flying! Regards Pete

And that is the range you get on the axes? Really? They are well nigh perfect then, as most don't give such exact perfect values! In any case, you'd still do better to do what the calibration steps (in the User Guide) advise, and to set the minimum a little higher (i.e. with some pressure on the pedals), to stop accidentally pressing brakes when using rudder normally, and also to prevent brakes coming on should you ever get any little jitter in your currently perfect pedals. Jitter is caused by wear, dirt, humidity, temperature, and power fluctuations, so can affect anyone. Also it is generally wise to set the maximum a little less than the true maximum input so that you can always be sure of getting to the max when you need it. All this would be accomplished by following the numbered steps to calibrating correctly in the FSUIPC User Guide. Regards Pete

Windows ME? Good grief. I very much doubt in 3.99 has much chance of working on such an antique operating system, and most certainly WideFS will not. I'm afraid I just cannot support anything earlier than Windows XP these days. Sorry for the bad news. I've not heard of anyone using such an old Windows version for many years. I'm surprised FS9 works with ME! After all FS9 came out in late 2003, almost three years after Windows XP. BTW Windows ME was a mistake, a really bad version. I skipped that -- Windows 98 was far better, but both were demolished by XP in 2001. And that is now over ten years ago! Regards Pete

What program are you using to set the weather? FSUIPC doesn't actually provide any "weather setting" facilities, only facilities for other programs to set weather. And what is this "little window"? I've no idea what that is. Does it say anything? Are you sure it isn't from wehatever weather program you are using? Please also always mention which FS you are using, and also the actual version number of FSUIPC. On the same PC, yes. FS will see them, and you can use FSUIPC to assign if you wish. Please see the thread near here entitled "2 saitek Yokes" where I've answered a similar question. Regards Pete

FSX will be able to assign and use both, but it reacts to the any changes from either. Provided there are no changed inputs from the one not in use, you won't have a problem, but unfortunately many joysticks do have occasional "jitter" which would interfere with the one in use. You can get around that in FSX by increasing the "null zone", but since you have a registered FSUIPC there is a better alternative. Assign both yoke's aileron and elevator axes in FSUIPC, selecting "direct to FSUIPC calibration", then calibrate in FSUIPC. When you do this FSUIPC will arbitrate between the two otherwise conflicting inputs, giving precedence to the one with the greatest deflection from centre. Regards Pete

Registrations for both FSUIPC and WideFS are done in the FSUIPC Installer, not in FS. Just as described in the Installation guide you got within the FSUIPC ZIP file. Just run the FSUIPC Installer and enter the registration details when the opportunity is presented. Pete

Ah, sorry then, I don't know. But i think there's a program which you can run which saves and restores assorted windows positions. Ask over in the general FSX Forum. I use a hardware cockpit, no FS gauges, so only the scenery from FSX on a projection. I've never really messed with undocked gauges and windows. Pete

Is it an undocked FS window? Can't you just do it and save the Flight? It should come back next time to the same position? Pete

There's only one FSUIPC for FSX, FSUIPC4, the current version of which is 4.70 (updated to 4.734 in the Download Links subforum). How come your joysticks don't work in FSX? As long as Windows recognises them, so will FSX. FSUIPC is not a joystick driver. If FSX doesn't see them, neither will FSUIPC4. I have an old Saitek wireless gamepad (a P3000), and that is seen the same way in both FS9 and FSX. It doesn't need any special drivers either. The Saitek rumble pad looks very similar (but of course it has force feedback as well), and Microsoft sites seem to say it doesn't need any special drivers. Pete

Yes. There seems to be something wrong with your Registration: If you remove the FSUIPC.KEY file from the Modules folder your applications will probably work fine. The bad registration is messing up the interface. Check the key in the Key file. If it looks okay, Zip the KEY file and send it to me at petedowson@btconnect.com and I'll check it for you. Pete