Pete Dowson

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

Ouch! That does indeed imply that Goflight are using FSUIPC for something. They haven't approached me about this, so there's no access key issued for their modules. Even if they were to get a key it wouldn't work because they are using an incorrect method to access FSUIPC in the first place -- one which will certainly cause problems with other modules or gauges in due course in any case. If you were to pay for and register FSUIPC then those modules may work, but if you ever have any other gauge or module using the same incorrect access method they could easily corrupt each other's data (as they would be forced to share the data interchange memory space), probably causing odd problems or even FS crashes. Please, when you've verified this, do report it to GoFlight support. Regards, Pete

Erwhy not just assign the button to the PTT controls in FSUIPC, which works fine with the current Squawkbox no matter whether it is on the same PC as FS or on another via WideClient. You don't have to do anything in any INI files. the keyboard method hasn't been used for ages and probably involves fiddling around with other parameters in any case. Just use the easy method provided for the purpse (and documented too, even!). please. Regards, Pete

The GoFlight modules don't use FSUIPC at all as far as I know. "offset 0238 size 3" is the FS local time (hours, minutes, seconds). In the FSUIPC log the "P1432" is a reference to a Process which will have been logged shortly before that line -- 1432 is the process "ID". See if that tells you. If it says it is "FS9.exe" then it is a gauge or DLL using FSUIPC incorrectly. Regards, Pete

That is NOT from the "latest" FSUIPC, but from one which is now many months old! Download the current release (which is 3.60) from http://www.schiratti.com/dowson, or get the very latest interim version from the Interim Versions announcement above. ALWAYS check the version number and report that, never just say "latest" as that is totally meaningless, as this proves! To find the version number simply right-click on the FSUIPC.DLL file itself and select "Properties" then "Version". The one you are trying dates from before the FS9.1 update Microsoft released for FS2004. Pete

Yes. did you check the documentation? If not why don't you simply download the ZIP and read the documentation, see what you think? Pete

A void pointer is one which can be cast into a pointer to anything. That's the whole point. Please check your C programming references. If the compiler doesn't do it automatically, try using an explicit case, but it does rather spoil the point of having void pointers in the first place. Regards, Pete

Well I just googled his name and came up with it in lots of places -- regarding airliner photographs. Try for instance http://www.airliners.net/message/index.main?id=1049029&photographer=Matthias%20Neusinger Regards, Pete

Not that I know about, sorry. It wasn't even me who found these values to map in the first place, but some other clever person. I wish I knew -- if I did I'd add it to FSUIPC, but I doubt if they'd want to release their secrets. Are you sure they are not simply editing the aircraft or flight file then loading it? Maybe the "reload aircraft" control would do it, but it seems unlikely. Regards, Pete