Pete Dowson

No. Why should it be? FSUIPC is not doing anything at all most all of the time, and when it does do anything is is sync'd to frame rates. You don't get better frame rates when you increase the sim rate. How? What do you think is causing the instability? If you mean its autopilot can't control things so well at higher sim rates, then if it is a well designed well programmed autopilot I am not at all surprised. Autopilot coding will be based on feedback control, a process of reading values, determining the correction needed, then applying it. All this is probably calculated in real time, as it would be in a real aircraft. By speeding things up the feedback is probably insufficient -- the changes are happening twice as fast as so the corrections must be twice as "good". The only reason it probably doesn't affect the FS A/P so much is that it calculations aren't so sophisticated. I think all FSUIPC could do to stop this under-control would be to stop you changing the sim rate. Sorry. Maybe you could ask the PSS programmers to provide several autopilots, one for each increased sim rate you want to use? I can imagine their response though. I think their aim is to provide more realism, and this is really your problem. I would think that real aircraft would be unstable if real time went twice as fast too. Regards Pete

Sorry, can you be a little more explicit, please. Are you talking about FSUIPC? If so, which version, and which page of the joystick options? If FSUIPC is not processing an axis then it is not calibrating it either. But there are several options which divert the processing to other sections. without knowing what you are talking about I'm afraid I cannot explain it to you. Regards, Pete

Don't worry about it. I'd rather be doing something, else I feel even worse. It's just that I better not do anything too complex or serious in case I make a mess of it! :) Regards, Pete

I hope so tooI'm not doing any serious work at present as I tend to be coughing and sneezing all over the place and it does nothing for my concentration. I'm fiddling about with small easy things. Don't like just lazing about, only makes me feel worse! Anyway, sorry about the fuel selector. I had a quick look at the code and saw that somehow, presumably when editing something else, a spurious "!" character has crept into a conditional -- unfortunately in a place which didn't make a compilation error! Duh! I can only put this down to sloppy keyboard usage whilst I've been sneezing or coughing! Anyway please check your email and let me know if it's okay now. Thanks, Pete

Regards, Frank No, sorry, it is on my list to look at, but the Cirrus is upstairs in a cold room and I am sick with 'flu' at present. I noted to check it as soon as I can. The other stuff about radios must be your kit. Regards, Pete

