Pete Dowson

Of course. Each parameter is independent of each other. Of course, providing it's the correct port number. How could it be otherwise? Pete

WideServer is built into FSUIPC4, that's why, but it won't work unless you purchase a registration. Why are you worried about it? Pete

Only if you want to change them. The default values will be assumed otherwise. Pete

No. "AI" just means "artificial intelligence", and includes many things in FS. The zapper only operates on traffic, as provided by traffic add-ons and controlled by traffic sliders in FS, not AI sliders. It is known as traffic for all traffic add-ons and to all FS users I know of, except you, evidently! :-) Pete

"Traffic zapper", "Traffic zapall", "Traffic density set", "Traffic density toggle". Pete

Sorry, no. It might be possible for the right click to be trapped and discarded, but wouldn't you need it sometimes? There's really no way I can think of to determine whether the right click, when seen by FS, would result in a context menu or not. Pete

You are missing the "sync pos" facilities -- the button is actually labelled like that. Please refer to the User Guide. There's a whole section on it under the title CALIBRATING MULTIPL THROTTLE, PROP & MIXTURE AXES TO "LINE UP". Pete

Well it occurs in real aircraft too, and pilots seem to cope. This is why the levers aren't tied by bars -- in almost all the cockpit rides I ever had in airliners (a lot before 9/11) it was quite noticeable that the throttles were rarely in a straight line. However, if you can't simply adjust the positions yourself to achieve similar N1% or EGTs (which should be easy enough), you could use the synch pos calibration facilities in FSUIPC. This involves setting a number of points along the axis ranges where the calibrated output should be the same. It doesn't take many for the linear interpolation between each gives you a good match throughout. Not particularly strange. Just as in real aircraft, the hardware concerned is never exactly the same. Pete

Doesn't sound right. Considering you got exactly half the range originally, *2 seems correct. Adding or subtracting something is irrelevant -- that just moves the '0' position. The value uses the complete range of a 16 bit word -- 0 to 65535. Adding or subtracting anything won't change that, you still need the complete range. Overflow off the top makes no difference. I know, 07CC. You told me that already. But how are you writing it? Are you assigning to an FSUIPC "Offset" control, and if so, which one? I'm sure it will be easy to work out what is going on with just a little logging. We need information, not guesswork. Pete

There's no way it can just disappear --and it hasn't been changed ever since first added, But it will not be shown if mouse trapping is not possible. Check your FSUIPC4.LOG file. Is there a message like WARNING: Failed to install Mouse Macro hooks! If so there is something wrong with your FS installation. Masybe you are using the original RTM version of FSX, in which case you don't get Mouse Macro support. You need at least SP1 and ideally SP2 or Acceleration. The other possibility is that your API.DLL is corrupted. Otherwise, if you see no such message, then perhaps you are looking in the wrong place? Tell me more -- the button is labelled "Create Mouse Macro". On the Buttons & Switches tab it is bottom left, on the Key Presses tab it is top right. Note also that the latrest interim update, available in the Download Links subforum, is 4.866. Pete

You have something seriously wrong with your Windows installation, as I can find no way around having that dialogue appearing. It literally is the very next line after the message saying ask the user. I've tried removing all trace of FS9 from the registry, and proven beyond any doubt that it works every time. You could try repairing the registry. If not manually then use one of the free programs designed to do it for you. For instance, go to http://www.tweakfs.c...ools_module.php and download the "FS9 Registry Utility". I just hope that works for you despite the stange Windows problems. If it doesn't you would need to edit the Registry directly. If you told me your actual FS9 install path I could probably make you a "key" file to do that. Regards Pete

That's even stranger, then, because in the Installer the comment "... NOT found! Asking user to find the .EXE instead ..." is immediately followed by a Dialog display with folder/file selection available. It doesn't continue until enter (for "ok") is pressed. I wonder if a keypress was somehow buffered so the dialogue was only momentary? Perhaps you could try again just to be sure? If you purchased the registration recently it will not work with such an old version of 3.70. It is detected as an illegal (pirated) key with the results you experienced. Regards Pete

Actually I am not really in favour of making the "killing" of Lua threads more easily usable than now. I know it is necessary to be able to kill them, usually when developing them so that changes and fixes can be made. But in general it is not good practice -- killing threads forcibly is a brutal process, and whilst I've taken lots of steps in FSUIPC to avoid this causing access violations, memory leaks and dangling handles, it is difficult to actualy guarantee this. The better way it for the Lua plugin to terminate itself when it gets a user signal -- the Lua flags are ideal for this, and can be set, cleared and toggled. You'd only need to do this for those Lua plug-ins you realy want to otherwise 'kill' easily. If you still feel that your idea is better, could you perhaps give examples of what you'd actually be using it for -- i.e. what plugin functions need such handling? Regards Pete

Fixed in 4.866, now available in the Download Links subforum. Not sure how long those controls have been broken -- thanks for reporting the matter! Regards Pete

ALL of the FSUIPC settings are contained in the INI file in the Modules folder. If you copy all of the contents of the folder you have all the settings, including Macro files, Lua plug-ins, documentation, everything. There is absolutely NOTHING to do with FSUIPC outside of that folder and its subfolders! Pete

All switch and button functions can be changed provided your FSUIPC is registered. Please see the section in the PFCHid user guide entitled "Macros: configuring a PFC HID device for FS add-ons". Regards Pete

