Pete Dowson

Well, if you could find out what it is warning you about maybe I could help. Perhaps Wilco support can tell you? Not sure why or how that would be, but then I have no idea what Wilco use FSUIPC for, if they do at all. How? All the installer does is copy the files in for you. It changes nothing of your setup other than update FSUIPC.DLL. The main reason now for the installer is to help folks get over assorted problems registering under Vista and Windows 7, which were becoming more and more common. The installer provides Registration options. Regards Pete

A few messages ago in this thread I did say "This is obviously only for FSX and ESP, as 090C is new to FSUIPC4. It isn't available for FS9. ". Did you somehow miss that? Offset 090C is not listed in the offsets list for FS9 and before, only in the update for FSX, and coloured in that list to show it is new. The other offsets you use are okay. Please use the correct documentation for your endeavours. Pete

But this is a question about the PFC driver, isn't it? Is this the quadrant connected via a serial link and driven by my PFC driver? If so, you need to do it all, calibrate the levers, in the PFC driver's options dialogue, not in FSUIPC. Please refer to the documentation provided. For axes assigned and/or calibrated in FSUIPC there's no distinction about what make they are. The instructions provided apply to all. What does that mean? Joystick assignment and calibration is just joystick assignment and calibration. Follow the steps as documented, and even in some areas illustrated with pictures. I cannot undertake to reproduce documentation here when you have it on your system and can refer to it at your leisure on your own system. If you have specific questions, by all means ask them. but detailed guidance for the use of my PFC driver is provided in the PFC driver documentation, and for FSUIPC in the FSUIPC user guide. But I think first of all you need to decide what it is you actually have there. Regards Pete

No, I don't mean that. I just mean run it at least once after a correct install, so that the FSX.CFG file can be found in its proper place. Well, it certainly looks like your install of FSX went wrong, because there's no registry entry for it showing its SetUpPath as there should certainly be. The "log not attached" being the extract from the Install log, you mean? Where it says "... NOT found! Asking user to find the .EXE instead ...", at that point it asked you, the user, to find the FSX.EXE and select it in a file selector dialogue it presented. Had you done that, FSUIPC4 installer would have continued its install checks and may have proceeded to a successful install. Did you abort it there? If so, why? If you had continued and the remaining checks turned out successful, FSUIPC's installer would have provided you the option to fix the missing Registry entry for you. Regards Pete

Okay. I'll look at that. Thanks, Pete

What's "buzzing" mean? You mean a sound? FSUIPC has nothing to do with any sounds. Settings of what? there are no sound settings. The changes from version to version are clearly listed in the History documernt. There has never been any sound facilities in FSUIPC. Regards Pete

You need to install AND run FS before installing any add-ons for it, as the files the add-ons need aren't there otherwise. Regards Pete

If you mean registering an application with FSUIPC, that hasn't been necessary for over three years now. Regards Pete

Right. This is obviously only for FSX and ESP, as 090C is new to FSUIPC4. It isn't available for FS9. As I say, I don't know VB. But That "Of Integer" looks odd to me. Is it saying the value you will tread is an integer? Because it isn't. The 2nd line implies the fuel is a double -- i.e. a 64-bit floating point number. Which it isn't. As the offsets list shows, this value is a 32-bit floating point number, a "float" in C/C++ terms. I don't know what type that is in VB -- "single" perhaps? Which part of that code actually connects to FSUIPC and reads the value? Apart from the conversion to a string it seems to be only declarations. Don't you have to call some function to do that? In C there's first of all an FSUIPC_Open, to make the connection, then any number of FSUIPC_Read and FSUIPC_Write function calls, and an FSUIPC_Process to action them. An FSUIPC_Close is used to sever the connection before terminating. I suspect you are going to need help from someone who knows VB. Regards Pete

I don't know VB at all, except, yes, a hexadecimal number which is expressed in C/C++ as, for example, 0x0B74 would be something like &H0B74 in VB. Do you have any books on VB so you can find out a bit more about programming first? If you want help here I think you really need to ask specific questions. Saying you "don't understand offsets" is a bit meaningless. What is it about "offsets" you don't understand? The fact that you put the offset value, in hex (or decimal) into function calls, to tell FSUIPC what you want? Just think of them as identifiers of data if you don't understand computer memory addressing (which is what they really are -- offsets from a known base into a 65kb area of memory). I am pretty sure there are examples in VB in the FSUIPC SDK. Have you looked? There's also a lot of help and a tool you can use -- see the sticky thread called FSUIPC Client DLL for .NET near the beginning of this Forum. Regards Pete

