Pete Dowson

If the ailerons are visually changing by use of your controls then that's all any input can do. It means the value iss being correctly passed to FS. Why the aircraft flight path isn't affected by it is another matter and something I don't understand. Are you sure the A/P is not enabled and keeping the wings level? Or else maybe your aileron trim is completely out of whack? Do you mean "axis ailerons set" or "ailerons set"? If you want to use the normal FSX assignment it should be the former. Why are you assigning in FSUIPC in any case? If you want to use the normal FS controls on the same axes for all aircraft you might as well assign everything in FSX. You can still calibrate in FSUIPC. Aha: You've used the old "Ailerons Set" control on the X axis yet the newer and standard FSX "axis elevator set" control for the Y axis. You should be consistent, and for most FSX aircraft you'd need to use the newer controls, the same ones FSX itself uses: Axis_ailerons_set, etc The others are usually supported still by FS, but not all aircraft will respond to them. Regards Pete

Sorry, but I've no idea what that is. You might be able to do it by "fiddling" the appropriate offsets, writing to them in a Lua plugin called "Initial.lua". You are running PM software too, without FS running? On the same client PC? That gets more complex. You might have to ask the PM support folks whether it can be done. If you don't need the PM software running then you could probably get away with just fiddling the offsets you need, via Lua. Regards Pete

You could try calibrating them properly. Are you using FSUIPC? If so, please look up calibration in the FSUIPC user guide and follow the numbered steps. You cut jet engines by cutting the fuel. Idle has nothing to do with it. You cut the fuel by the Mixture Lean control. All this is surely covered in the FS help? It isn't a function of FSUIPC but of FS itself. Regards Pete

Really? There is something defeating FS's acceleration then, as holding the mouse button down on such a control should cause it to speed up after something near a second. Does it not work okay with default aircraft? If not, I've no answer. If it only happens with specific add-on aircraft it is likely that they are defeating the acceleration by continually sending loads of FS controls, usually which do nothing but repeat settings already made. The "fix control acceleration" option in FSUIPC should help if that's the case -- please look this up in the FSUIPC User Guide for an explanation. It's in the Miscellaneous section (and Options tab). Regards Pete

Yes, of course. When the Installer reaches the stage where it asks you if you want to Register, just press the Cancel button. You only ever need to Re-register if you reinstall Windows, or roll it back to a Restore point before your registration was entered, or move to a different PC, or, in error, delete the KEY file from the FS Modules folder. If you insist on re-entering the details, just get them right. If you enter them incorrectly then of course it won't work any more and you'd need to reenter them correctly. I'm sorry to say this, really, but isn't this just common sense,? There's nothing magic going on here. You have a good registration, you get good results, you have a bad registration, you get bad results. There's only one registration kept, not a whole history of them with FSUIPC choosing from them at random! But as I said there's no need to re-enter anything. Mostly these things are answered in the documentation by the way. Regards Pete

Just download and install the latest. See the Download Links subforum. Regards Pete

Pasting someone else's assignments for things like buttons and macros rarely works, because the joystick and button numbers will not be the same on your PC, and nor will the Macro numbers. For instance, though you say "None of the buttons, switches or knobs do anything", these entries: are dependent on YOUR specific joystick and button numbers, or, in the case of 64, a software driver such as the one for PFC equipment. Best to make your own, correct, assignments, via the FSUIPC options "Buttons and Switches" tab! As for these: et cetera, did you check that the EFIS registered as Joystick 170? And the name of the aircraft "Level D Simulations B767-300ER " -- are you sure there should be a space at the end? FSUIPC normally removes trailing spaces. Best in any case to use the substring facility for aircraft names. er ... FSUIPC 4.5? Phew! That's two years old! Sorry I cannot support such an old version. The OLDEST supported version for FSX is 4.60, which has been available now for many months . Please ALWAYS check you are using a current version before asking for Support. It really isn't possible to deal with old versions. Even 4.60 is pretty old now -- there's a version 4.651 in the Download Links subforum, soon to be released as 4.70 and superseding 4.60. Pete