Not without more information about what is going on, no. Why not try logging offset 07CC and the axis itself so we can see what is coming in and going out. Maybe the Bodnar connection isn't doing what I thought it would be. I also do not know what actual assignment you are making it -- which FSUIPC control are you using? Pete

Thank you. It clearly shows the reason for your preoblem. When you were asked to find the FS9.EXE so that the Installer could locate the correct Modules folder you appear to have given it this path: ... NOT found! Asking user to find the .EXE instead ... User identified path: "C:\Users\A.......\Documents\FSUIPC" This cannot possibly be the location of your FS9 installation! This then resulted in INSTALLATION FOR Unknown: It is "Unknown" because the Installer could not find the FS9 files to identify the version. And since it was not the correct FS9 installation path, there was no existing Modules subfolder, hence this error: Failed to place FSUIPC.DLL into folder as "C:\Users\A.......\Documents\FSUIPC\Modules\FSUIPC.DLL" Error 3 reported ("Impossibile trovare il percorso specificato. ") Please run the Installer again, and this time do as it requests. Note that if you replied "Yes" to the question about correcting the Registry, then the Installer may simply fail again as above, because now the Registry will be pointing to the wrong place. If this happens you will have to edit the registry yourself. This is the first time in the 9 years of the Installer that anyone has actually pointed it to completely the wrong place. Could you explain at all why? I'd be interested to know how you could make such an error. Is it a language problem, perhaps? BTW looking at the log for your very old installation of FSUIPC 3.70, it appears the Key you are using is not valid: FSUIPC Key is provided FSUIPC not user registered Regards Pete

Sorry, but I've never heard of "phoenix". Does it even use FSUIPC? Please always state the version of FSUIPC -- currenty nothing earlier than 4.65 is supported for FSX. FSUIPC makes a log in the Modules folder. If there are any problems they will be logged there. Regards Pete

Er, it won't be 55 mb if you only enabled the items I said -- buttons and Events (not Axis events), and just pressed the buttons which are going wrong, then switching the logging options off again! The logging was only supposed to be used to see what your buttons were doing and showing where the assignments were! Please just paste the contents of INIs and LOGs rather than uploading them. Just at a cursory glance at your INI: It appears that buttons 19 and 21 (mentioned in your message) are not programmed in FSUIPC at all. Only 1, 2,3,4,6, 9, 10,12,13,14,15,16,17,18. I suspect you have buttons also programmed in FS itself hence the multiple assignments I mentioned. Additionally you have button 2 assigned to "elev trim dn", not spoiler arm -- that's button 5. Button 6 appears to be assign to keypress 222 for the iFly -- that's the #~ key. I'm afraid I don't know wehat that does, but it seems unlikely be be 'gear up' as you say. Also, the X52 seems to have been disconnected at the time you got this INI, judging by the 'MISSING JOYSTICK' message. Pete

When it failed to find the path automatically, did you in fact point it to the FS9.EXE as requested? If you did, then FSUIPC should actually be inside the FS9 Modules folder. Did you check? If so, there's an Installation log there. Please show me that. If you didn't do this for some reason, then I think there's something pretty seriously wrong with your FS9 installation. For me to help I need to see that actual Installation Log. If this isn't actually placed in the Modules folder, then, before the installer terminates, you can find a menu item in the log being displayed which allows you to save it. Please do that then paste the contents in a message here. Pete

Not if you aren't using it. You only need files you are using. Pete

Sounds like you either have multiple assignments, maybe in FSUIPC and FS, or your device is playing up and sending spurious button presses. Try using FSUIPC button and event logging to see what is going on. Pete

That is a result of the "InitDelay" option in the INI file to delay SimConnect connection. It was provided to allow possible conflicts with other SimConnect-using addons all trying to do things at the same time. It defaults to 0. From your log it seems the user has set it to 30. Regards Pete

Sorry, I'm confused. Where are you looking for "slew rotate left/right"? For Axis assignments, assigning directly to FSUIPC calibration, the slew axes are: SlewAhead SlewAlt SlewHeading SlewSide No "rotate". You'd use "SlewHeading". If you mean button assignments, then the controls listed are obrained directly from FS itself and include all these, but no "rotate" -- thst would be HEADING MINUS and PLUS.: SLEW_AHEAD_MINUS 65745 SLEW_AHEAD_PLUS 65739 SLEW_ALTIT_DN_FAST 65624 SLEW_ALTIT_DN_SLOW 65623 SLEW_ALTIT_FREEZE 65622 SLEW_ALTIT_MINUS 65626 SLEW_ALTIT_PLUS 65625 SLEW_ALTIT_UP_FAST 65620 SLEW_ALTIT_UP_SLOW 65621 SLEW_BANK_MINUS 65738 SLEW_BANK_PLUS 65740 SLEW_FREEZE 65742 SLEW_HEADING_MINUS 65744 SLEW_HEADING_PLUS 65746 SLEW_LEFT 65741 SLEW_OFF 65730 SLEW_ON 65731 SLEW_PITCH_DN_FAST 65627 SLEW_PITCH_DN_SLOW 65628 SLEW_PITCH_FREEZE 65629 SLEW_PITCH_MINUS 65633 SLEW_PITCH_PLUS 65632 SLEW_PITCH_UP_FAST 65631 SLEW_PITCH_UP_SLOW 65630 SLEW_RESET 65796 SLEW_RIGHT 65743 SLEW_SET 66048 SLEW_TOGGLE 65557 Regards Pete