Pete Dowson

You need a special cable to link PC to PC directly, one with the wires crossed over. Ask in the store for an EtherNet or Cat5 crossover or PC-PC cable. That IP address looks like an external IP address, one on the World Web. Are you sure that's right? Most local PC networks use IP addresses beginning 192.168...., though I know there are less used alternatives. Maybe that router is setup incorrectly? I would recommend setting fixed IP addresses in any case on all PCs on a local network, especially when used for FS, as it stops those intermittent blips in performance when Windows goes and asks for IP address data. Regards Pete

Why not use the view Up control, instead of terribly inefficient and re-assignable keystrokes? Now that I know you are using FSX, I would ask why you don't use its splendid camera facilities instead. You can set up your own cameras to do what you like, each with their own control/selector. Ask around in the FSX forum. I'm sure someone there will show you the ropes. ;-) Regards Pete

FSUIPC3 can, like all of its predecessors, only handle joysticks through the Windows "joy" API. This provides for 32 buttons, 1 POV and 6 axes (XYZRUV). This interface is simple and efficient and was used by everyone until the invention of the over-enginerred, over-complex, and rather slow "DirectInput". Even FS, when it used DirectX for other things like the screen, still used the old joy interface until, I think, FS2002. The DirectInput interface can handle up to 64 buttons, 4 POVs (my names PQMN) and 8 Axes (XYZ Rz Rx Ry, S1, S2 which I name XYZRUVST). I changed FSUIPC's axis assignment facilities over to DirectInput during the re-write made necessary by FSX, so FSUIPC4 supports 8 axes and 4 POVs (as axes), but still uses the older "joy" API for the buttons (so, only 32) and 1 POV (as 8 buttons). However, the work involved in rewriting FSUIPC3 in this area to do the same is huge, and it simply isn't worthwhile at this stage. I have too much to do going forward. I am only applying easy changes to FSUIPC3 arising from ones first made to FSUIPC4, and that particular change is far from easy. There should be a solution for your 6 axes, though. The interface program should be supplying those axes as the same 6 supported by the "joy" interface, not 5 from that set and one from the DirectInput set. That makes no sense. It may well be as easy as a Registry change to do that -- but you will need to talk to the people who know your interface. Regards Pete

No idea how you lost your settings, but if they were in all places, including FSX and GoFlight configurations, it sounds like your FSX session crashed rather than terminated correctly. FSX in particular only saves its settings when it closes normally. FSUIPC's settings are saved in its INI file when you OK out of the options and settings dialogue. You will certainly not easily lose those. There's nothing different about a set of buttons and knobs just because you change aircraft. You have to decide what you want them to do then assign the appropriate functions, no matter what aircraft you use. At least with FSUIPC assignments you can make them aircraft-specific, so they switch over when you load different aircraft. I don't know in CHCM or GoFlight's software can do that. Regards Pete

Yes, as far as I know. GoFlight's own software is completely independent to FSUIPC. In fact I think you can mix them in any case, even on the same unit. Just running GFdisplay does nothing. It is a free program provided for programming the way the lights work. It is not intelligent. It doesn't know what you want the lights to do unless you tell it, through its parameter file. So, you programmed the "press" action for Gear Down, but forgot to program to "release" operation to tell it to do Gear Up? That's because the GoFlight software is written specifically to drive GoFlight units in the way they were designed to be used. FSUIPC is a general facility for assigning whatever you like wherever you like. Greater flexibility has a price -- you have to do more work to use it. If the GoFlight stuff does all you want, use it. Only use FSUIPC for stuff you want to do differently! Sounds like you've assigned the space bar to do something else -- you might have done that in FS, in FSUIPC, or maybe even elsewhere? You'd need to check this yourself. FSUIPC doesn't touch the keyboard unless you've asked it to. Regards Pete

What version? You forgot to mention it! :roll: If it isn't 4.40 or later, please update it. Regards Pete

Have you also assigned and calibrated the rudder through FSUIPC in the same way? Otherwise it cannot work correctly. It is using the rudder and has to balance the two. No. i have always used it in my cockpit, but it does depend on routing the complete rudder control through FS, otherwise they interfere or simply prevent operation. You never fly with the tiller. It is completely inoperable as soon as the wheels leave the ground. There's a gradual crossover from tiller to rudder as you accelerate. The default max tiller speed is 60 knots (GS), meaning that at 30 knots you have half the control from the tiller, half from the rudder. This is all because the only way to steer on the ground in FS is to use the rudder. FSUIPC is merely simulating a tiller. Regards Pete

FS has never really simulated the hydraulic subsystems very thoroughly in any aircraft. FSX has added a little. In SimConnect there is only the one Hydraulic toggle switch, and yes: You've found it. Regards Pete

