Pete Dowson

The stop is easy as there is a control for that, but I think the only way to start one is via the menu, isn't it? Regards, Pete

Good. No, that's okay. I just don't want it generally downloadable yet. Regards, Pete

Okay, in that case I think I've fixed it -- that option should only affect the throttles but through an error it affected the elevator trim axis too, which evidently the PSS airbus uses. I'm sending you an interim test version of FSUIPC to try. Please let me know if it is okay once you have re-enabled that PFC option. Regards, Pete

I only found out how to do the white on green method, as described in offset 3302. Are you using an out-of-date SDK by any chance? Pete

I don't know what data the ACARS is using. You can see what is available from FSUIPC in the Programmer's Guide, part of the FSUIPC SDK on http://www.schiratti.com/dowson. Programs like FS FlightKeeper do manage to keep quite a detailed log through this information, I suspect it is more than enough for your needs. Regards, Pete

I don't know ADVtext. If you mean AdVdisplay, one of my modules, then both foreground and background colours can be set -- in fact the background can be matched to one of your panel colours easily. It's all in the pop-up menu along with all the other options. Please look at the documentation supplied. Regards, Pete

This is a bit mixed up isn't it? You flew WITHOUT GPS and it crashed, but the last thing you did was add GPS? Can you clarify please? Er .. I'm still confused. What's the "GPS unit" in this context? There is absolutely no relationship between GPSout.dll and any weather facilities in FSUIPC. In fact GPSout doesn't even use FSUIPC in FS2004, it is completely independent. I'm really not at all clear what you are describing (too many "GPS"?) but if you would like to explain I will try to make some suggestions if I can think of any. GPSout cares not one iota about any "GPS unit" -- what is that? Do you mean hardware attached to the serial port, or something else? GPSout, when installed, always does the same thing, it simply sends data to the serial port all the time. It doesn't care if anything reads it. It is 100% output, no input involved, and it only stops when you close FS. If you mean you have your receiving apparatus, whatever it is, connected but not "active" in some way, try unplugging it. Maybe it is that device causing problems? Regards, Pete

Again, on this: I'll look at providing a "reverse" checkbox for each axis into the FSUIPC joysticks section. If it isn't too difficult, I'll slip it into the next version. Regards, Pete

Well, as described in the FSUIPC user guide -- you can provide precise null zones in centre and min/max areas. Also, you can compensate for an off-centre device, you can apply response curves to give variable sensitivity, and in the next version you can apply anti-jitter digital filtering. Regards, Pete

On landing it's only when actually on the ground. If you want it otherwise it's best to use the manual method and assign a hot key (FSUIPC Hot Keys page). Pete

Please read and join in on the thread entitled "FSUIPC & PSS Airbus". Regards, Pete

Please be more specific. WHAT doesn't "start" and how can you tell? There's no such file used by WideFS -- there's a WideClient.ini for each Client and a WideServer.ini for the Server. More importantly there's a Log for each and this will contain useful information. Regards, Pete

That's no good for me. Please send the WideFS notification and your current FSUIPC.KEY file to me, petedowson@btconnect.com, and I'll try to see what is wrong. Regards, Pete

No, that won't work because FSUIPC insists on the values being in order. I think some of the calculations also depend on that. Regards, Pete

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