Pete Dowson

Yes you can and yes it will. You need to register it properly, not simply copy the KEY file over. If it isn't working it is because you are making an error somewhere. Make sure all three parts (name, email, key) are exactly correct -- cut and paste from the original notification is best. Also make sure the system date on that PC is correct, or at least certainly not earlier than your original Registration purchase. Pete

Good. You should know, however, that a corrupted FSUIPC will always be detected as it is code-signed and the signature is checked on every load, so it could not actually be a corruption of the DLL itself. The updated graphics driver may well have had something to do with it, though the fact that your crash was in WEATHER.DLL also suggests the possibility of a faulty weather download or weather (WX) file on disk. The only reasons the presence of FSUIPC may have exacerbated such a problem are (a) that it reads the weather via SimConnect regularly, possibly unlike the other things you had loaded, and (b) that its mere presence would change timings and memory arrangements slightly, possibly revealing a bug elsewhere. Additionally, the weather characteristics would of course affect graphics (in the cloud renditions) and this in turn relates to the graphics drivers. Incidentally there is a later version of FSUIPC (4.156) available in the FSX downloads, above. This is a Release Candidate for 4.16, which I will be releasing properly before the end of the month. Regards Pete

Yes, ignore the "Side by Side" errors. These are all a result of FSUIPC4's flexibility in selecting the best of any number of SimConnect side-by-side DLLs you may or may not have installed. In your FSUIPC Install log you will see a list of SimConnect versions you have installed. Each time the Install runs, it tests for the presence of each version it knows about and lists them. That process in itself unfortunately creates these error entries, which are irrelevant -- it merely means that the installer issued a Manifest Probe for those versions which failed because they are not installed. Similarly, when FSUIPC4 runs (it is manifested to the original SimConnect DLL so that it can get itself loaded), it checks for the latest versions it knows about, and works backwards until it finds one it likes, then links to that. The same Manifest Probe produces the same errors. The alternative for FSUIPC4 would be to have a different version for each supported version of SimConnect, which would be intolerable. I think this marks a deficiency in the way the SidebySide system works, as it does not differentiate between an error caused by "trying" from an error caused by "doing". Maybe it should have a separate API for "trying". But that won't occur now in Windows XP. We'll see what Vista SP1 brings -- but then, more incompatibility. :-( Meanwhile, don't worry about it. It does no harm other than helping to fill your disk with a little more unnecessary logging -- and it has actually been occurring since version 4.10 of FSUIPC, which was the first version with the flexibility to cope with multiple SimConnect installs (because of the release of FSX SP1). Regards Pete

But not FS controls, which would be an easier choice. Of course any of the FS controls can be sent by writing its number to offset 3110, so all is still possible. Well, deleting the keystroke assignment in FS will free that keystroke but won't help if your driver is trying to use that very one to invoke the function! Really, for a much more efficient and reliable system I would advise programming all of your functions as FSUIPC offset writes. There's a list of FS controls available for every FS version since FS98, so you can re-program any keypress as an FS control write to 3110. An alternative way, which might be more attractive as it is more versatile (more easily re-programmable, including use of FSUIPC's aircraft-specific and button programming facilities) -- is to program each of your switches/buttons as a "virtual button" (a bit on any of the offsets from 3340 to 3363). This is how I provide programming facilities in FSUIPC for any button/switch on PFC equipment -- the PFC driver simply toggles bits in a similar (but different and reserved) area. These then show up as regular buttons in the FSUIPC buttons tab. Sounds like buggy software. Sorry, but if you want to go that way I think you need to deal with their support, and get their driver fixed. Regards Pete

I don't really understand all of that, I'm afraid. Are you saying that the driver software ("InterfaceIT"?) drive functions in FS either by keystroke or button pressing, if so where does FSUIPC come in? Or is this all about FSUIPC? I assume that "switch" is actually a button? If you are using what I call a switch (something with more than one position, on and off), it would make more sense to use the Autopilot On and Off controls instead. Where are you assigning these keystrokes? You know that you can assign keystrokes in FS as well as FSUIPC, and presumably now in your "InterfaceIT" program? There's a lot of places for keys to be re-interpreted! Really, for all FS functions, I'd recommend using FS controls all the time -- more efficient and not liable to interception/change by assorted facilities and other programs. The main use of keystrokes is for third party add-ons which don't, of course, provide the equivalent of FS controls. If you aren't assigning keystrokes in FSUIPC then it isn't doing anything to conflict. But by all means use the Logging facilities provided in FSUIPC to not only log keys but also resulting controls -- see the options on the left-hand side of the Logging options tab. Regards Pete

What action is needed, exactly? Sorry, I don't recall and don't have the reference to hand. Isn't it a simple matter of toggling a bit in an offset, something that can already be done with one of the Offset Byte controls? Regards Pete

Yes, that is why there is extensive documentation in the Advanced User's guide for the button parameters, including examples. Comments ARE retained in that section too. Flags for options checked. All those things should be programmed via the options screen, as I said. Regards Pete

Which documentation? User or SDK? Yes. The Programmer's guide in the SDK lists an "aircraft on ground" flag. Regards Pete

Sounds like the SimConnect bug which causes FSX to crash when one SimConnect client tries to read FSX data whilst you are being prompted to allow a newly-installed client to run. This is mostly fixed by the SP1 update for FSX, which you don't appear to have installed. (I say "mostly" because it doesn't fix 100% of cases). You have two choices: one is to temporarily disable your other SimConnect clients (ones loaded by the DLL.XML or EXE.XML files), by renaming them, for instance. Then run FSX and get FSUIPC "approved" (you can optionally tell Windows to always approve programs signed by me, Peter L Dowson, which would allow easier updates), and finally close FSX and re-enable the other programs. If you are not sure what you have running which is conflicting, show me the DLL.XML file, and, if you have one, the EXE.XML file. They will be found in the same folder as your FSX.CFG file -- Documents and Settings\\Application Data\Microsoft\FSX (or slightly different for Vista). The other choice, which is a good move in any case as it fixes a load of other stuff, is to download and install the SP1 update for FSX. By the way, there is a later version of the FSUIPC4.DLL available in the FSX Downloads announcement above. (4.156). Regards Pete

