Pete Dowson

What? I don't see how that is possible -- the bits are individually tested in every place they are affected. [LATER] Aha! Yes. Sorry, found it. A silly typo in one new line of code. I'll fix that. Ah, yes, that is certainly true. In actual fact in all 4 cases the source data is the raw input. So, for instance. That is where they are being intercepted, before going through calibration. Hmm. That is a bit more of a problem. All 4 will have to be re-thought, otherwise it becomes the job of the program which is intercepting them to do their own "calibration". Well, you can work it out of course as FSUIPC has to do. But this is just another result of the input date being raw, not calibrated. I'll have to think about whether to and how to re-design the whole facility here. The similar one for the control axes was designed deliberately to by-pass my calibration, as it is used for "fly-by-wire" where the controlling program wants direct control over the end values, not a "simple" interference. I assume your use is different. You aren't after direct control, where you are deciding exactly what brake, flap or spoiler values to use, but simply want to reduce or change the actual values which would have been applied? Maybe before I change anything at all we ought to have a longer discussion? My first inclination is to put the "raw" value through my calibration routine before providing it in the 34xx offsets. Would that be best? Regards Pete

Okay, so it isn't the weather. This is strange. I've not had anything like this before at all. I don't know how to proceed now. wrong with your FS or Windows system, but what? If I was there, with your PC, I'd use debuggers and all sorts of tools to determine what was going wrong, but I can't see how to do this from here. Just as a last gamble, could you please send me a directory listing of your FS modules folder. I attach a little batch file which will produce one of these. Just unzip the ListDir.bat file to your Modules folder, then execute it (double click it). It will make a small text file called Dir.txt. Zip it and send it to petedowson@btconnect.com. Well, if you are starting with a complete reinstall, test with FS9.0 first before doing the update to 9.1 in case the latter is corrupt. Regards Pete ListDir.zip

I have implemented both Flaps and spoiler axes disconnection facilities in an interim version of FSUIPC (and FSUIPC4), but I have not had time to test them properly. If you would like to download the updates and try them, letting me know, I'd be grateful. Thanks. These are the links: http://fsuipc.simflight.com/beta/FSUIPC4221.zip http://fsuipc.simflight.com/beta/FSUIPC3781.zip The implementation details are: Hope this is clear enough. Regards Pete

Aha! Yes, I see that too. It isn't the Wind settings specifically, but the "Allow changes .." option. This must have been what you were seeing before. It also affects the Visibility and Clouds pages with the same option. It is a result of my moving the "Allow changes ..." option off the Miscellaneous page with copies instead on the Winds, Clouds and Visibility pages, where it has some significance. Seems I omitted to remove code from the Miscellaneous page processing. Sorry. Thanks for this clearer report. I will have this fixed in the next incremental release, or at least in the next main user release which I am aiming for the end of the month. Meanwhile, please visit the Winds, Clouds or Visibility pages after the Miscellaneous page to re-check that option. Regards Pete

Please ignore this in 4.218 because all that was changed in 4.219 which I uploaded this afternoon. That seems fair. I can't SPEED UP FSX smoothing, I only try to slow it down when it is faster! That's the whole point. If it is being changed by FSX I don't even know what its ultimate target is, in any case, only what it is trying to set at the moment. If that is within the range you chose then it is okay! ;-) No smoothing I've ever implemented speeds things up, ever. Not possible, not desirable. Regards Pete