Did you make your own version of that Microsoft-compiled LIB to suit your Borland compiler? I don't think LIB files are freely exchangeable between different makers' development systems. You'd need to use the source of the library, which is included in the SDK. Alternatively, did you look at the BCB5 stuff in the SDK? Maybe BCB6 isn't too incompatible with BCB5 and the stuff in that part of the SDK will work for you? Regards Pete

I thought that was explained in the documentation? Those rotary switches operate like toggle switches. One lick -> on, next click -> off, and so on. If you want every click to count to have to program both press and release. I just checked. The answers to your questions are in the user guide, and even in the right place -- the section about buttons. Have you never looked? Things like this are explained there for a reason, so that you can easily find out how to use the facilities provided! Exactly what I said, and as explained at greater length in the documentation, which is why I wrote it. Please read the section entitled "Programming the buttons". I shouldn't need to repeat extracts here! :-( Pete

Do you mean for AI traffic? If so, they are both available through FSUIPC, in the TCAS_DATA2 structure -- the fields both (incorrectly) called "chICAO[4]" in the SDK documentation. Call them chICAOdep and chICAOarr instead. For AI? I'm afraid FSUIPC cannot supply those values. For FSX you can probably get them through the SimConnect interface, but I never figured out how to decode the binary data correctly for those in FS2004. Not sure what program you mean. FSInterrogate? In any case, the SDK's "Programmers Guide" is the correct source of information, and all four TCAS tables are defined there in some detail. If you mean the GPS plan for the user aircraft, the only information FSUIPC gets for any loaded plan is available in the offsets 6000 and following, those the documentation declares as "FS2004 GPS data area". These were found by others, and I really cannot vouch for any of it in FSX, but some of it does work in FS2004, though by reports not consistently. As far as I know the only name and time data available is that relating to the previous and next waypoints, not the complete route. Regards Pete

There are only two possibilities: (1) the key is in fact invalid, possibly a forgery, or (2) the system date in your PC precedes the date of purchase of the key. If you are sure it cannot be (2), please send me all the details, to petedowson@btconnect.com, and I will check them here. Regards Pete

Those are FS control numbers, and I have ALWAYS provided such lists, since FS98 days. They are the numerical equivalent of the named "Key Events" or FS controls you see in the FSUIPC or FS assignment facilities. You can use them when sending controls through the FSUIPC offset interface via offset 3110, and they appear in assignments in FSUIPC's INI file and in some of FS's own CFG type files. They are not offsets, but controls or events. Nothing in that list is anything whatsoever to do with "offsets". What could possibly give you that impression? Offsets are documented in the Offsets lists, provided in the FSUIPC SDK. They are for programmers, but if you need them you have to download the SDK. I am rather surprised there is no documentation explaining anything for SIOC users. Don't the makers say anything about how to use their product? Regards Pete

Did you try without the C++ style comment at the end? I would be concerned that this would be taken as part of the filename. Since spaces have to be allowed (viz the spaces in the path), the presence of a space would be irrelevant, and I don't think Windows treats // as a comment marker in Private Profile (INI) files. They aren't in C or C++. Regards Pete

Of course this message is in the wrong place, as it is entirely unrelated to code-signatures. I only found it by accident! I don't understand how going back and forth between 4.3 and 4.4 can change anything, as there is no difference is any part of the Installer (which is responsible for the registration). Having fixed things by your own experimentation I suspect it is now too late to get any information about what happened. I would have liked to see the Install log for all three installs, but I suppose you only now have the last one, and also the systems date set at the time you tried each one - the date has more relevance that whether it was 4.3 or 4.4 being installed. The most frequent reason for registration problems being reported by folks with new PCs, or ones which have been totally updated/re-formatted, is that the PCs system date has not been corrected and the registration purchase date is LATER than "today", which renders it invalid. In fact there are very few other reasons for a failing registration other than forgery. If you are absolutely sure that the date was okay, please at least ZIP up your FSUIPC4.KEY file and send it to me at petedowson@btconnect.com, so I can investigate it here. Regards Pete

About the closest to success (and maybe real success) is this thread viewtopic.php?f=54&t=73255 I was hoping someone with more knowledge and practice at this would write down the exact instructions for doing all this without getting into trouble, then I would add it to the Help announcement. So, if you do achieve it please consider writing back to me exactly how. Thanks, Pete

