Pete Dowson

ErI didn't think the BRAKES message came on with auto-brakes, only manual braking. Are you using the latest interim version of FSUIPC? Please try that if not. All those calibrations seem far too "precise" or "reguar" to be true calibrations. Are you sure you are leaving a small dead zone at either extreme? Even the centre zones for the main controls seem impossibly contrived for manual calibration! Without any "parking" place for the brakes when off it is likely that they are appearing to be on a little, on occasion. Pete

Well, of course. You could put the microphone and the recognition software on the MCP client and use PM's keystrokes instead, provided the MCP has the keybopard focus. Otherwise, only by asking Enrico to add voice recognition to his programs. ;-) Which aircraft are you simulating trhat has voice activated controls, by the way? Or are you just simulating a CoPilot? Regards Pete

You could write a program interfacing to FSUIPC to do such things, yes, though changing the autopilot values won't do anything unless the autopilot is engaged. You can move the airlerons and rudders and elevators direrctly too, or their trims. Get the FSUIPC SDK. http://www.schiratti.com/dowson. Regards, Pete

They sound like reasonable INput values, yes. You calibrate in FSUIPC to change the OUTput. If you calibrate max correctly you will always get 16383 for max OUT. Min would give you -4096 or similar, whilst the whole idle zone (which can be as large as you like) will certainly give 0. You simply need to calibrate in FSUIPC by following the numbered steps in the documentation. It couldn't be easier. You are currently mistaking INput values for CALIBRATED values, which they are most certainly not. If the OUT value is identical to the IN value, then you haven't even enabled the calibration! Pete

No idea what NetBIOS is nor how to program it. There is no Netwrok code whatsoever in GPSout -- if there's any relationship it will be something you have installed whoch is hooking COM2. Check by using COM1 or any other port. On Win2K or XP, WideServer by default sends a mailshot every 1 second so that its Clients can identify it. I have no idea what Ports Windows uses for its mailshot service. No, nothing of mine tries to do any such thing. Sorry. Pete

Not seen any of those. How many lines/characters per line? I'm not really developing Advdisplay any more, having moved the main point of it into the latest FSUIPC versions. However, I can take a look for the latter. Any links to details? Keyboard names/ids etc? Pete

Yes, each correctly configured WideClient can and will receive the same GPSout transmissions. Pete

Since there is no difference between them either electronically or programmatically -- they are only mechanical levers, with no identifcation readable in the firmware/software -- that was really an unnecessary expense unless you like tyo be totally realistic and also have positive "latches" for the "centred" idle points. Whilst I had one of eachtype of quadrant for development, all the testing could have easily been done with just one 6-lever quadrant. An ordinary lever has two points of intereset -- maximum and minimum. So for such levers that's all that needs calibrating. On levers which have three specific points of interest (eg max, idle, reverse or max, idle, feather, etc) then obviously calibration of the "centre" zone is needed. For the levers with latched/gated centres you need to calibrate that latch point with a defined area (just above, just below the gate), to allow for small variations in the pot reading. Just follow the directions and it will work. Pete

Hmmm. that's rather vague and unhelpful I'm afraid. Sorry. What are "incorrect" values to FS? Reverse should give reverse to FS, zero will give idle, and full throttle will give full throttle. Maybe you haven't actually calibrated them yet? Perhaps what you are really trying to say is that you have calibrated the centre in the centre and you don't want it there? Unlike ailerons, elevators and rudders, usually you don't want the throttle idle to be in the centre, as you need much less of the axis movement for reverse (at most a fifth -- FS aircraft have up to 25% thrust available in reverse) than for forward thrust regulation. Simply recalibrate, following the simple step-by-step instructions in the FSUIPC documentation, with the idle (centre) set where it should be, and where you want it, not in the centre of the axis movement range. This is the whole point of FSUIPC's more accurate and settable calibration system, something you perhaps may have missed? You can put the "centre" wherever you like! Please just take a look at the steps to set each position. I think you should find it easy enough. Otherwise, really, if you are going to let the centre lie where it wants you may as well not use FSUIPC! ;-) Regards, Pete

Sorry, it is trial and error. If it does it with defauilt aircraft loaded (and loaded as default -- i.e. change the default, close down, then reload) then it must be an add-in DLL. Remove each one in turn and re-test each time. If it doesn't happen with a default aircraft then it is something to do with one of the others you fly. No. Registering FSUIPC changes nothing for accredited programs -- all registration does is give you access to all of the FSUIPC user options. There's only one version, not a registered and an unregistered version. And FSUIPC isn't causing the problem in the first place. FS9.EXE isn't terminating correctly because something you've added won't let it. Regards, Pete