It isn't actually my page at all, but Enrico Schiratti's, as it points out. There is a link there to this Support Forum, and the Support Forum is nicely equipped with an Announcement facility, where I make Announcements and keep folks up to date with what is going on. ;-) I don't release major updates as often as interim ones here, even if Enrico would actually update his page so often, which he doesn't. I was made extraordinary clear with the "official" 4.2 release that the wind smoothing, new in that release, was "experimental" -- it actually says as much on the screen you so kindly posted here (as if i'd not seen it before! ;-) ). There's also quite a lot written in the documentation as well explaining a lot of the problems with doing much with FSX weather. There is no "B" key in a real aircraft, and 18000 is only the "standard" level in North America. Here in the UK the TA varies from about 3000 to 6000. It actually varies considerably all over the world. And unlike in North America the rest of us have two different altitudes to consider -- TA and TL. The TA is generally published in the charts, but the lowest Flight Level you can fly, known as the TL, varies with the QNH and is computed by ATC to ensure adequate vertical separation betwen those on QNH and those on STD (i.e. flight levels). The "B" key "cheat" in FS doesn't obtain the QNH for you, it actually sets it on the altimeter. What you are doing is wrong (and of course not possible in the real world). When descending below flight levels you should set the altimeter to the QNH value you get from ATC or an ATIS weather report. That wouldn't change so often. You shouldn't have to be worried about what the ACTUAL sea level pressure is immediately below you -- other aircraft will be using the ATC/ATIS QNH values as well. Also, the fact that the actual QNH is changing slowly means that FSX is actually smoothing the pressure -- otherwise it would keep jumping. If it kept jumping you would see your altimeter jumping too. Do you? That means, really, that there must have been a sudden jump somewhere -- from another area's QNH to the one at that airport. That isn't smoothing, it is the opposite of smoothing! I'm 65 this year and really would like to fly more in my nice 737 cockpit on which I've spent quite a bit over the years. FSX's SimConnect was supposed to take over from me, and let me have more time .... now it looks like FSXI before I get time off! :-( Regards Pete

Hmm. I thought that was aimed specifically to help folks with CH gear? I didn't have anything to do with it of course. The "manual" to follow when using FSUIPC to calibrate things is the one supplied with FSUIPC -- the "User Manual". It provides a very simple step-by-step guide for ALL types of joystick, yoke or rudder system. I've no way of explaining anything in any more basic way, as that is it.But it sounds like you've not actually referred to it? :-( Pete

You need to properly calibrate the rudder pedals with an adequate null zone. If you have it working fine in FS, what are you trying to use FSUIPC for? I don't have any of those. But didn't you see the earlier, "sticky" thread in this Forum entitled "FSUIPC guide for CH Users"? I really don't think I can help more than that! ;-) Regards Pete

You've evidently not reviewed the two other recent threads here on this subject? It has been a real pain hacking through FSX's code to try and get some sort of control over the winds, but by all reports it is a helluva lot better with version 4.219, available in the FSX Downloads. Do please also read the other relevant threads. None of the intimate weather control we had with FS2004 and before is easy in FSX. The facilities in FS2004 and before cost me many thousands of hours hacking into FS code. With the coming of SimConnect in FSX I thought I was over all that (I am getting too old), but it wasn't to be. I've tackled the wind smoothing now. I cannot make the visibility smoothing work no matter what I try. And no one has, so far, mentioned any need at all for pressure smoothing in FSX. Are you saying that this jumps up and down badly as well? The user guide for the FSX version of FSUIPC does explain a lot of this, if you'd care to look. It does show a complete lack of pressure smoothing, you'll notice. ;-) Regards Pete

Well, I'll do some more testing and try to find it next week. Meanwhile I'm releasing 4.219, which fixes a problem stopping 4.218 being used without FSX SP2 or Acceleration, and also, hopefully, improves the simulation of turbulence in my wind smoothing stuff. I've tried to make turbulence introduce fast but small variations in all three directions. I've got to get my cockpit up to date next week then do some proper "flight testing". Everything I've done so far has been on my development PC, so no real flying of any consequence. Regards Pete

No, obviously it is getting the wrong address. I have seen such a thing before, someplace, but I can't remember what the cause was. Something to do with Network card drivers I think. You are providing the Server name, I see. (A rather complicated one too, "127019600301"). All WideClient does with that is ask Windows to convert it to an IP address. That's the one you are then seeing it try. Windows should of course provide the correct IP address. Are you using WinXP or later on both PCs? If so you could simply allow WideFS to connect automatically. Do this by removing both the ServerName and Protocol parameters from the WideClient.INI file. The default installation as supplied from the WideFS downloads should work this way in any case. If you aren't using WinXP or later on both, then just try specifying the correct IP address yourself, as "ServerIPAddr=n.n.n.n", and remove the ServerName. For this, though, you will really need to set fixed IP addresses for each PC, not allow the router to set them, as they may not be the same each time if you do. Fixed addresses tend to be more efficient in any case (I've always used them), as it saves extra traffic, asking the name server (your router) for a translation each time something wants to start a fresh transaction. Regards Pete