I've never heard of this "Sarah.dll". Certainly it is no part of FS9 or anything of mine, and neither "wants" anything from it. When you say that it's "the socket that connects to" your ISP, what do you actually mean by that? What do you know of it? Windows sockets are supported by intrinsic parts of Windows, a section called Winsock -- wsock_32.dll is, I think, the usual main socket support for all of the Ethernet API calls. It sounds like something has been installed which has replaced or hooked into part of Windows and, evidently, doesn't do the job properly. [LATER] From Googling on "Sarah.dll" it looks to me as if it is some sort of invasive hook installed with a thing called "fritz!dsl" or "FritzBox", whatever that is. Looks like a type of Spyware but it might be related to whatever firewall you have operating there. Sorry, but it really is a problem on your system unrelated to FS9 or WideFS. Try Googling on these things. Maybe there's a solution out there less drastic than uninstalling stuff. Regards Pete [Ooops .. I see I've edited your message instead of quoting it. I've done that twice recently! Must be this new Forum design. I'll need to get used to it. Sorry!]

I have just noticed this announcement on Avsim: Maybe using the FSX version will help? Pete

I never did receive any more information from you to help me narrow this down, but I had some time this morning to browse through my code. I found one place where my conversion form the FS2004 version was incorrect, and would certainly result in some PH values being set to zero when the original value (which you should have seen in your Log files too!) was most certainly not zero. I have fixed this in version 4.92, today, 15th August 2007. This updated version will be available for download from the FSX Downloads announcement above later today. Please try it and let me know. Please note that yours is the first actual feedback on EPICINFO5 since I released it for testing by EPIC users last September. I am a little at a loss to test properly here, not being an EPIC user these days. If you have any further problems, please do include the Log itself, as this would have certainly helped in the cases you mention. [LATER] Okay -- 4.92 is available now. See the FSX Downloads announcement. Regards Pete

If their USB driver interfaces with FSUIPC for all of its FS connectivity, then yes, it will work via WideFS too. However, if it produces a standard joystick-type interface which you then make assignments to via FS or FSUIPC, then it would only work for button assignment, not axis assignment, because WideFS doesn't transmit axis values. Assuming you've not bought the hardware yet, then to be safe I recommend you contact FlightDeck Technology and ask them. If you already have everything then you should be able to try it, or even read about it in the documentation (?). Regards Pete

Never heard of a problem like that before, sorry. I'm afraid none of the details you gave relate to the problem at all. If it only happens when a client connects it sounds like it may be down to a bad Network driver in the FS PC, so possibly uninstalling and re-installing the network card/device (via the Device manage) may help. To narrow down the location of the problem in FS you should find, when the crash occurs, a place in the notification where you can "click for more details". This will tell you where in FS it crashed, including location (an 8-digit hex address) and a module name, like 'FS2004.exe' or 'api.dll'. See if that helps too. Regards Pete

Not sure why you are posting here about it as it really cannot be anything to do with FSUIPC. Please make sure you submit the problem to Microsoft when the crash notification appears with that option. Also see if it happens without the "iFly" add-on, as if it doesn't you may wish to notify them, assuming they support its use in FSX. Incidentally, the currently supported version of FSUIPC4 is 4.152, not 4.15, and there is an interim update for that (4.156) available in the FSX download announcement above. Regards Pete

Don't look for offsets there -- they are most certainly the domain of the SDK where you will find a complete document listing and explaining thousands of them. Normal users, even "advanced" ones, don't normally need to know anything about those. [Axes] 8=1Z,256,D,17,0,0,0 //17 prop1 9=1R,256,D,42,0,0,0 // reverse throttle 2 10=1V,256,D,41,0,0,0 // reverse throttle 1 numbers 17 41 42 are FS functons I figured out by looking for change and a list of those whould be handy, so I can fix errors in my INI The reason the [Axes] and [JoystickCalibration] sections aren't fully documented there is that it is not intended for users to edit those manually. It is much easier to change those on-line in the Options. The "advanced" documentation for Buttons and, to a lesser extend, Keys, is there because there are many programming-type things you can do with those which cannot be done on-line. Anyway, the D (Direct to Calibration) function numbers 1-44 equate to the position these have in the Joystick Calibration tab -- 1 to 4 on page 1, 4-8 on page 2 etc. So you can make a list fairly easily if you wish. I don't want to encourage folks to bypass the on-line setting methods for those sections. There's no general convention for comments in Windows "profile" documents, as my INI files are. I explicitly allow for them in the sections I expect folks to edit manually, but not in the others. I suspect any you add will get stripped next time you change anything on-line. FSUIPC doesn't do any of that, it is a function of the way Windows maintains INI files via the Profile API. I've always left everything to Windows. The [buttons] section, in particular, has a lot of extra 'parameter' type handling specifically to retain comments and even add error messages when appropriate. The other sections really are best dealt with as intended, via the options. Good, but I've no idea what was happening, but it is confirmed that it was something at your end, or with your ISP. The Forum administrators have confirmed that the Server to which the download links connect is not the same one which was recently updated (it's even in a different country!) and that there's been no change at all as far as those links are concerned. Weird. Regards Pete

Sorry, I've no idea what is happening, but it something at your end, or with your ISP. The Forum administrators have confirmed that the Server tp which the download links connect is not the same one which was recently updated (it's even in a different country!) and that there's been no change at all as far as those links are concerned. Weird. Anyway, glad you got what you wanted eventually. Regards Pete