If WideFS is registered in both (copy FSUIPC.KEY file from FS9's Modules folder to the FS2002 Modules folder), and has the same INI file, and you are using the same version of FSUIPC in both, then there is no difference. I assume the Clients are the same for both? Apart from saying that, if you want me to advise further I would really need more details. The WideServer.LOG file from the Modules folder is the place to start. Regards, Pete

Yes, they were requested a while ago. I had a big effort on PFC last week and implemented all the things left on my "wish list" for PFC. Enjoy! Regards, Pete

You can probably get that sort of effect by writing to the accelerations -- like the catapult effect, though obviously not so severe. Just read the longitudinal acceleration (which should be negative under braking) and keep increasing it (towards zero). FS will keep trying to change it back, but i think it will have an effect. Regards, Pete

Hmm. I don't recall whether it was working originally or not. I've a feeling that pretty much none of the engine-related variables worked with CFS1. I hope someone else can help. Sorry, I don't even have the program any more, and it was really only accidental that FSUIPC worked (partially) with it in any case. It was never a target program. Regards, Pete

Can you detect when the button is pushed? If so, when it is pushed, set the value to standard, which is 1013.2 hPA. The value to be written to IPC offset 0330 is 16 times this (i.e. 16211), as documented in the Programmers Guide. If you want to alternate that with the QNH, you have to read the vlaue first and keep a copy, then swap them back next time. It is just a matter of programming the logic. Regards, Pete

Sorry, this seems a bit confused. are you trying to control the brakes from a program, or do you want to use the CH pedals? Writing 0 won't put any brakes on, 0 would mean brakes released. What are you expecting to happen when you write 0? These locations work fine for brake application, as documented. They are used for the Aerosoft GA28R cockpit's pedals, and for PFC pedals and proportional brake options. If you tell me why you are writing 0 and what you then expect to happen, mabe I can help. Otherwise, please re-check the Programmer's Guide which explains the difference between setting brake pressure (0BC4, 0BC6), and operating brakes (C00, C01). Beware that if you want to take control from an externally assigned brake you will have to disconnect that brake axis, or at least ensure that it is parked in a position of "no jitter" so that it doesn't change the brake settings. Good calibration with a null zone should do it. Regards, Pete

Yes, I'm sure. Regards, Pete

Yes, there are quite a lot of users with French FS and French Windows for that matter. There were some earlier technical problems with some of the facilities (e.g. saving a flight through the IPC interface), due to the different folder names for Flights and the FS9.CFG file, but these were resolved a few versions back. Regards, Pete

If you just what to Increment/Decrement it, just use the standard FS controls, like you would to assign them to buttons or keypresses -- KOHSLMAN_INC and KOHLSMAN_DEC (MS have allways mis-spelled Mr. Kollsman's name :) ). If you want to write to FSUIPC rather than use it like a pair of buttons you can send the controls via 3110. see the Programmers Guide. Otherwise, probably more efficiently for a rotary, you can read the value in 0330, increment or decrement it locally, and write it back to the same offset. If you only re-read it when you've not changed it for a second or so then it should be a lot faster and you can keep up with the rotary. For airliner use the rotary should also have a push-button action which sets standard altimeter pressure (1013.2 hPa or 29.92") for flying flight levels. Ideally you should keep a copy of the previous QNH value and swap between the two on alternative presses. This enables the QNH to be pre-set whilst still flying on Standard. Internally you will notice that FS operates in mb or hPa (x 16). Whether it displays hPa or inches of mercury is a gauge display function. Regards, Pete

I hope someone else here can help. All the stuff I can provide is in the EPICINFO ZIP, and also the EPIC95.ZIP ( though that's many years out of date now). I don't know what type of EPIC card you have, but if it is a USB EPIC then the EPL I used to use years ago is no longer valid. It has changed a lot and I no longer use it I'm afraid. Eventually experimentation is the way you will have to proceed. I remember when I first started with the ISA EPIC, many years ago (FS5 time I think, certainly with DOS originally) it was a very steep learning curve, and I had to get lots of help from Ralph Robinson. I'm not sure what sort of support is available now, but you might like to look at http://avsim.com/bluesideup, a website soecialising in EPIC matters. There may be lots of examples there too, and other users to chat to I expect. Regards, Pete

There have been similar such assorted bugs with different drivers in all versions of FS and DX as long as I can remember. The trouble is they are all hardware configuration dependent. The first thing to try, as even advised by MS support, is later or even just different video drivers. Regards, Pete

Read the documentation please. The part entitled "Installation", where is says EXACTLY what to do. Read the documentation please. The part entitled "Entering Registration Details", which tells you EXACTLY what to do. The email you received with the Key also gave instructions. I'm not going to repeat all the instructions here, sorry. You have them. Please refer to them. Regards, Pete

Yes, many cards have that facility these days. Alternatively, if you can find a PCI card, you can, with a little more difficulty, run an AGP card for one and a PCI card for the other. Regards, Pete

I think it is more to do with the gauge which insists on only working in FS2002 even though there is no reason for such a stupid restriction. For FS2004, which I assume you are using, there is an unpublished fiddle, which I am not about to expose here. You need to talk to Peter McLeland or at least read his readme files on the subject. Regards, Pete

Ah, the Alting module. It seems rather similar to a Microsoft tool, not yet made available generally. It is an FS module, not a free-standing program -- in the same way as FSUIPC is an FS module. In fact I think its AI graphics views are the ones you get with CTRL+W: it is generating that standard FS view for your selection. Since it is an FS module it can only run in FS. If you want to run it on a separate PC you have to have FS installed on that PC too. For FS2002 or before I'd then recommend you link them with Luciano Napolitano's WidevieW. That isn't available for FS2004 though, so for FS2004 the only way would be to link the two using Multiplayer. However, MP defeats the object completely as when MP is running you get no AI traffic. Even with two FS installations running on separate PCs, assuming you could link them and have AI running, there is no real way to get the AI synchronised so that it's the same on both PCs. I'm afraid your only solution is to have multiple monitors on the main FS PC and undock the AI display windows and drag them onto the other monitor. If you can do without the graphics and just want to keep tabs on the traffic details, then you can certainly do that on a second PC via WideFS using TrafficLook, supplied in the FSUIPC ZIP. For observing traffic movements at the airports, TrafficBoard (shareware) is very good, and that can be run on a second PC too. Version 2 works with FS2002, Version 3, for FS2004, is currently in Beta -- see the separate Forum near this one. Trafficboard also comes with an FS module which can bring up the appropriate CTRL-W window to view a selected aircraft -- but of course that window will still come up on the FS PC even if Trafficboard is being run on a client PC. Regards, Pete

The most likely possibility is that you have set the option to "suppress possible interference from Game Port throttles", on the Main Options page of PFC. As it says in the documentation "the suppression cannot be on by default because Wilco’s 767PIC (and others) uses the same input controls to operate the auto-throttle." -- perhaps this also applies to PSS aircraft? Otherwise, the A/T getting overruled is often a symptom of jitter on the axes, but this shouldn't really be applying to the PFC gear, especially not with the smoothing incorporated recently. Where do you 'park' the PFC throttle levers when using A/T? Certainly the PFC driver will only be sending throttle values to FS when there are changes, so jitter does sound a possibility. Try calibrating the levers with good "dead" zones at both ends, so you can park them at full throttle and at idle and be sure that no changes are being sent. Regards, Pete

Does AIView actually show the aircraft graphic, or just details of its activity, like TrafficLook? If you could tell me more about it I could perhaps advise what might or might not be done. Have you an URL where I can get it, perhaps? Pete

Sorry, I don't understand any of this. What's AOM and Sound Carpet? What's the FS top bar? You mean the Title Bar? What does that say? FSUIPC doesn't do anything with any "bar", title or otherwise, and since I've never heard of AOM or Sound Carpet I cannot really see how FSUIPC has anything to do with either. Very sorry. Regards, Pete

According to messages on some of the other forums, this is because the Microsoft/Jeppesen weather service has been down for a while. I don't know when it'll be back up. Maybe it is already. See for instance this thread in the FS2004 forum: http://forums.simflight.com/viewtopic.php?t=15341 Regards, Pete

That is because FSUIPC needs to know when you have loaded a new flight or weather scenerio using FS facilities so that it doesn't try to overwrite it with any externally set weather. That's all it means. It isn't FSUIPC clearing the weather, it is clearing its memory of external weather from FSMeteo or whatever. By doing that you are asking FSUIPC to make changes to the weather FS sets itself. If it does this you will never, for instance, get weather themes to stick. They will always revert to "user defined". That is what that is defaulted off, so you don't get FSUIPC interfering with anything! You needed to leave it alone, as it was. You have set it the reverse I'm afraid. FSUIPC doesn't touch downloaded weather UNLESS you change some of its options to allow it to. That is why the defaults are set that way, to avoid the confusion you have got into by misinterpreting one log message as its reverse! Regards, Pete