Pete Dowson

Yes. That makes sense because I think WidevieW struggles to get the weather identical in each copy of FS9 -- the problem arises because FS9 weather is dynamic, and localised, even when set globally. I think WidevieW should be able to do a better job on FSX where the global weather can be enforced -- but then there are other problems on FSX, like less control over cloud types and thickness. Is FSInn feeding every PC, like having several copies of ActiveSky? No idea. I don't know what FSInn is doing. Sorry. This is really not related to any program of mine, except insofar as the weather data being passed to FS9 via FSUIPC. Does FSInn do something of its own, not using FSUIPC? Regards Pete

No, nothing. You shouldn't get a crash no matter what. When you do the re-run to get the Logging files, at a point before you get the crash, could you please Save a Flight (press ; and give it a name). Include the resulting FLT + WX files with the logs, and tell me how to proceed from that point to get to the crash. If I can reproduce the problem it will be much easier for me to work out what is happening -- I think I still have an FS2002 around here somewhere. ;-) Regards Pete

It should also have found the SP1 SimConnect build, but didn't. As shown in the FSUIPC log file, I did build in code to try to recover from this -- if the first version of SimConnect I try returns an error, I try backtracking to an earlier version. However, it seems that when SimConnect is mis-installed it cannot do this. I advise you to uninstall SP2 (or Acceleration if that is what you tried, and then install SP1 first, then SP2. If you are using Acceleration you should be able to get away with only re-installing Acceleration, as it is supposed to include SP1 too. Regards Pete

Actually, please amend that -- enable Weather logging too, please. I've just checked, and that offset is in the weather reading part of FSUIPC. I'm wondering now if it might be a corrupted weather file. Are you always starting with the same weather? Where is the weather coming from? Does it happen if you clear all weather first? Regards Pete

Well, I don't get urges like that, but it is easy enough to do so it'll be in the next update. I can't say when that'll be though. Watch the FSX Downloads announcement. Regards Pete

Sorry, I cannot support 3.75 therefore it should not be supplied. I've contacted HiFiSim and apparently they seem to have made an error, and check explicitly for 3.75 or else refuse to connect! I think they should be issuing a correction quite quickly. Regards Pete

Doesn't the documentation which refers to offset 5628 tell you how big it is -- 1, 2, 4 or 8 bytes? A byte has 8 bits -- multiply the size in bytes by 8 to get the number of bits. Or it might tell you how many bits there are instead. It isn't rocket science. Why not assign them via the dialolgue in FS instead of fiddling about editing the INI files? When using the NAMES of the controls surely their use is obvious? 'Set' sets a value, 'Set Bits' sets bits, 'Clear bits' clears bits, 'Toggle bits' toggles bits. They are in English. I tried to make all this stuff easier by naming controls and providing full facilities for assigninging them in the dialogue, so why make it harder? Pete

There's no offset for these at present, but the data is available through SimConnect and I could add them if required (for FSX only). They are just some of many items not yet requested. Pete

Ah, that's very interesting. I need more information. could you enable IPC read and write logging (in the FSUIPC options, logging Tab), and repro the error for me please? Zip up the FSUIPC.LOG and send it to petedowson@btconnect.com. Regards Pete

The elevator axis is jittering a bit, not repeating -- the value changes initially between 1167, -8 and -3 are odd (maybe you touched it), but the rest there are just minor jitters, quite common for ansalogue axes and nothing to worry about. The PANEL LIGHTS OFF controls are probably coming from an aircraft cockpit gauge just making sure that the lights are as set on the switch. It shouldn't really do it, but that sort of behaviour isn't uncommon and does no harm. There's nothing there affecting the flaps, so I can only conclude that ytour flaps problems are something to do with the aircraft model you are using. Nothing external to FS is sending any Flaps controls whatsoever, else they'd be seen by FSUIPC and logged. Well, I'm sorry, but it certainly isn't FSUIPC which is doing it. If it only does it when FSUIPC is there there must be some weird corruption someplace else in FS which only manifests itself when the timing or memory arrangmenets are just so. Originally you said "Suddenly, out of the blue, the flaps command of my GF modules (LDG and TQ6) do not work normally anymore ..." Things don't happen "suddenly out of the blue" without something changing, so maybe your best bet would be to try to identify exactly what may have changed. Regards Pete

Ah, right. I didn't see that message when I first logged on. Regards Pete

