Pete Dowson

Okay, it is obvious from the log you sent. This part: 167601 Client Application: "fs9" (Id=392) 167601 E:\FS2004\fs9.exe 167601 Product="Microsoft Flight Simulator 2004 - A Century of Flight" 167601 Company="Microsoft Corporation" 176404 Illegal read attempt: offset 0B74, size 4 176404Program or module not accredited for use with this unregistered FSUIPC indicates that your gauge is using the External program method of interfacing to FSUIPC. This is most inefficient and is not supported for Gauges and internal modules. You need to use the Module User's library and the FSUIPC_Open2() call. Please see inside the SDK, there is a separate ZIP with what you need. Regards, Pete

No, sorry. FSUIPC isn't actually handling joystick inputs, it is handling the control values after FS has dealt with all that. You need them working reasonably well before using FSUIPC. Regards, Pete

Are all the details for WideFS the same as for FSUIPC? The name and email address need to be identical, as it says in the documentation. Regards, Pete

Is any part of the FS A/P used in any of this process? Are they calibrated with a reliable dead zone in the idle position so they don't give any input at all (i.e. no jitter)? It is sounding more and more like I need comment from PSS about what is going on. A Mr. Blackburn has written to me (I asked him to join this thread) saying that "3.31 seems to kill the PSS Airbus flight Controls in that initial stick input shows them move for a fleeting moment and then return to neutral." which seems rather extreme. I'm still trying to get clarification from him as he seems a little mixed up over the FSUIPC version number. But what's this about, do you know? Regards, Pete

The PFC throttle control? No A/T enable toggle, nothing like that? No "SPD" or other button, all just by, what, moving the PFC throttle levers? I know for sure that PSS disables all joystick inputs by default when activating the AP and I assume that it's the gameport-inputs they are shutting down. PFC-driver works through the serialport however and maybe that is the reason why the checkbox doesn't respond as it should. But the PFC driver (a) disables its input when it sees the A/T engaging -- maybe PSS's A/T is invisible, not the FS one?, and (b) as long as you don't move the throttle levers and there is no jitter (best park them), there are no inputs to the FS throttles from the PFC driver. Regards, Pete

There's been no changes in the PFC driver for some time. I do have a new version in hand, but it isn't ready yet. Was it checked, and you unchecked it, or vice versa? How do you enable the A/P and A/T -- is this via regular controls on the PFC equipment, or other ways? What of the option on the main (front page) screen of PFC options -- does the "suppress interference" on or off change anything? Well, it may well be something related to the new facility in FSUIPC 3.30 to disable trim inputs when elevator inputs are disabled, but it is puzzling that it is the same with that option off. In the past, PSS have sent me demo versions when there's been any similar questions. Obviously if I had the aircraft here I could probably find the problem very quickly. If you don't get a quick response from them let me know and I'll chase them for something -- I am still snowed under catching up from my week off! Regards, Pete

PFC.DLL uses FSUIPC to interface to FS -- saves having to re-write PFC for each version of FS, I then only have to rewrite FSUIPC. I'm afraid I have no idea. I do not have the aircraft and no one in PSS has contacted me. Maybe it uses the elevator trim for its A/T? Did you see my earlier message in this thread? Regards, Pete

In that case, it does precisely what you want. If you have the taxi wind option set to automatic, then on take-off the wind transitions from the taxi wind speed of 1 knot, at the smoothing rate you specify, up to the correct wind speed. On landing the reverse happens on touchdown -- unless you have the option set to only smooth when airborne, of course. Maybe that's your problem? Or you have the smoothing rate set a bit high for your liking? Regards, Pete

The changes since 3.22 are all listed in the History document. I've had no other similar reports to yours, and really I've no idea what function in FSUIPC that the PSS airbus could be relying on which is now not performing as they wished. However, read this item (from the History): Have you got this enabled? Have you tried disabling it? If it isn't this, then I am really going to be completely dependent upon the PSS folks analysing what is happening -- they are the folks that know their code, and it is evidently something they are perhaps relying upon which, for some reason, is no longer true. However, having said that, I would have thought this would be experienced by a lot more folks than just one. Do PSS support say anything? Are their other similar problems reported on the PSS forum? Is there anything odd showing in the FSUIPC.LOG file? Regards, Pete

