Pete Dowson

I think you mean 4.86.. And I don't have a "site", so I assume you mean Mr. Schiratti's page. I'm not sure how this is related to your thread title of multiple controls, but: If the axis is jittering then you most likely have a bad controller, or a poor power supply, or dirt in the controller itslef. The values shown on the Axis assignments tab, coming from your axis, are the ones FSUIPC gets from Windows, via the direct input system. Fluttering or jittering there is not easily correctable by software. If the jitters are minor then you might get away by simply increasing the "Delta" value, so FSUIPC ignores small changes -- but this reduces the axis resolution, so be careful. There's also a "filter" option in calibration, but this does have a damping/delaying effect and is only advisable as a last resort, and certainly not for stunt aircraft or fighters which need quick response from controls.

Luck with the processor I guess. Mine is not quite as up to date as yours. H100 cooler, but Asus Maximus Extreme P67. Maybe it's the Z77 chipset. Ah well. I doubt I'd really notice the difference between 4.8 and 5.0 -- it was just a magic number I originally targetted. ;-) Pete

Get this and let me know, please, before I release it. FSUIPC4869.zip ... BTW, how did you get your i7 stable at 5GHz? I'm running at 4.8GHz. It will go to 4.9 but is a little unstable then. I guess i need better tweaking somewhere. It was a specially selected processor, higher price. Pete

I wouldn't have thought so, but I'll release an updated FSUIPC4 which is more accurate with Sleeps with larger values. Give me a few minutes ... ... BTW, how did you get your i7 stable at 5GHz? I'm running at 4.8GHz. It will go to 4.9 but is a little unstable then. I guess i need better tweaking somewhere. It was a specially selected processor, higher price. Pete

They simply call the Windows "sleep()" function, but they do it in a loop with "sleep(9)" interspersed with checks on whether the user (or FSUIPC through an aircraft change) has tried to 'kill' it. Each Sleep(9) is deducted from the total needed by 10, allowing 1 millisecond for process/thread switching and abort testing. This works very well for shorter intervals and on less capable PCs with a lot going on, but on a powerful system with less going in it may induce as much as the 10% difference you've noticed. This might be much more likely on an FS9 installation which loads the PC so much less than FSX. Do you need great accuracy? I could probably implement an accurate one based on the microsecond timer instead, but for 99.9% of uses this is over the top, and would certainly result in a minimum delay of more than the current code allows. I won't be changing FSUIPC3 for such a requirement, but FSUIPC4 and WideClient are still open to small changes when needed. Just give me a good reason, please. Note that even with a more accurate system, other factors could still contrive to make the interval longer than requested. Regards Pete

FSUIPC4 is the 'new' version for FSX, ESP and P3D. FSUIPC3 is for FS9 and before. FSUIPC4 will not install into FS9 or before. When you install it there will be full documentation installed in the FSUIPC Documents subfolder. They tell you all. If you want to read some first, check the "Download Links" Subforum here where you can download documentation on its own. Pete

GPSout is no different in operation on any Windows version. It is a very simply module, just sending out data on whatever port you specify. You need to double check that COM3 is correct. GPSout is not an FSX module. GPSout is built into FSUIPC4 for FSX. And the Modules folder is created when you install FSUIPC. Regards Pete

Have you tried using FSUIPC's logging to check what is going on? Monitor offset 66E5 as type S16. You could also set Axis event logging on, and, before loading FS set this in the [General] section of the INI: Debug=Please This allows you to set numberical options in the "Extras" edit box in the Logging tab. Set 9 there and it will log the incoming axis value too. What exact FSUIPC control are you using? Maybe you could show me the [Axes] section from the INI? I don't know SIOC. Apart from using the Monitor log to check it on the FS PC you can use FSInterrogate (from the SDK) to check it on the client. Is it possibly that SIOC doesn't like WORD (2-byte) values on an odd byte boundary? Pete

Only the Modules folder. All of the FSUIPC related files are kept there, nowhere else. And he must have accessed his INI file to set the delay value as it isn't defaulted. And he seems to have supplied you the LOG file, which is next to the DLL and the INI file. Maybe he's got Windows hiding program filetypes -- the FSUIPC user guide warns of this -- in which case it's type would simply be "configuration settings" or similar. Pete

If you've moved its connection then it would appear with a different joystick number. If the old joystick assignments are still there, then, yes, that could interfere, depending on what drivers are also left in Windows. Just check the settings in the [Axes] sections of the FSUIPC INI file. Also the [JoyNames] section which lists all the devices FSUIPC knows about. If you want to start again completely, just delete the INI file before loading FS. FSUIPC will make a new one with no assignments. If it is only the axes you are worried about, just delete the [Axes] sections. Pete