By itself FSUIPC4 has a negligible affect on frame rates. Obviously it is making FSX do more things (mainly the SimConnect communications), but that is all asynchronous and it is it which suffers first when your PC is under stress, rather than FSX. It is normally the FSUIPC client programs, sharing the same PC, which may have an impact. Check the FSUIPC4 log file -- see if there's a problem causing continuous re-connections. That will certainly slow FSX down noticeably. (ALWAYS look in the log for any of my programs if you ever suspect anything. That is what it is for. Which boxes for what weather source? Most of the weather "effects" suppression facilities in FSUIPC4 relate to facilities in its wind smoothing capabilities, where it is optionally ADDING effects in order to compensate for the suppression of those provided by FSX when smoothing wind changes. Apart from wind smoothing and its related effects, most of the weather facilities either only operate on weather sourced from outside using FSUIPC client weather programs (e.g. ActiveSky6, but not ASX), UNLESS you check the option for changing FSX's own weather. The latter is NOT recommended, for reasons explained in the user guide, and can certainly make FSUIPC have more of an impact on frame rates than otherwise. Regards Pete

It sounds like the Key you are using for WideFS is not valid, either one generated by an illegal pirate key generator, or one made AFTER the system date of your PC. Check the date in your PC first. If that's correct, then send me all the details for both your keys (to petedowson@btconnect.com) and I will check them here. (Incidentally, I assume "Jack Sparr" is a pseudonym, as I cannot find any records for such a registration in any case). Regards Pete

FSUIPC Macros, whether for mouse actions or anything else, are merely additional controls, added to the drop-downs for assignment just like any other FS or FSUIPC control. So whether you use a joystick, a keyboard, a GoFlight unit, an EPIC unit or, indeed, on of the PFC digital controllers, it is irrelevant where the controls come from. They are assignable because they are listed. There's absolutely no difference. Surely, you have tried before asking? The only difference is in the joystick numbers for GoFlight devices -- ordinary joysticks are numbered 0-15. GoFlight devices have much higher numbers. But you have no need to worry about that. Pete

Do you mean one of my PFC.DLL (FS9 or before) or PFCFSX.DLL (FSX and ESP)) driver modules? If so, you must surely have installed it by merely copying it into the FS Modules folder? Uninstalling is simply the reverse -- delete it from the FS Modules folder. That's it. Nothing simpler. Pete

Is this "Saitek Pro Flight Switch Panel" an FSUIPC client program? I wouldn't have thought so -- no one from Saitek has ever contacted me about this. If it doesn't use FSUIPC then installing FSUIPC will not magically make it work. BTW what's this "FSUIPC folder"? The only installation needed for FSUIPC is the presence of the FSUIPC.DLL in the FS Modules folder. Regards Pete

Does WideClient see the Server broadcasts, on port 9002? If not you either need to enable that too, or specify the ServerName and Protocol in the WideClient INI file so that WideClient is not dependent upon the broadcasts. It surprises me that it is not the Server firewall with the problem. Does the WideServer log show the client connecting? I rely on the firewall capabilities of my router. I hate my own computers in my own house stopping me having full access al of the time. Do I have something to be worried about? Regards Pete

FS frame rate is the base rate for most things like that, the same rate as FS uses for its visual updates. Lack of smoothness is not usually due to a slow data rate but an unsynchronized one. You need to throttle FS's frame rate to a value it is always going to achieve, so it stays fixed, and then read at that exact same rate. The only other way is to use a fixed rate independently of FS and interpolate between for a faster rate locally. Pete

Sorry, I've no idea what this all means. What's F11 view, and what would 25 shift+ups do? And how do you mean "will not do more than 7-9"? FSX, FS9, FSUIPC? What are you programming where and how? If you are trying to force keypresses faster than Windows can process them they tend to be merged by the recipient. Surely you are not using keypresses for an FS control use? That would be extremely inefficient and error prone. Always use FS controls to control FS. Keypresses are for other programs/addons which don't have controls assigned. Not sure why -- is this the equivalent of your copilot slapping your hand when you try to raise the gear on the ground? The aircraft has an interlock in any case and you'll get a warning beep for sure. If you want to do programming trickjs on axes you'd have to either assigned those ranfges to virtual buttons, then program the buttons with condifitons, or use a Lua plugin. That's absolutely awful! What on Earth are you trying to do? First NEVER use keypresses when there are FS controls to do the job. For each one, FS is looking up the keypress in the FS assignments to see which control it is, then it sends the control itself. All those get into the same message queue. It becomes a right mess! Second, work out what you want to do then find the best way to do it. If I understood what this was about, maybe I could advise. Pete

Widescreen? I assume you mean WideFS? The answer is in the logs: Your two PCs are probably in different Workgroups. For broadcasting to work you need them to be in the same workgroup. Just change the name of one to match the other. Alternatively, you can simply use the ServerName and Protocol parameters in the WideClient.INI file to allow the client to know where the server is without broadcast reception. You could have found out by looking at the documentation supplied in the WideFS ZIP file. That is why it is provided. Regards Pete