Sorry, I'm not sure I know what you mean. "aims the FS is running and Battery is on"? What is it that you expect WideFS to do without talking to FS? Do you mean to have a sort of test program for your hardware? How is it connected? Is it a normal joystick type connection with buttons you program in FS, or is it a special device with a serial COM or USB link to the PC? COM and HID devices can be read and written to by Lua plug-ins, and WideClient supports almost all of the same Lua library facilities as FSUIPC. To have WideClient load and run a Lua program before FS is connected it has to be saved in the same folder as WideClient with the name "Initial.Lua". WideClient Lua doesn't support the Joystick buttons testing facilities which are present in the FSUIPC Lua library. This is because those facilities are oriented around the assigned joystick numbers used in FSUIPC, of which WideClient is not aware. So if your hardware is based around a normal joystick connection you'd need to deal with them as for other HID hardware, using the HID comms facilities in the COM library. The same would apply to axes. If your hardware is based on Keyboard encoders, then, again, they are HID devices and can be treated through the HID aspects of the COM library. Regards Pete

Good, but you shouldn't have needed to delete anything. All parts that matter are replaced or updated by the Installer. It simply does not undo any interim update you may have done, such as install the much later 3.989u or 4.651 versions currently available from the Download Links subforum. Regards Pete

Thanks, I've posted my refutation and expect Robert to explain himself in due course. Thank you. [LATER] He's just retracted it, saying it was an error on his part. In fact he uses RC on a Networked PC with IYP too! ;-) None of the programming information is supplied in the normal user pack. There are no offsets mentioned at all, let alone only 3110 and 3114. If you want offset information for programming FSUIPC (and this is effectively what you are doing in Speech Buddy) you need to download the FSUIPC SDK. It contains the complete list of the many thousands of values you can read from, and often write to, FSUIPC offsets. There's the "Programmer's Guide" with details for FS9 and before, and the "FSUIPC4 Offsets Status" document which mostly supersedes it for FSX, ESP and P3D. Good. Regards Pete

Sounds like you either reinstalled or rolled back Windows, or deleted your FSUIPC Key file from the Modules folder. Why did you download it again? Did you lose it? And what exactly do you mean by "the registration doesn't work". At what point when you re-entered your details did it say this? You don't "reinstall the installer", you simply run it. When you run it it checks the version you have, and of course won't overwrite a later one. That would be stupid, don't you think? But it continues, and at the end offers you the opportunity to register. Did you ignore that? Please please PLEASE read the documentation. There's an Installation and Registering guide packed with the Installer! Why do you want to uninstall? If you really want to, just read the section in the User Guide on how to uninstall it -- it is near the beginning, and listed in the contents list as "De-installing". This is what documentation is for, to tell you how to do things, and help. Please do make use of it. If you want to continue using FSUIPC, though, there's no point whatsoever in uninstalling it, is there? That would be stupid, don't you think? Oh dear, better give up smoking! Call the fire brigade right away! Or, if you mean about your registration, sit down, read a little of the supplied documentation, then run the Installer again and re-enter your registration details when the dialogue is offered, at the end. Make sure all three parts are entered exactly correctly, then you'll be okay. Panicing and making assumptions doesn't fix things, it never has. Regards Pete