If FSUIPC is not registered, then it does nothing at all unless asked to by another application. Maybe Captan Sim uses something in FSUIPC -- you'd need to ask their support. BTW versions older than 4.86 are not supported, so tell your friend to update, please. There's no reason to stay out of date, registered or not. Pete

Yes, of course. You must either do without a firewall, or allow FS and Wideclient through it. Sorry, I've never used a firewall on my 10 PC network. I think the one implemented in my Router is sufficient. Putting barriers between your own computers seems a little odd, and over the top, to me. Maybe someone else can help. Doesn't ESET come with support or documentation? Regards Pete

Sorry, I do not understand. Can you be more specific please, or at least show me what you are trying to do. What controls are you talking about -- throttle, aileron, elevator, rudder? And what version of Flight Sim? What version number of FSUIPC? I suspect you may be referring to some very old facilities which are not really needed any more with any recent versions. Mostly all you need to do is assign all controls in the same way, "direct to FSUIPC calibration", and then FSUIPC will arbitrate between them, giving preference to the one giving the most deviation from normal. Pete

Sorry, no. Nothing of mine can do that. You must have some option set incorrectly in whichever simulator you are using. Pete

Ah, never thought of that! ... A sound proofed cockpit room, maybe? <G>. Pete

No, the sound is only on the computer you installed it on. Surely, that's the big main advantage of installing an ATC program on a client PC -- so you can properly have ATC on your headset and the general cockpit sounds around you on the normal speakers. I can't think of any really good reason for doing it, otherwise! Regards Pete

It certainly sounds likely that you have conflicting assignments -- perhaps both in FSUIPC and FS. However, if things were okay and only recently started behaving badly, without any software settings changed at all, then you can't rule out hardware or USB connection problems. But check for multiple assignments first. If you haven't disabled controllers in FS this sort of thing can occur quite easily as FS makes automatic assignments when it things you've attached new controls. I would also be suspicious of the CH Control Manager. Most folks find things work better without, I think, though perhaps others will advise you more on that as I don't have any CH stuff myself. BTW you posted the same question twice with different thread titles. To avoid confusion I've deleted the other one. Regards Pete

What is there to indicate any restriction on the number of buttons at all? Folks have hundreds of buttons programmed through FSUIPC, and you can hve up to 255 separate KeySend assignments for sending actions to WideFS. Why would you think you were restricted to one only? No! If 123 is the Key Code for the F12 keypress, then all 4 of those assignments press F12. If you want F11 you need to use the Key Code for F11, as I told you!!! Every key on the keyboard has a different number -- otherwise they would all be seen as the same key which would make the keyboard pretty useless. Don't you see? Pete

It's easy enough to add an INI file option to set FSUIPC to not use the Middle Button at all. This would affect Mouse Look and the switching option between Mouse Move and Mouse Trim, so it would still be okay provided only one of those two were used, and the mouse look was handled by the controls instead. It'll be in the next interim update, 4,868, later today. Regards Pete

No. If they are the same then they do the same thing. and if you have two lines for "KeySend1" only one will be read in any case. You'd add KeySend3 and KeySend4, and use the code for F11, not F12, obviously. All the keycodes are listed in the documentation. Obviously not as it would then do the same. If you want different functions you assign to the different Keysend parameters -- 3, 4 instead of 1, 2. BTW you posted the same thing twice. I've deleted the duplicate! Pete

How will you get FSUIPC "running at the same time"? It's a part of the FS process and needs to be loaded into FS. It isn't a separate program. The fact that you can't have custom gauges reinforces what i found -- that is a completely closed program. The DLLs loaded into FS, like FSUIPC, are similar to gauges in many ways. FS's gauges are just DLLs with a .GAU filetype. Pete

In which case it will be implemented in their code, not in the root FS code, and would have to be operated by whatever mechanism might work with it. Maybe they allow keystrokes to be defined for the panel functions? If not, then the other choices are: special FS controls outside the normal range (as is the case with the PMDG 737NGX), or a mouse macro (but i think you said that didn't work), or, finally, a local panel variable (L:Var) which can be written to. In that last case it would mean having a small Lua plug-in to do the job. That can be activated in a macro file too. Good idea. Pete

If no control is logged and it is an FS defalut aircraft it probably is a cosmetic switch without real function. Does it do anything noticeably? Is it an add-on aircraft? If so it may need switching some other way -- you'd need to consult the add-on documentation or contact their support. Pete

Not at present. What add-ons use the middle mouse button, other than Ezcam (for the same purpose as FSUIPC)? Pete

In FS98 and to a certain extent FS2000 it's main source of data both in and out was Globals.DLL. But Microsoft gradually moved everything into self-contained "black boxes", and it got difficult. FSUIPc uses multiple methods to get and set data -- all internally, withing the process. It took a lot of hacking and assembly code to get there, using sophisticated debuggers such as Soft-Ice. I really don't know what you could achieve. Your best bet is to see if you can write a Gauge using the gauges interface first. Pete