I get a better response from the links now than before! Strange! I have emailed the administrators for advice. I cannot do anything myself. The FSUIPC4 installer installs several documents, including the User Guide and Advanced Users guide. The fact that it does is also logged to the Install LOG. All the installed files go to the FSX Modules folder, and the message box announcing success says so! Maybe you need to re-install if you have deleted these files. Please check. If your installation failed I need to see the Install log please! Pete

There seem to be several in your situation, but it not only works fine here, but since they changed the Forum software, they are much more efficient. Possibly there's a change in the IP address to which the link resolves and some ISPs are using name servers which aren't up to date still? I'll point it out to the Forum Administration, but there's nothing I can do myself -- the links are all better than before, if anything, just like the speed and design of the Forum. Regards Pete

Ooops! Sorry -- looks like I Edited your message instead of merely Quoted it! Doesn't it accelerate anyway if you select the "repeat whilst pressed" option? If you are using the INC/DEC controls then it is really the same sort of thing as holding the + key down or the mouse button on the gauge. Otherwise, without writing a client program to do it, the only way I can think of is to program each way to not only do the INC or DEC but also to increment a count in one of the free user Offsets and test that to see whether to do several more INCs and DECs in the same button push. You'd need to reset the count when the button is released. No, it is all covered in the Advanced User's guide, supplied in the FSUIPC Zip package. They are all working fine as I type this, so if they were down it couldn't have lasted very long. Regards Pete

There's nothing whatsoever wrong with the link. Check with your ISP -- there's evidently something wrong your end. Regards Pete

3.72 is a long way out of date. Please use the current version, 3.75. I cannot support old versions. This is a video driver issue. I really cannot offer any solution other than to try different video settings or a different driver version. Are you perhaps using one of the new DX10-capable video cards, like the 8800 series? The new DX10 Vista drivers for those are known to be a little flakey at present, at least it seems so from what I have read. There may not be a fully working driver yet, if it's a DX10 card. I can only suggest trying different video driver or FS display settings. It may be related to the anti-alias or filtering, for instance. Of course, for FSUIPC settings, which are really not needed to be accessed very often (in fact not really at all once you have things set up as you like), the easiest work-around at present is simply to swap to Windowed mode before accessing them, and swap back afterwards. SP1 for Vista, postponed TWO years? I can't believe that! Surely it cannot be so? I have one PC with Vista installed but I'm hardly using it because of all the problems and real annoyances -- I'm waiting for MS fixes. In any case I suspect it is new video drivers you really need. Regards Pete

It was uploaded last night -- version 4.156, in the FSX downloads announcement. I had to make additional changes for FSX, which appears to operate the spoilers rather differently internally. Version 4.156 works perfectly. Regards Pete

Good, glad you sorted it. Not annoyed so much as a little exasperated at times! ;-) (and f course I am not renowned for my patience ;-) ). Regards Pete

Dear Pete , :? Confused :cry: Sorry , I need more explanatory details :idea: about this assignment in FS2004 & FSUIPC 3.75I'm a newbie about FSUIPC :roll: Thx for your help ... Which part confuses you? Perhaps you should please (please)_ read the User documentation first? There's even pictures in there, directed specifically at "newbies". I really cannot offer the same level of documentation here!!! If you cannot see the helpful pictures, load up FS2004 and do it there. Just go to FSUIPC options (ALT M F in FS2004), then select "Buttons and Switches" tab, then press your button, then select Assign to Control (right-hand-side), then find the "Offset float64 set ..." control in the drop down, set the Offset and the Parameter. If you'd bothered to go and look you'd have found all this really easily. Crying about it "as a newbie" without trying to help yourself at all is not going to solve anything. :-( Pete