No, it shouldn't do. It's using the Windows "SetTimer" function, which operates with a millisecond value. However, its granularity might limit it -- for instance, older Windows systems like Win98 did, I think, operate to 55mSecs (about 18 Hz), the "tick" count. But all recent versions do, I'm pretty sure, operate to 1 millisecond. Not that you could use anything so short in a Lua program, as that's being interpreted in any case at a max rate, maybe approaching one line per millisecond. Also, timer callbacks are low priority things. You don't necessarily get control of the processor back until you next regular timeslice (or, these days, I should say "one of the processors, of course). Theoretically 0 should result in an immediate callback -- or at least when you exit the program which sets that, as the interpreter won't re-enter the program till you exit. There's no way to get a frame-synchronised function. In fact, on FSX, I don't think there's a way at all. On FS9 and before I could hook into a chain which was called once per visual frame (there are different concepts of "frame" -- the simulation rate in the Sim engine is usually much faster than the visual frame, i.e. the re-drawing of the screen image). Regards Pete

What's 65586 for? If it's meant to be the FS control, that's "MAGNETO"! Ah, so it DOES send commands via FSUIPC. $3110 is the place where the command NUMBER is sent. Yes, the command NUMBER is 1070. But before writing that you have to send the PARAMETER (your 817's etc) to $3114. So try: FSUIPC_SetInt( $3114, ATCValue ); FSUIPC_SetInt( $3110, 1070 ); As I kept saying, you need not only the COMMAND or CONTROL number, but also the PARAMETER. The Control number (1070 is decimal by the way, not hex like $1070) only tells FSUIPC to send a key press-and-release, but how would it know what keypress without more information? Hence the parameter, which has to be supplied first because the command is excuted on receipt. Really? I've ALWAYS used both IYP and RC on a Client PC, and NEVER on the FS PC! How old is this exchange? IYP most definitely uses the $3110 offset and sends 1070 commands, as I've just described. If that comment is recent (within the last 18 months or so) please give me the reference (link) so I can refute it. Robert, the IYP author, knows full well it can all run on a Client! Pete

Yes, the sync points give it different points to aim at. To transform the curve (which is also only a set of points) to match any randomly chosen sey of sync points would require a level of maths that UI am not really wanting to either delve into nor have FSUIPC spend tits time doing. Linear interpolation is fast and easy. But you can have more than -- up to 63, which is not so far from the true resolution of most joysticks that you cannot make it follow the curve quite closely. The documentation recommends AT LEAST 4 points, not "only 4 points". The documentation also points out that the slope doesn't apply -- the up-to-63 points you define replace that slope, and you can see it by pressing the Slope button. Please do check things like documentation when you have such questions. Things are often answered there. I've tried all sorts of values for the filter, and to make it more effective it needs to sample a lot more values which introduces too much latency, in turn making it difficult to control the aircraft. Kind of like trying to fly with a display frame rate of 2 or 3 fps or so. Maybe there are better formulae around, but I did a lot of research and came up with the only one which was at least reasonably effective without toonoticeable a latency. Good potentiometers are cheap enough, even slide ones. Why not replace the ones in your quadrant? Or at least try to give them a clean with some electrical cleaning spray like Servisol. If find it does the world of good! Regards Pete