Can I see the logs for those? Maybe they have several threads going, and the thread which does the registration doesn't always stay ahead of the ones reading the data. If so they need some sort of interlock or flag. It's probably readable by logging on the PCs which work. The key is C8HX 18NZ I54G but I think you should report this problem to them in any case. Regards, Pete

That's nothnig whatsoever to do with WideFS. The Microsoft weather server has been down all day! None of my programs have anything whatsoever to do with any intrinsic FS functions. Please don't look at them first to blame all the time. Pete

Thaty won't be anything to do with either FSUIPC or WideFS, as you will be able to prove for yourself quite easily -- just remove the DLLs. Possibly you have a badly instaled aircraft or some othe FS corruption? BTW what do you mean by "successful install"? All that there is to the installation of FSUIPC is putting the FSUIPC.DLL into the FS Modules folder. Regards, Pete

If you haven't filed a flight plan then I don't know of any other way of identifying the current airfield for the user aircraft. Even if you have filed one it would only be correct before you left. Normally users know where they are so it hasn't been a problem for all these years. Utility programs which give you data on position and so on do use a database, almost invariably. Regards, Pete

The answer is simple. Although the access code for this program has been issued, it isn't being supplied to FSUIPC. It either needs to be written to offset 8001 (which is the normal way for automatic access), or placed in one or two of the version info resources, as described in the FSUIPC SDK documentation for developers. Since it isn't being supplied in any of these ways the only ways to make it run correctly are: 1) Tell the user to purchase an FSUIPC registration, or 2) Tell the user to manually register the program himself. You'll need to provide the key and instructions. Regards, Pete

Please turn on IPC read/write logging so I can see its registration sequence. Regards, Pete P.S. It will have to be today (Friday) or tomorrow (Saturday) as I am away for two weeks from this Sunday, 11th June. Else you could also try manual registration (via the FSUIPC "register an application" dialogue -- exe name without the .exe plus the assigned key).

There's Luciano Napolitano's "Key2Mouse" program. I don't know of any other way. If you are talking about default aircraft, or aircraft developed from the defaults, then in nearly every case there will be a control listed in FSUIPC's buttons/keys dropdowns. For some sophisticated add-ons there's no way FSUIPC knows anything about extras they may have implemented over and above what FS supports. Regards, Pete

I'm told it works if you have the very latest SB3 -- the FSUIPC facility went in as soon as Joel agreed to support the new commands, but it didn't get into SB3 until later. Sorry, I don't know release numbers. If you think you have the latest and it still doesn't work, please contact SB3 support, because the mechanism in FSUIPC (latest version) certainly does what they agreed. Regards, Pete

"PMStartUp" not "... starup". And it is in the "intermediate files" folder, click the link top left someplace on the Updates page. Regards Pete

Which "latest version" is that, I wonder? There's 3.60 which is the current user release, and there's a later one available up in the "interim versions" announcement above. I'm not the best person to ask, my systems are all a complete mess. My good friend Eric from PFC was over here these last few days and he kindly installed and configured PM's "PMstartup" program for me. Maybe you should investigate that? It obeys a script to copy files before starting each PM component. It's in the Intermediate Builds part of the PM updates site. Regards, Pete

Okayreally I'm now thinking about how I will go about at solving such things in the FSX timeframe. I found about as much about FS2004's innards as I'm going to be able to now (I have been at it on FS2004 for three years). I know some folks know a lot more than me in some areas, particularly scenery, graphics and aircraft modelling/characteristics. Regards, Pete

This is only part of the log -- I don't see the FSUIPC version number nor the registration data at the top. Have you registered it? Pete

Most of the advanced aircraft add-ons do their own thing with the Autopilot. I suspect the only way you have into those values is using whatever keyboard shortcuts they've provided for incrementing and decrementing them. FSUIPC interfaces to FS itself for these things. some add-on aircraft makers do use some of the FSUIPC offsets for their own programming, but they don't always publish these. I know there's an SDK for the Level D aircraft (and an interfacing program, fsconv), and I know some folks have found some values for the earlier PMDG aircraft, but I don't know of anything for PSS at present. See if there are others who have solved these things in whatever Forum PSS users inhabit. Regards Pete

Yes, I use the Visual Studio C/C++ debugger. It works best with the "no CD" crack for FS9 -- the only justification I can offer for using that piece of work. Otherwise you may be able to attach to the FS9 process AFTER it is started and fully running, but that can sometimes prove difficult too. For much development I have to write my own "foraging" DLLs which run inside FS and show me what is going on. Regards Pete

No. there's no way Advdisplay with change any of your panels, it has nothing to do with them. But what, in any case, do you mean be "deactivation"? If you don't want to use Advdisplay, please simply remove the DLL itself from the FS Modules folder. Regards, Pete