Pete Dowson

Yes. You can run as many as you like -- I have three on one client PC. You'll need to put each copy of WideClient.exe in its own folder, with its own INI file, and in each INI file for a Client which is NOT running any application programs (i.e. which is only running a button screen), set the "ClassInstance" parameter to 1, 2, 3etc. Only 0 is used by applications. Of course with the button presses being sent to the Server all coming from one PC, the button numbers in the same positions will be identical on each screen. I use multiple page screens with the selection buttons down the side, on on the Captain's side and the other on the First Officer's side. They can be used independently, each selecting the page he wants. If you are wanting multiple screens just for more button space (instead of using multiple pages) you'll need to experiment with how to set it up so you get different pages/buttons displayed on each. Regards Pete

Okay. And that is with the standard VRi install, I assume? Without taking steps to wrest control of the device from SerialFP2? Hmm. Nothough you might have investigated the VRi facilities for programming keystrokes. Well VSPE is not the solution, it is just the means of interjecting FSUIPC control between the M-Panel and SerialFP2. VSPE enables the line of communication between the M-Panel and SerialFP2 to be routed via FSUIPC's facilities -- yes, including Lua capabilities -- but more importantly for button programming. The first thing to do is get the VSPE settings and the FSUIPC INI entries set so that SerialFP2 still works as it did before, but so that FSUIPC can see the buttons and you can program them. Don't even think about the JS41 till then. Regards Pete

petedowson@btconnect.com Thanks! Pete

Just do exactly what it says. If you have a specific question I can help, but i am not going to reproduce what is already published, here. There's no point! If it could have been explained more simply, it would have been. Forget about specific aircraft for now. All you want to do to start with is get it working as it should out of trhe box with a default aircraft. THEN do the FSUIPC stuff with VSPE and get to the point where you can see the buttons and knobs recognised in FSUIPC. Only then start thinking about anything specific to an aircraft! I thought the question was about the VRi M-Panel. What is this part about? Regards Pete

Ah, that directs me elsewhere, to download sites where it seems I have to become a member. I am a little wary of that. Is there an ordinary download possibility anywhere? Pete

Thanks for the logs. There doesn't appear to be anything untoward with WideFS's operations, so I can only think the strange difference is due to domething vasFMC is doing. I've not encountered anything like this before (and WideFS has been going now for about 15 years), so I'm a bit puzzled. Unfortunately the two sessions are not really directly comparable because the original INI session was allowed to run for over 4 minutes whilst the modified INI session only a little over one minute. However, I'll take your word for it that the performance stays the same if allowed to run longer. Assuming that to be the case, the crucial parts of the performance reports appear to be these: Old INI 243938 Reception average whilst connected: 22 frames/sec, 13451 bytes/sec 243938 Client 3628 requests: 776 (Ave 3/sec), Data: 6395290 bytes (32137/sec), Average 8241 bytes/Process Average receive rate from "CHRISTOPHLAPTOP": 3 frames/sec, 515 bytes/sec New INI: 72515 Reception average whilst connected: 32 frames/sec, 35508 bytes/sec 72515 Client 4676 requests: 872 (Ave 12/sec), Data: 6980628 bytes (99723/sec), Average 8005 bytes/Process Average receive rate from "CHRISTOPHLAPTOP": 12 frames/sec, 1533 bytes/sec Seems that this vasFMC is somehow sending requests to the Server at a lot faster rate in the second example. I would really like to know what it is doing which generates this strange difference. There's a lot more logging I could ask you to do to find out, but I think I should try it here to see if I can work it out. So, is "vasFMC" readily available? How would I set it up to use it in the way you are doing? If you could sort me out a "starter pack" for it I will do the investigations on my own systems. Thanks & Regards Pete