The "code" number for the "send key press and release" FSUIPC control is 1070, as listed in the table headed "Additional FS controls added by FSUIPC"£ (in the Advanced User's guide). The parameter to determine the key press is formed (as documented there) by a number 256 x Shift codes + KeyCode. These codes are listed earlier in the same document, in the Button Programming section. For exaple, "ctrl+Shift+1" would be: (2 for control + 1 for Shift) x 256 = 768, plus 49 (for '1' on the main keyboard) = 817. Likewise CS0 = 816, CS2 to CS9 = 818 to 825. Pete

Correct. The flat part of the "S" should be around idle, right? Obviously, then, it couldn't be an "S" for an NRZ option in any case, as the idle point is then at one end. With a reverse zone it's a sort of S curve but with the reverse part kept linear because of its limited and variable range. Sync points are used to match positions on separate Throttles 2, 3 and 4 to whatever you calibrate for throttle 1. So do on throttle 1 whatever you need then use the sync point facilities to make the others match. Regards Pete

The calibration for the separate throttles only affects forward thrust (0 to 16k OUT values), not the reverse, which is therefore left linear. This is because the actual useful reverse zone varies from aircraft to aircraft (eg -4096 to 0). The graphic for the slope merely reflects this, and it isn't regenerated just because you adopt the NRZ (No Reverse Zone) option -- all that does is spread your -16k - +16k over the 0 to 16k area, following the selected upper part of the slope. Regards Pete

The log shows everything is fine, so it isn't anything wrong with your registration for sure. Have you actually USED FSUIPC for anything, made assignments, calibrations, etc? If so, maybe you made a mess? Try deleting the FSUIPC.INI file from the FS Modules folder before running FS, so it will start again with default settings. That effectively makes it run exactly the same as if it wasn't registered. Verify things work okay, and only THEN start using the FSUIPC facilities you've paid for. If that doesn't help then it's something to do with the Aircraft and you need Wilco support. Check the date the System -- i.e. the PC you are using -- is set to. Actually it is okay (the log shows "System time = 09/01/2011 ...". If it was earlier than your purchase then it would make the registration look invalid. Regards Pete

Sorry, I still don't know how you are sending these keypresses. I take it then that you cannot actually send numerical FS controls as you seemed to say right at the beginning? If it is SpeechBuddy generating the keystrokes and not FSUIPC (via the use of the controls I keep referring you to), then it will be because RC doesn't see keystrokes on the Client. They have to go to FS so that FSUIPC can detect them on RC's behalf. I assume that SpeechBuddy sends FS controls to FS via WideFS and FSUIPC, but it cannot send keystrokes that way unless it is encoding them in the added FSUIPC control for this purpose. Pete

FSUIPC3 works on FS98, CFS1, FS2000, CFS2, FS2002 and FS2004. However, I can't support anything earlier than FS2004 simply because I no longer have the earlier ones. There will be many added facilities which don't work before FS2004 but all the old basics should be fine. BTW why on Earth are you marrying a state-of-the-art PC with such outdated FS software? Pete

I've no idea how to help at all since I don't know SpeechBuddy and I don't know what you are doing. Earlier on you seemed to imply it could send numerical FS controls with parameters. If so it should be able to send the added FS controls. That should be all you need. Pete

I don't really want to SEE anything. I suggested that since you evidently have a corrupted DLL.XML file (presumably corrupted by that aircraft install you did) that you tried either renaming it, then running the FSUIPC 4.638 installer, to see if that solved the FSUIPC problem, or simply deleting it and re-installing in any case. The only possibly reason for me to SEE it is if you want me to fix it for you instead. You showed me one many messages back but that was evidently the wrong one as it didn't try to load any of the other things you said didn't work, and was a perfectly good file in any case. Please go back over the whole of this thread and review what's been going on here. We've simply gone round in circales with you apparently getting more and more confused all of the time. I can understand none of this is easy, but you persist is either misreading things or simply not reading them. I'm not sure which. Have a good holiday, and please review the whole sequence above when you come back and try not wasting so much time for us both. Okay? Regards Pete

Please show me the FSUIPC.LOG file which you can find in the FS Modules folder. You can cut and paste it here. Be sure to close FS first. Have you checked your system date? Regards Pete

Is this FSX or FS9 or some other simulator? What version number of FSUIPC? You always need to provide some information. There's no "full" version of FSUIPC. There's only TWO main current versions of FSUIPC -- 3.98 for FS9 and before and 4.60 for FSX and later. There are later interim releases of both in the Download Links subforum. But there's never been a "full" and "reduced" version difference. If you mean that things stopped working correctly when you Registered FSUIPC then it will be only one of three things: 1) your system date is wrong, preceding the purchase date of your registration, or 2) the version of FSUIPC is way out of date, or 3) your registration key is a forgery. Pete

On that note you might want to try FSUIPC version 4.649, just this evening posted in the Download Links subforum. It handles Radar Contact's weather requests more efficiently when running ASE in DWC mode. At least it looks better here. Regards Pete