Pete Dowson

Can you show me the FSUIPC4.Log please? You didn't see this note in the Announcement above then? Also, temporarily try removing the FSCopilot DLL and see then if the FSUIPC entry appears. Show both FSUIPC4 Logs please. This is sounding like a bug in Simconnect's menu handling -- there was a report in the other "No Add-Ons" thread about the FSUIPC entry sometimes disappearing when FSCopilot was loaded. The gentleman changed the order of the two in the DLL.XML file and it was okay then -- but that shouldn't be needed. I did download FSCopilot, and even FSInn, but I couldn't reproduce this problem here. Maybe you actually have to use them as well. I'll need info so I can report it to Microsoft. Please als oreport it via tell_fs@microsoft.com when we've done a couple more tests. Regards, Pete

There's no option. FSUIPC4 will only install in FSX. It won't see FS9 and cannot be installed into it. FS9 and FSX will not interact. You just cannot run them both ast the same time on the same PC. WideFS clients will connect with whichever is running at the time. You need no changes that end. Regards, Pete

Unfortunately, whilst you did correctly Monitor 0C3E for me (and very odd it certainly looks), you forgot to enable IPC read and write logging as requested. I wanted to see the relationships between what you wrote and what was happening to 0C3E. So, could you do that, please? Whilst you are at it, please enable Event logging too. Looking in the code I see that there is no direct way to set the drift, or at least I couldn't find one. The code I have actually uses the FS control GYRO DRIFT SET. [Later ....] Hmmm it isn't just a matter of using this control to set the absolute value of the drift amount. It looks like the value which has to be set is the DIFFERENCE between the current value and the one required. Or at least it looks that way from the code I have. It is quite possible that this was true in FS2002 but fixed in FS2004. No one has mentioned any problem for the past 3 years, but maybe you are the first one to actually write to this offset in FS2004! Looking through my History document, I see that the last change in this area was this: That was in FSUIPC 2.96, one of the later versions for FS2002. Looking at the Monitored values it does seem plausible that this was changed in FS2004 -- if so then I'll need to change FSUIPC as well. I'm out tonight. Meanwhile, do you think you could assign a Key to the GYRO DRIFT SET control, with a non-zero parameter, and see if it changes it correctly? If so then I'll change FSUIPC to do the same. I'll try it myself later, but it will be in the wee hours or tomorrow morning now. Regards Pete

I don't have a Server, and in any case FSUIPC doesn't go on-line. The email address you used when you purchased the Key is irrevocably tied with your name to the Key. The three go together as a totally unique tracable identification. The actual email address doesn't matter as it isn't used for email, only to identiy you. Folks with no internet connection would use the first line of their address, for instance. You must ALWAYS use exactly the same details as notified to you when you got the Key. Not just the email address but your name too, to the letter. It does say this someplace. Regards Pete

Now you explain it, yes. It is the same problem as reported in another thread. I fixed it and am trying to put a release together this week. It is only a problem with unregistered installs of FSUIPC. See your email. Pete

Yes. It's exactly the same as in FSUIPC 3.709. I have no idea what is going on there and I cannot even picture it. Can you show me your starting settings in the INI file please (only the JoystickCalibration sections), and then ennumerate step-by-step what you do and what you see so I can try to replicate it? I'll also need to know your "ShortAircraftNameOk" parameter setting. SimConnect itself won't be able to mess up the way the dialogue works. It is needed to supply the aircraft name, though, and of course forward the joystick values for calibration -- unless you are assigning those directly via the FSUIPC4 axis assignments. Let me have the info and I'll try to work out what is going on. Regards Pete

I am sorry but there is no way I can or will support such an old version! The current version is 3.70 (or you can get 3.709 in the Announcements above -- that will be released as 3.71 soon). Answers: - No - Don't know - Don't know - Only if you use the currently supported version. Please re-test with that. If you think there is still some problem I'll want a suitable Log file with IPC reading/writing and 0C3E monitored, please. Regards Pete

Yes, I get that too. Not always, but most of the time. I've not yet found a solution, and I'm afraid with all the Simconnect support I'm having to do at present for Microsoft (it seems :-() it isn't high on my priority list. It's something to do with the way FSX closes down much faster. PFCFSX is certainly still tyring to send the code sequences out to the device (there's a whole sequence of them, for each display part), but it's getting killed. With my connection to FS via Simconnect now being asynchronous, it looks like by the time I get told that FSX is closing there isn't enough time -- the serial buffers are purged when the process disappears, and that's that. Similar problems will occur with WideFS's "shutdown" facilities for Clients. It isn't a "PROBLEM" in capitals as you maintain, just an annoyance. Until I can find a way around it I suggest you switch the aircraft's battery off before closing FSX. I may have to create a special thread which doesn't die for several seconds after the rest of FS, but, I'm sorry, there are more urgent things to do first. I have a similar problem in trying to find a way of rectifying FSX's omission of a "Previous Flight" facility. I like to pick up my aircraft from where I parked it at the end of the previous session. In FS9 and before it was easy -- just set "Previous Flight" as the default. FSX doesn't save one. I would like to save one automatically from FSUIPC4, but, just as for PFCFSX, by the time I can detect that FSX is closing, it is too late! I have a request in with Microsoft for an earlier notrification. Regards Pete