There's no way I know to get into CFS3. It isn't like CFS1, CFS2 which were both based on FS with its openly linkable modules structure. CFS3 was a completely different development, and not open to additional modules. You'd need to hack into it and make hooks for yourself. A pretty laborious job I should think. Regards Pete

Fixed in 4.535, now available in the Updates Announcement. As often the case with these conversions over from the FS9 code, it was a typo. It was actually using offset F000 not 1F80 internally! Duh! The strange corruption you saw in TrafficLook was the result of the corrupted details in the 40 bytes at F000, and these then affected further attempts. FSUIPC wasn't hung or in a loop as it first looked. The fact that it's taken 3 years to discover this seems to indicate that the facility isn't used much in FSX, if at all! ;-) Best Regards Pete

Okay. Please download 4.535, now available in the Updates announcement above. The facility (a "Sync Pos" button on the 4 throttles, 4 props, and 4 mixtures pages) is now working as well as I can make it with the resources I have here, and was also checked on a friend's pair of Saitek quadrants, so it should be okay. Here's the note describing the addition in the Announcement: 5. Added a position synchronisation option to the 4 throttles, 4 prop pitch, and 4 mixtures calibration pages so that multiple levers can be calibrated to line up when applying the same inputs to FS. An extract from the next User Guide update is included in the ZIP explaining how to use this facility. Feed back is requested, please. when proven in the field this option will be ported to FSUIPC3 for use the FS9 etc. Let me know, please. Regards Pete

The fuel tank capacities are provided by one offset location for each tank, and the level of the fuel in each is provided in another offset location for each. The offsets are listed quite clearly in the documentation -- check offsets 0B74 to 0BA8 for the more commonly used tanks and 1244 to 1260 for the extras some aircraft have (2nd and 3rd centre tanks, and 1 or 2 external tanks). Is there something you don't understand about these? Regards Pete

No it did not! The installation was completed by the time the Registration option was presented! You do not have to register, that's why there is a cancel option! The whole registration part is a follow up to installation for your convenience, should you have wanted to. Please do tell me why you thought installation was aborted. Is there any possible indication that it was? Did you read that it was aborted in the Log it showed and which was also installed? Did you see all the files being deleted? Tell me, please. I don't understand why you would misunderstand it so extremely. The installer is one I've been using for FSX for three years now. Regards Pete

It only requires a key if you want to use the extras, the user facilities. For its intended purpose, as an interface between applications and FS -- as originally provided by FS5IPC for FSW95 and FS6IPC for FS98 -- it is free. Maybe that is what you read? Regards Pete

If it is the same error, saying connection refused, then it has either got to be a firewall -- or an inaccessible IP address. Virus checkers are not relevant. Actually, looking again at the Log from the client: IP Address = 62.157.140.133 that IP address looks wrong. Surely that isn't the true IP address of your Server PC? It looks more like an address for an external connection, on the Internet somewhere. Perhaps your Router is mapping the addresses and its DNS (dynamic name server) is translating "DIMENSION8400" incorrectly? Check the IP address of your sever PC. It would more likely be something like 192.168.xxx.yyy. Have you assigned a fixed IP address? If you know its address try using "ServerIPAddr=n.n.n.n" in the Client INI nsteasd of "ServerName=..." in order to get around the incorrect name translation. Regards Pete

There's no need to do that if the PCs are in the same named workgroup and both running Win XP or later. There's no way to do that (and no point). Actually, WideFS doesn't use folders and needs nothing shared, but maybe programs you are using do. That almost always means a firewall block. Yes. This server message means nothing ever got through from any client. Running the filechecker on an unconnected client obviously see much to report. All the evidence points to a firewall blocking the connection, on either or both of Server and Client. Regards Pete

Sorry, I don't understand what you want to do. Are you writing a program which interfaces to FSUIPC? Are you wanting to read fuel levels, or change them? What programming language are you using? Regards Pete