Strange. Neither of those make sense unless something else is wrong, or that vasFMC program is written very inefficiently in the way it requests data. The WaitForNewData time only gets used when an item of data is first requested. It avoids things going wrong from incorrectly providing default values (generally zero) until the true current values arrive from the Server. Once a program has requested all of its data once, the time out never gets used again, so for this to make any noticeable difference either the connection is being continually re-made, or the program is asking for one item of data at a time over a noticeably long period. The Pollinterval merely controls how frequently the client sends a "dummy" message to the server, in order to reassure the server that it is still operational. Since the server won't time out the Client for something between 10 and 20 seconds, having dummy messages sent 5 times a second, as you are now doing, makes no sense. The values in the INI file have been evolved and tuned for best performance over many years and really should never need adjusting except to make of for problems elsewhere. Didn't you bother to check the WideFS logs as I suggested? Regards Pete

Possibly not, but it would be worthwhile checking the list of services running to make sure that one still is. You imply it WAS in the untrusted list? How did it get there? Erno, neither have anything to do with FSUIPC specifically. What are you reading? To do either of them is just a matter of editing a line using Registry Editor. By all means back it up first (make a restore point), but if you only change the entries specified you can't do any harm. I get the feeling from your answers that you haven't yet looked in the right place. It's the Announcement entitled "Help with FSUIPC4 code signature problem". Also, as I already said, by the time the Installer reports any code signature problems, the Modules folder, with FSUIPC4.DLL in it, has already been produced, so I now I'm not really understanding what you are talking about. With you not showing me any log files I'm really not able to help you further. If you don't understand he easier options, I guess so too. Shame though. It might have been quite easy but I'll guess we'll never know! :-( Regards Pete

Sounds like you have one throttle reasonably calibrated and the other one not calibrated at all, or completely mis-calibrated. Sounds like you've made a bit of a mess of the FSUIPC settings. It is probably a lot easier to simply delete your FSUIPC INI file (from the FS Modules folder), get everything working reasonably well in FS BEFORE trying to be clever with FSUIPC. Then, and only then, re-calibrate for more accuracy in FSUIPC. I can't tell you what you've done wrong, but if you want me to then the only way is to show me the [Axes] and [JoystickCalibration] sections from the INI file. You can do this before you delete it if you like, in case it's an easy fix. Regards Pete

Can you not find the Installer Log file and show me? It shouldn't be hard to find -- look in the FSX Modules folder. Have you tried running FSX? Is there an FSUIPC4 log file to show me? Actually the installer has to have installed the DLL before it can apply the security check. Possibly the check is also failing when you run FSX. But you may have a Log to show me. But that contradicts what you said earlier, that . Are you getting a bit mixed up? Which is true? Without seeing any logs I can't be definitive, but it won't be a problem of FSX or FSUIPC, but of Windows. Something has messed up Windows. Depending on the cause of the problem, the only solutions I know of are: 1. Re-allowing of the cryptographic services in Windows. Many folks stop these running in the hope of more frames in FSX. 2. Removing "simFlight" from the untrusted publishers list in Internet Explorer 3. Applying one or both of the Registry patches described in the Announcement in this Forum on the subject. 4. Complete re-installation of Windows. Maybe there are other fixes, but I've not come across any. I used Google to find some of these. Regards Pete

Yes. WideFS works with all versions of Windows since Windows 98, and possibly earlier. It doesn't need anything more than a properly working network between your PCs, but it makes it easier (less configuring) if you make sure the Workgroup name is the same on every PC. Win7 has a different default workgroup name to WinXP. Regards Pete

I don't see why! The hassle over these past so many days is quite evident -- not just for me but for you. And it turns out to be rather down to something a bit silly because the question being asked, "where is the user guide" was answered in the document purportedly read by you, and referred and answered again in my replies. I therefore think both terms apply. Why would you think them insulting? Insulting to whom, me or you? And if insulting to you, why? In what way does referring to an inanimate situation insult anyone? I'm sorry, but the way you write and deal with things is very strange to me. I try to point to the answers, not necessarily answer directly, as this is a better way to help folks understand how things work. I pointed you to the answer to your question quite a few exchanges ago, yet you persisted in being rather blind to what I was saying. I persisted in trying to help nevertheless. I do my best, but you cannot expect me to understand that the question you are really asking, in your head, is in no real way relating to the one you put in writing. I'm sorry you feel my support is less than perfect. Perhaps you will never come back for more. If this is the case, so be it, but I'd prefer you'd at least make an attempt to see all this in a reasonable light. Regards Pete

Was one of those Forums one for WidevieW support? Not sure if anyone here would be able to help. I assume you don't have WideFS enabled in FSUIPC4, because that uses ports 8002 and 9002 by default. I think FSX's SimConnect opens a few. Regards Pete

It is evident because you still asked where the FSUIPC User Guide is, and it tells you clearly in the first few lines of that Installation document, in the very section I reproduced part of for you earlier on and which you still persisted in ignoring! You never asked where FSX or the FSX Modules folder was, which is what you now seem to say you had difficulty with, but where the FSUIPC user guide was, which was told to you in black and white in the Installation guide.. Once I saw this I opened under administrator and my problem was solved. But that is only relevant to MANIPULATING (i.e. changing or inserting files), not simply reading them. And it doesn't apply to the FSX Modules folder in any case as special provisions are automatically made for it! I've no idea how it would have possibly helped as it is totally irrelevant to both Installation and finding the documentation. It is never necessary to open anything under administrator unless you want to CHANGE something in one of the restricted folders. Windows simply protects the folders against changes, not against finding things and reading them! You never have to run "as administrator" to view the FSX folders (or in fact anything in either Program Files folders), and the Modules folder is a further exception in that you CAN change things in that because it is automatically made fully read/writeable for you by the FSUIPC4 installer. I have honestly never known anyone have any problem at all finding this folder and I am sure that trying to write about administrator mode in the Installation guide would not help anyone at all -- it is more likely to bewilder and confuse, in my opinion. The installation phase is deliberately kept to its simplest and most automatic levels, and it has worked well for four years without any of this silly hassle. Certainly neither Program Files nor Program Files (x86) folders are hidden from you, ever. I honestly think you must have got mixed up somewhere, and it could have certainly been resolved many days ago if you had asked the question you appear to have been unsure of than the one clearly answered in the evidently unread portion of the Installation guide. :-( Pete

By WideFS 6.71 you must simply mean the version of WideClient.EXE you have installed on your client PCs, because WideFS7 is the version which works with and inside FSUIPC4. You do not purchase specific versions of FSUIPC4 and WideFS7, but should keep up to date. The oldest supported versions of FSUIPC4 and WideClient are 4.60 and 6.78 respectively, but you will find later versions (4.624 and 6.823, respectively) in the Updates Announcement, as referenced for you by Andy. How on Earth can you miss it? The link is where it tells you about delivery: Anyway, why not refer to the documentation you get with FSUIPC and WideFS, or even read some of the Announcements here in this Forum? Regards Pete

License for what? Do you mean FSUIPC Registration? The signature checking on the FSUIPC binary is a precaution against file corruption, tampering, and virus infection. The signature by a publisher assures you that the program is as it sohuld be. If a signature fails the program should not be run under any circumstance, because it could infect your system and do untold damage that would be hard to remove. This check is performed in all cases no matter whether you have paid for and registered FSUIPC or merely using it for application support, in its free unregistered form. Merely registering it will make no difference. You therefore have something else going on which is not at all related to registration. What was "everything you said in the post posted by british aviation"? So far you've given me no further information than "When i try to install ". I have no idea even which version of FS you are using, which version of FSUIPC you are trying to install, or what Windows operating system you are using. Before we can go any further I think you need to fill in some of these essential details, please. And show me the FSUIPC Install log and, if there is one, the FSUIPC log, from the FS Modules folder. Regards Pete

That's handled by the MIXTURE controls. It always has been on all jets in all versions of FS. Full lean = cut, full rich = idle. You mean for each engine? Of course. There are Mixture1 lean, Mixture1 rich, Mixture2 lean, Mixture2 rich etc. If you want to find out the FS internal names for any controls and you know how to operate them on screen with a mouse, or via keyboard short-cuts, simply enable FSUIPC event or axis logging, operate the controls, then check the log to see what happened. The number and name of the controls are logged if what you did genuinely is controlled by some. Regards Pete

Do you mean "toggle fuel valve eng1"? Enable event logging in FSUIPC's Logging page, operate the button. check the log. Is it being sent to FSX? If so, that's all FSUIPC can do for you with that control. It is then up to the aircraft concerned to do what you ask, if it is designed to do so. What aircraft is this, and where are you seeing the fuel valve on screen? Are you sure you don't mean to operate the idle/cutoff lever, as on the 737 throttle quadrant, the one used to start the engines? I don't think the separate valves are directly accessible in many aircraft. I think they open/close automatically when needed. Pete

And did that compile without an error? What is "heading" defined as? It fails because "aileron_trim" is a number, a value, and you are asking FSUIPC_Read to place a value into it! Values cannot be placed into values, only into memory. You missed off the "&" -- please see that in the original: ("&heading"). The prefix & tells the compiler you want the address of the variable -- in other words a pointer. Best if you have a little reference book to C syntax. You would have seen this very quickly. Either that, or perhaps take a little more care when copying code? ;-) Regards Pete

A decent setting for one should be reasonably well suited to all. If you mean for FSUIPC calibration, the mechanics of setting things should be similar. The FSUIPC User's Guide is the authoritative reference, however. I can't offer specific advice for partiular hardware -- I don't even have any CH or Saitek controllers. Not in FSX itself, no. You can have different assignments and calibrations for different aircraft or profiles for aircraft types in FSUIPC. Regards Pete

What version of FS? What version number of FSUIPC? What is "the avidyne software"? There is no such thing unless you create one. Many FS add-ons are simply not susceptible to this treatment in any case. Please see the FSUIPC User Guide. There are pictures there to help, too! Regards Pete

Evidently you have NOT actually even referred to the Installation guide section I just pointed you to, let alone read it properly if at all, as it tells you exactly where to find all of the documentation and other extras which are installed with FSUIPC! That is why I referred you to it! :( :( Pete

Not that I know of, none such reported. And I use pmSystems all the time with the latest versions of FSUIPC4. Have you tried the current interim release, 4.624? See the Updates Announcement. If you want further assistance I need to see the FSUIPC4 installer log and the FSUIPC4 log. Close FSX first. Both files will be in the FSX Modules folder. If you stay with 4.30 please never come back for Support! I can't support old versions. Regards Pete

You might, but you don't get any support if you don't keep up to date. Download and install 3.98, of course! Then even possibly, optionally, get the very latest, 3.989 from the Updates announcement. Pete

You can do that, but it only works with them all connected and assigned at the same time if either they are all perfectly stable, never sending any spurious or jittery values to FS when not being touched, or they can be "parked" in a calibrated null zone where changes they send are ignored. With FSUIPC you can have assignments which are aircraft or profile-specific, so that FSUIPC automatically changes assignments according to what aircraft you use. That solves those sorts of problems. It also provides a more accurate form of calibration where you can be sure that "parked" or central positions of levers and yokes and sticks aren't going to interfere. I have read the passage above three times now, and I am still not sure. Just to see if I am correct: is it possible to disable ALL controllers in FSX, clear ALL the relevant controller assignments in FSX and assign all axis and buttons of all the connected controllers using FSUIPC? Yes, of course. But you don't need to "clear ALL the relevant controller assignments in FSX" if you simply disable the controllers themselves in FS. That makes FS ignore any assignments you might have made. Regards Pete