"The same error"? What is that -- if the folder is read-only protected, how could you copy the Install program into it? Are you saying you can write to read-only folders but my program cannot? I don't understand. Does AS6.5 write to somewhere in FSX? If you already have FSUIPC4 installed, is there something in 4.02 you are desperate for? If so I can email it to you, but I'd really much rather sort the problem out, if that's all right with you? Can you show me the actual message you are getting please? I really don't understand this as there's been no change in the part which checks the modules folder and copies in FSUIPC. If there's something I can do to get past your problem I'd like to do it, first, here and now. Regards Pete

FSUIPC4 is not FSUIPC3. It is a new program. FSUIPC3 keys are for FSUIPC3, as was made very clear when you bought them. There is a discount for recent purchasers of FSUIPC3 when buying FSUIPC4. Please check the sales booths at SimMarket. Only if you want to use the User Facilities. Please check the User Guide first, and make up your own mind. You don't need to for applications support. What does that mean? The PFCFSX.DLL (the one provided above for FSX) works fine with an unregistered FSUIPC4. You don't need to register FSUIPC4 just to use your PFC gear. Regards Pete

Glad you made it through! Well done. I wonder why the installation didn't work properly though? I think I'll check out exactly what the SimConnect.msi file does in the SDK -- I would think it would do exactly what you did manually but with no hassle. If so, I will get MS's permission to send it to anyone with such problems, or maybe even host it in my Announcements above. Thanks, Pete

Thanks for letting me know -- yet another symptom of the same problem by the look of it. Could you please be sure to report your findings via tell_fs@microsoft.com., with as much information 9which firewall program etc) as possible? Thanks, Pete

That's just one of the reaspns FSUIPC4 comes in an Installer which creates it for you. Sorry, I don't know how FSNavigator will install. I expect each module author will choose a different way, unless they use FSUIPC4 (which FSNavigator doesn't). I only chose to create a Modules folder to install FSUIPC4 into to keep some compatibility and understanding with previous versions, but it didn't have to be like that. Simconnect will load modules from anywhere -- the path is given to it. Regards Pete

One more question here. This "half way" business sounds remarkably as if you are assigning the axes to "THROTTLEn_SET" controls instead if the more usual "AXIS_THROTTLEn_SET" controls. Both sets are listed in the FSUIPC4 axis assignment dropdown but they don't behave the same. The AXIS ones only have forward thrust, the others have reverse thrust too -- your "50%" position would be the default idle. Have you tried it on a jet with reverse, to see if the reversing lever is operating when you pull back? Nothing I've looked at here in either FSUIPC4 or FSX is different to what happened in FS9.1. It does sound very much like you are doing something different and have got controls mixed up. Mind you, even then if you calibrated properly in FSUIPC's calibration section, it would map the existing range exactly in any case, so something is wrong in your settings somewhere. If you haven't actually copied your FS9.1 settings using cut-and-paste I'd advise doing that, but, please, before you do so show me the FSX Axis and Joystick Calibration parts of the INI so I can see where things aren't right. In fact show your FS9 ones as well for comparison, please. Regards Pete

FSUIPC4 is a completely rewritten program for FSX and needs new registration. There's a discount for recent purchasers of FSUIPC3. Please see the announcements. Download and install FSUIPC4 first in any case, and check the documentation. See the Important notes in the first announcement above -- FSX has some problems at present which Microsoft are working on. Regards Pete

I can't reproduce anything like that here. Can you give me more information, please? Perhaps the Axis and Joystick calibration sections of the FSUIPC4.INI file? The calibration in FSUIPC merely stretches whatever minimum and maximum values you "set" there to cover the whole range needed in FS. I can't understand what you are seeing. I need the figures please. BTW did you cut and paste these sections from your FS9 FSUIPC.INI file, as suggested? This is what I did for all my controls and they all work just the same as in FS9. If there's something wrong I'll fix it, but I need to understand it first, so please don't give up yet. Thanks, Pete

Unless you can get FSUIPC4.DLL into the Modules folder, you cannot update the one that is there. I don't understand how it is not letting you write to it. If you cannot write to any part of your FS installation you will never be able to update any of it. Are you sure you haven't logged in as some other user with no privileges? Make sure you are logged in as the person who installed FSX in the first place. You probably need to be an administrator. Or you may be able to run the installer using "Run As" and select the correct user or the Aministrator? Regards Pete

You can't have two files both named the same in the same folder. I don't know why there are two - hopefully they are identical so it won't matter which one you put there. Otherwise, right click and check that the version is the same as that you quoted me someplace (it's also built into part of bthat long folder name). Regards Pete