I assume you mean using FSUIPC? If so, the best place to read about it is really the User Guide for FSUIPC. it is all explained at much greater length than I could here, and with pictures! Briefly, get into the FSUIPC options (in the Modules or Add-Ons menu, depending on which version of FS you are using). Find and click the Key Presses tab. Under where it says "Program keyboard controls here" Click the SET button where it says enter your keypress, and enter it (Shift + N as you wish). Then click the down arrow in the part below to reveal the list of controls you can assign. find the "Toggle nav lights" one and select it with the mouse, then click Confirm below, and OK to exit. It really is explained in more depth in the user guide. that is why I wrote it. Regards Pete

That's okay. I'm busy this weekend with other things in any case. I will have an FSX update ready some time on Monday. I've not finished it yet in any case, and will need to write something about it as well! ;-) Regards Pete

I have nearly completed changes to allow close synchronisation between throttles (also mixture and prop pitch levers), but at present only for FSUIPC4 (FSX and ESP). When I know it works okay I'll port it over to FSUIPC3. You didn't say in the thread whether you use fSX or FS9. I see that "duckbilled" is using FSX, but i could do with more than one tester. I can't test it properly as I only have a silly little game pad with spring-loaded mini joystick paddle things. My main system is PFC so uses my PFC driver. Regards Pete

I'm not surprised. It looks like it got into a never-ending loop. Yes of course. So I don't waste time trying to emulate what you are doing the wrong way, and not getting a result, could you turn on FSUIPC IPC write logging, and just run that test again for me. I need to see the exact writing sequence so I can do the same here. I'm afraid I might not get to this till Monday now. Tied up today with some other big changes and I'm busy with other things over the weekend, but if I can repro it quick i'll fix it quickly too. Regards Pete

I don't think that's anything to worry about. Unlike FSX and ESP, FS9 is not dependent on much outside its own structure. It was written before they had all these side-by-side libraries and manifests and things which complicate matters now. If it is a problem of FS installation, it won't show in the Registry. If you are concerned then there is a repair tool for the Registry provided by Flight1 -- see http://www.flight1.com/view.asp?page=library I really think it best to do what I advised before. i.e. rename your FS9 folder, and move your FS9.CFG and Scenery.CFG file to a safe place -- so as not to lose anything, then install FS9 again (and the 9.1 update), in the original folder name. That will hopefully fix the registry. Check it before adding anything, then add FSUIPC and recheck it. If that's okay, you know it was something you've added, and you now have the original texture and other scenery folders in FS9 to compare or replenish from. Doing it this way you can still return to your fully-added version any time by renaming folders and restoring CFG files. As I said, I always have a "virgin" (untouched by add-ons) installation as well as a fully-added to installation, and swap between them by folder renaming and FS9.CFG/Scenery.CFG exchanging. That way allows me to narrow down on these things a lot faster. Regards Pete

Hmm. not sure what you mean there, sorry. I am really at a loss to understand what it is you want to do, as nothing accords with my understanding of what a motion platform is all about. I'm sorry I do not understand you, but perhaps you will forgive me for not being able to help at all with something i don't understand. I have not included any humour or criticism, only emphasising again and again what I understand and what i do not. No, that is absolutely not so. One of the most effective small platforms I have tried was a small D-Box supported one as supplied by RC Simulations in England and demonstrated at a Birmingham show earlier this year. It did just support a seat, but again it was the acceleration effects which it reproduced, and very effectively even though no part of it ever rose or fell by more than a few inches. So the screen and controls always remained in the correct place relative to the pilot. I have seen and tried others, such as those at the Lelystad weekend in the Netherlands, which moved a little more, but carried the screens and cockpit controls with it. There are many ingenious solutions, but all of them that I have seen seem to be of the acceleration, and so "seat of the pants", variety. Sorry, it is obvious now that you do not understand my words as much as I don't understand your intentions. The current pitch, roll, bank and other parameters are clearly listed and available, if you wish to use them. What is the problem? How can I advise you on something different if that is what you think you need? Or I you merely asking for me to search my documents as you yourself could do so? If that is all you wish, just look at offsets 0578 - 0580. Regards Pete