I've checked my FS9 code, and there is still a test facility built in which would enable us to ascertain whether it was related to some Weather files or not. Edit the FSUIPC.INI file again, adding Debug=Please LogExtras=8 to the [General] section. Then see if FS9 gets any further. If not then I have no idea, because with that in place and you not being registered, FSUIPC is doing nothing at all until some application links to it. Regards Pete

You've not "pissed me off". You are just not reading and following my suggestions, so it eventually becomes not worth replying to you. Well, not until now you haven't. You didn't look among the Announcements then. All the Announcements at at the top of the Forum. All you have to do is scroll up from where your message is!! Assuming you added the LogReads and LogWrites lines correctly, it shows nothing attempting to access FSUIPC, so we must conclude it is something in FS itself. From your later message: Okay, so it cannot be a rogue joystick driver. The only thing FSUIPC is doing at that stage (especially as you are not Registered so it isn't operating any user options) is reading the Weather data. So possibly you have corrupt weather data in FS9. That can happen sometimes when real weather downloads go wrong, but usually it is fixed by deleting all the existing WX files. You did delete ALL the files in your "My Document\Flight Simulator Files folder, didn't you? If so then it must be elsewhere. Quite honestly, I'm stumped. This is unique. I suspect there must be something you must have left un-deleted last time you uninstalled and re-installed FS9. Are you CERTAIN that you deleted the whole of the folder (and all its subfolders): C:\Documents and Settings\\Application Data\FS9 because I think the answer must lie there. And when you uninstalled FS9 last, you did delete any remaining folders that its uninstall left behind, didn't you? The uninstaller doesn't delete all add-ons and changes, only the original install. In particular, there would be additional files in the FS Modules folder which it would not have deleted. Maybe there's a rogue module in there. You have to do a fair bit of tidying up, deleting loads of bits left behind. Pete

Ah, sorry. Sounds like you don't have FSX SP2 or Acceleration installed. As just reported in another thread here, it was discovered earlier today that I made a silly build error with 4.218 and it only works with those. I will post a revised build over the weekend, Monday at the latest. 4.219. If you believe you do have FSX SP2 or Acceleration installed, please show me the FSUIPC4 log file (from the FSX Modules folder). BTW there is really no need to keep posting those pictures, lovely though they are. I do tend to believe folks -- even if I didn't I'd prefer other types of proof (logs etc) not disk-filling and screen pictures! ;-) Regards Pete

Well I can probably set that up without a flight from you. I'd need to fly my 737-700 as my ASX is rigged up only for my cockpit which is a 737 not a 747 -- too many changes. I won't have time till next week, but I'll try to remember: KSFO headed, what, towards KSEA, with the weather from, say 1700Z on 23rd Jan '08? Do you use the AutoSave option at all? If you do and can set it for a save every, say, 2 or 3 minutes, then if you do get the same thing again -- i.e. a sudden directional shift NOT explained by the wind variance value -- please make a note of the PC's system time and go save me a copy of the FLT + WX AutoSave files from the nearest time beforehand. This would be the most efficient way for me to find out what is happening. Regards Pete

Windows is blocking the access. That's what "connection refused" means. WideClient is simply relaying the error it is being told by Windows. Well, I'm pretty sure the answer lies in that direction (firewalls, that is). Well, it won't do -- replacing a program with an identical copy of the same program changes nothing. Sorry, you need to find what is preventing access. It could be something stopping Wideclient seeing out or the Server receiving the connection, so double check firewalls both ends. Not anti-virus programs, they aren't relevant. Regards Pete

Ah! Sorry! I've just found that I built it with the wrong list of Simconnect manifests, so it only looks for SP2 and two recent Betas. I'll fix that and upload a fixed version over the weekend, or Monday at the latest. I'm in the midst of some other changes. Look for 4.219 before Monday. Regards Pete

Well, something is wrong with the file. Maybe it got corrupted or something? There are at least two files saved - a FLT file and a WX file. The latter contains the weather and it is in binary, so impossible for you to check. I'd delete it if I were you and try again. The FLT file is easy enough to check as it is a text file. what "AutoSave.DLL"? AutoSave is not involved in loading any files at all, and it doesn't even save them -- all it does is call the FS save facility, the same as you pressing the ";" key and entering a name. It just enters the name for you, nothing more. My advice is just delete the bad FLT + WX files and move on. Maybe you had some sort of hardware glitch when they were saved. Pete