Sorry, no idea at all at present. What operating system are you using? Try adding "PollInterval=50" to the [buttons] section of FSUIPC before loading FS (add [buttons] first if there isn't one). Let me know please. Regards, Pete

Sorry, that is, in fact, mostly the case. I have no idea what is going on in ATC.DLL at all. Most of my knowledge of FS internals stems from knowing earlier code (FS98-Fs2000-FS2002) and finding equivalences. For most of the brand new stuff, all in horribly convoluted C++ and COM interfaces, I get rather lost. Sorry. Regards Pete

Sounds like his code doesn't bother to check whether FS is up and running before starting, and then never retries some of its initialisation sequences later on. Tell Damian that. Best way to deal with such programmes would be to use the "RunReady" parameters in WideClient.ini to start them up when FS and WideServer is good and ready. Regards, Pete

FSUIPC prior to version 3 will work on FS2002 and needs no registration. It works with the FS2002 VA tools such as Squawkbox. I'm sorry, but I am not an on-line flyer and cannot sort this out for you - you need to contact the on-line flyer's support fora. Regards, Pete

Okay. Let's assume it was something odd in the previous setup then. Regards, Pete

Good. That is the correct way. I don't have any records as I don't issue the keys. Regards, Pete

This seems to be in the wrong thread! You may want to post this in the cockpit building forum, or in some FSBus site. Certainly the hardware you are talking about is completely outside my experience. Sorry. Regards, Pete

I know for certain that the RealityXP stuff doesn't use FSUIPC. I don't know the other one, but I am very doubtful than any weather radar uses FSUIPC -- the information just isn't there, and I don't know how to get it. I know RealityXP cracked it. Sorry, what does that mean? I don't understand it. All FSUIPC is doing for weather is allowing external programs to read it and write it. There's no radar support at all. Take it out and see if either of your radars complains. I doubt they will. I think you may need to contact the support site for your gauges. Sorry. Regards, Pete

Check the PM website. In the Documentation section there's a document on FSUIPC Offsets used by PM. You can do anything that lists. If the RJ features you need are not dealt with in the FSUIPC interface, FSUIPC cannot handle them, you need to ask PM support. Regards, Pete

If you haven't resolved this yet, please send an FSUIPC.LOG showing the problem, to petedowson@btconnect.com. ZIP it please. Regards, Pete

More offsets for what? Can you be more explicit? FSUIPC currently offers almost everything available in FS. Those bits it doesn't aren't included because I can't find them ort don't understand them. Regards, Pete

I've really no idea whatsoever what is going on. Can you be a little more explicit about what the problem is? Then maybe I could hazard some guesses. When the FS A/P is enabled, the throttle inputs should have no effect. If the panels are configured to assume changes on the throttle inputs should disengage the A/T, then it sounds like you have some jitter on your throttle quadrant. Try calibrating with parking spaces at max and min throttle (and park them when using A/T), and also enable the digital filtering. Note that, with PFC.DLL, if there's no change detected on the throttle levers, no messages for throttle changes are sent to FS. Regards, Pete

Have you tried enabling wind smoothing? Regards, Pete

Sorry, I'm not sure I understand the question. Does the panel have its own systems, not using FS systems like autopilot and so on? If it does its own thing (like ,for instance, PMDG's 737NG) then it is unlikely, unless he has published some interface for you to program to. FSUIPC gives access to FS mechanisms and also Project Magenta. Regards, Pete

When you say "recently", is there something you have changed, or do you mean just after installing AS2004 and FSUIPC 3.317? Those are very worrying. I'd like to see what IPC calls are being made which causes these. Could you repeat the terst, please, but first enable IPC read and write logging in the FSUIPC Logging options page? The Log will be long, so ZIP it please and send it to me at petedowson@btconnect.com. I'll send you a newer version of FSUIPC to see if it still happens. If so, logs for both please. Regards, Pete