No. this stuff is not leaving your PC. In fact for FSUIPC4 it isn't even leaving the FSX Process. That's what so daft and annoying about it all! Grrr. Regards Pete

Does it need to know? Sorry, I don't know. This is really a question about RC, not WideFS. Can you ask there? It probably depends on the application. It doesn't matter at all to WideFS. But if the application sees a Registry entry pointing to FS9 on the Client PC it may want to get data or stuff from there. That may be a good thing (if the data in that PC is identical to that on your Server), or a bad thing (if the data is different). But I cannot tell you. These are questions about applications which you need to direct to the application folks. All I can say is, that if FS9 is not running but Wideclient is, they will connect via Wideclient and not try to run FS9 automatically for you, even if they used to before. Pete

Good. Okay. Okay. If you want WideClient to load them for you, please check the WideFS documentation -- there's a section which tells you all about the Run and RunReady parameters. But you should test them first. Correct. Just minimise it or hide it. Haven't you looked at the WideFS documentation at all? :-( ErWIDECLIENT is an "FS Eliminator". It sits in your client PCs pretending to be FS with FSUIPC running, to fool all your utilities into connecting to it. How would you run your utilities on the FS PC? You have an FS Window (with FS in it), and you run your utilities, right? Well, this is just the same! The "gray window" of WideClient used to be used by some utilities which liked to "lock" themselves to the FS window. There's even a way to load an FS-looking Bitmap picture to make it not-gray. All this is documented you know. Really the only use of the gray window these days would be for a button array on a touch sensitive screen, as per examples in the documentation. You can re-shape the window to just show the menu bar, so you can see the connection. You can even tell it (via parameters in the INI file -- see the documentation ) to show the Network FS frame rate. 4) How to config these programs to run in wideclient pc? Most will just run. Some which need databases building from FS data will have their own instructions. Have you even bothered to try RUNNING them at alll yet? Why not do that before asking all these questions? I don't write those programs and I cannot support them. I just provide the tools and interfaces. I've no idea what there is there to NOT understand, you just fill in what you want to run. But if you don't, then please just don't use those facilities. Do everything by hand, yourself. They are only assists to make things easier, but if they make it harder for you, don't use them. I really cannot explain better here than in the documentation, else I would have done there! (I really have never had anyone else asking such basic questions. Sorry). If you don't understand anything in it, then just realise that you don't have to use any of the fancy features. If you want to use them you must have understood what you wanted to use them for, surely? Please, just run Wideclient, see it connect, then run your programs. I would have thought that would have been the very first thing you would have tried! :-( Regards Pete

Is there a Simconnect.dll readily available on the DVD? I don't know. you could try I suppose. I just cannot imagine why the installer would bother to create that complicated (but correct) folder and then not put the file into it. Very strange. Regards Pete

I'm afraid I can't quite picture what you mean. In FSUIPC4 you are using the Axis Assignments, right? Do you select the "Send direct ..." or "Send to FS ..." option in the Axis Assignments? It sounds like you might be sending them to FS. If you do, it is likely that the Sensitivity and Null zone settings are robbing you of some of the claibration possibilities. You need FS set to Maximum Sensitivity (full right) and Minimum null zone (full left). Alternatively if you select the "Direct" method you bypass FS altogether and go direct to FSUIPC Joystick Calibrations. Regards Pete

Yes, I think the TCP/IP usage with SimConnect is causing a typical queuing or bunching effect, like on a crowded motorway. I've been informed by MS that they are trying to get to the bottom of all these things. Meanwhile, I'm doing some experiments here to see if I can bypass Simconnect at all for some of the more frequently changing and needed variables. Incidentally, changes to video drivers seem to be able to have a MUCH more dramatic affect on frame rates than any of that stuff. I was using nVidia forceware 91.47 from a few weeks ago. There's now a revised download on the nVidia site (still confusingly called 91.47) which, after installation, has boosted my frame rates by 30-40%. Not only that but they appear to have got SLI working quite well too (it even specifically mentions FSX on the nVidia notes about this revision) -- on my one PC with SLI the frame rates are 50% better and smoother! I'll press on with whatever optimisation I can though, and hope that MS come up with some solutions. Best Regards Pete

Er .... that looks right for the FOLDER, in fact it's exactly the same as mine. But what do you mean by "the Simconnect folder" inside it? There should just be SimConnect.dll inside it, no more folders? If there is no Simconnect.dll I'm not surprised!!! The error message from my Installer will be the same. Without SimConnect NO ADDONS USING SIMCONNECT will work! I think you need to contact Microsoft support. If a complete re-install still isn't installing FSX properly then either you have bad DVDs or there's something about your system preventing correct installation and Microsoft need to be told. After that, if you have the Deluxe version, you can try installing SimConnect from the msi file as I suggested. But you shouldn't need to! Something is wrong and that should be reported! Regards Pete