Yes. I am sorry, I am also at a loss with Vista. I do have a copy installed on a LapTop (much against my best inclination), but I've tried to change permissions on the WinSxS folders and cannot. it seems you need "TrustedInstaller" status to do anything with it at all. It's enough to drive you crazy. Okay. thanks. Good luck. Pete

No. All versions of FSUIPC4 since 4.10 should run fine on any state of FSX update. Only 4.0xx versions had any problems after SP1. What was your previous version? Does FSrealTime connect okay? Please show me the Install log and the FSUIPC4 log from the Modules folder. Close FSX first and show me the whole file in each case, please. You can also enable IPC read and write logging (on the Logging page), then try FSRealTime again and see what the log contains. Regards Pete

Ouch! That version number is for SP1, not SP2, even though SP2 is shown to be there by the Installer. I think the SP2 installation is screwed up, and it is this which is causing the hang. You say and I think this explains it -- there have mean many problems arising for uninstalling and reinstalling things. It seems this "side by side" library system devised by MS is, er, rather fragile. Acceleration includes both SP1 (which won't install again if it is already there) and SP2. When you uninstalled it I guess you didn't remove the SimConnect folders, so in fact those didn't get repaired. . I think the next step is to try to "repair" SimConnect. Here is gets a little, er, complicated I think, especially on Vista. You need to see if you can delete the three WinSxS folders for SimConnect we identified earlier. You will probably need to run Explorer using "run as" Administrator, and you may have to change the folder permissions even then. If you can't do it I'm afraid I'm not much help. I don't yet use Vista (I don't like it one little bit). If you succeed, then you can try uninstalling SP2, then SP1, then run the FSX repair (i.e. run the original install again, from the DVD). That should get the base SimConnect working -- you could test it at this stage. Re-run the FSUIPC4 installer and make sure FSX loads. Then re-install SP1 and test again (there should be no need to reinstall FSUIPC4). Finally reinstall SP2 and test again. I don't want to alarm you, but some folks have eventually re-formatted their disks and reinstalled Windows to recover from FSX installation problems. I'm sure there must be better solutions, but I think you would need to contact your Microsoft support centre to get their advice. There are some additional assists provided by Microsoft on the http://www.fsinsider.com web site. You might like to read some of those too, before you start. Regards Pete

Okay. Maybe I remember it wrong -- it's a long time since I flew one. Make sure that this is so with the FS simulation -- turn the effect off under "realism" and see if it changes. Also make sure you do tests with zero wind -- the Cessna is light enough to try to veer into even light winds. Pete

Okay. and does the "pulling" occur to one side only (which way, the left?) only with prop planes, and is it more pronounced with higher engine revs? If so are you sure it isn't simply the normal effect of the propeller torque and the tailfin backwash? In a real prop you have to apply some rudder to stay on the centreline, and more as you increase throttle. Alternatively, possibly you have the rudder trim set off-centre? With a zero input to the rudder the rudder will be central, neutral. Go outside the aircraft and look at it to check. Pete

Thery are zero all the time, no matter what the input is showing? Have you actually calibrated them at all? That sounds exactly like either the calibration has not been done in FSUIPC, or you've done it badly. That sounds like the brake pedals are not only operating the analogue brakes, but also sending a normal "brake button" control (like the '.' on the keyboard) as that is exactly what that does. Are you sure you aren't using some CH driver too, sending such messages? Show me the [JoystickCalibrations] and [Axes] sections of your FSUIPC INI file (from the FS Modules folder). You can cut and paste those into a message here. I also need to know the VERSION numbers of both FSUIPC and FS. If you are not using the latest FSUIPC, please do so first. Pete

Okay. I just installed the PMDG 747 for FSX. It actually installs 3 (THREE) DLLs, and adds them to the DLL.XML file automatically, when installing. These are PMDG\DLLs\PMDGOptions.dll PMDG\DLLs\PMDGEvents.dll PMDG\DLLs\PMDGSounds.dll where the PMDG path is inside the main FSX folder. So, it looks like, with your configuration as you've shown me here, the PMDG aircraft won't work either. Possibly all this is down to whatever it was which messed your DLL.XML file up? After showing me the SimConnect log I think it would be a good idea to delete the DLL.XML file, re-run the FSUIPC installer, and also re-install the PMDG aircraft. Regards Pete