It isn't the VALUE, it is whether FSUIPC has anything to do with it or not -- the button top left, above the IN and OUT values, should read "Set" not "Reset". The INI file extract you showed most certainly showed the flaps axis as being handled! None of that is at all relevant. The numbers are HOW you calibrated the axis, not whether is is being "calibrated"! Calibration is turned on and off by the button that turns it on and off. The "first part" of the INI file generally is all about other things entirely, nothing to do with calibrations. If the axis is not being handled in FSUIPC, then it isn't being handled in FSUIPC. Full stop. Maybe you have a button set to operate flaps up/down and it is spuriously repeating. Enable FSUIPC's Axis events AND Buttons and other Event logging, and check what is actually being sent to FS. Pete

That sounds more like a scenery or terrain problem. What FS module is mentioned in the crash report? Generally those are G2D or G3D.DLL. Pete

I don't think messing with that area will help and is likely to cause more harm than good. You surely didn't purchase them before making sure that FSUIPC was working on your system? I don't know. Does the signature check out on the DLL (right-click and check it via Properties)? Pete

Sounds like a SimConnect problem. First, though, show me the Install and FSUIPC4 log files which you will find in the FSX Modules folder. There logs are produced to help resolve problems. Pete

Feature? Do you mean the Autobrake Set control? Not necessarily, but since the only valid parameter values are 0-5 it is difficult (but not impossible) to use with an axis. Erwhere are you reading that the parameter is 1007? That's the internal number of the Autobrake Set control. If you look it up it clearly says the parameter has to be 0 for RTO through to 5 for Max. Of course not. 1007 is the control called "Autobrake Set", exactly as documented. If you assign that control the parameter has to be ONE of 0-5, whichever setting you want it to do! If you just want to increment or decrement it just use the normal FS controls, DECREASE AUTOBRAKE CONTROL (number 66299) or INCREASE AUTOBRAKE CONTROL (number 66298). If you want to use an axis you will have to divide the axis into 6 zones and assign the AUTOBRAKE SET control plus relevant parameter in each zone. This uses the right-hand side of the Axis assignment facility in FSUIPC. Pete

Not crazy, it is a symptom of a bad connection (and it is even described in the documentation!). Show the log files (both Clinet and Server) for more help. I can't guess. Pete

Nonsense, FSUIPC is not corrupted. If the DLL gets corrupted it will not work, period. It is self-checking. All of your settings are in the FSUIPC.INI file. This line: proves without a doubt that you have told FSUIPC to handle your flaps! Just go to the FSUIPC Joystick Calibrations tab and press the "Reset" button on the flaps entry. Then it won't touch them. If you ask FSUIPC to do things, it will do things. If you don't, it won't. It is that simple! Pete

What about if you remove vasFMC instead of FSUIPC? Because FSUIPC does nothing unless asked -- it sounds more like something in vasFMC. You may need to ask FSInn support about this, because only they would know what could be affecting their transponder mode indication (there's no simulation of those modes in FS itself, and therefore no facilities in FSUIPC for them). Alternatively, possibly you have some conflict between button or key assignments between vasFMC and FSInn -- specifically the one operating the IDENT. Pete

FSUIPC has nothing whatsoever to do with your joystick settings in FSX. It cannot interfere with the FSX setting (I don't even know how to do that) nor does it touch the FSX.CFG file. You have something else going on entirely. Regards Pete

Not a doc, but the Joystick section in the options -- in FSX, find the FSUIPC4 options menu, select the Joystick calibrations tab (section), and page through to page 7 or 8. Pete

You just caught me before leaving on holiday till the 24th. Yes. Search the Advanced User document for the parameter "ShortAircraftNameOk" where it explains how. You'll need to edit the INI file. Program one of the aircraft only, first, then set "ShortAircraftNameOk=Yes" and shorten the hame of the aircraft in those sections. Or even, for all 737's, set "ShortAircraftNameOk=Substring" and set the names to something really short like "737". Regards Pete

Ah, sorry. My mistake. Yes. You have an FSUIPC3 key. You need an FSUIPC4 key. Please check the User Guide documentation where it tells you all about it and provides a link direct to the correct place in SimMarket. Regards Pete

No, why on Earth would you think such a thing? Only for a completely new version like FSUIPC4! FSUIPC3 works on FS98, CFS1, FS2000, FS2002, CFS2 and FS2004, including the updates like FS9.1. But FSUIPC had to be completely rewritten for FSX. You only have to buy it once even though there are THREE updates for FSX even now, each one needing more work. FSUIPC3 was current and maintained with almost monthly updates for three years, all for one subscription. Now, are you complaining? Do you not pay for new versions of FS? Pete

Why would they need Administrator mode? I only have one Vista system here at present and don't need Administrator mode unless I want to change system folders (or Register FSUIPC/WideFS). It is because you installed them into "Program files", which Vista protects even against programs installed there? Regards Pete