Pete Dowson

Hi Wim, Thanks for the interesting answers from Ralph. Seems it is, or will soon be, all solvable! Regards, Pete

I'm afraid still don't know what you mean by "enable dynamic weather". Do you mean the slider which tells FS whether to change the weather quickly or slowly? Or are you trying to tell FS to download real weather from the Internet? If the latter, then it sounds very much like your Internet connection is not working for FS is some way. I think the parameters for that are in its CFG file, so possibly finding that and deleting it will make FS begin afresh. Otherwise, maybe you can get some assistance over in the FS2004 Forum. Regards, Pete

E000 only? How many bytes? The ground traffic, only, starts at E080, and then in slots. Unused slots will be zeroes. Sorry, I can't really help much with so little information. Please use the tools available to check what you are doing. Use FSUIPC logging (IPC read logging will show you, and me, what is going on), and also FSInterrogate will alow you to read and write any area in FSUIPC offset space. Regards, Pete

Well, of course, the Avionics switch on the Jetliner (and I think the Cirrus?) also actually operates the power feed to the avionics board. Once that's off I get no more messages from radios and such like. I cannot actually cut the power from the PC. I can blank the displays, but then I also have to discard any messages from the avionics. I've had a look at it now, and it a lot messier than I thought it would be, so it will go on my list to put in when I have time. If the avionics switch in FS is turned off whilst the real one on the Jetliner or Cirrus is on, then they'll get resynchronised only by toggling the latter. Unless of course it's one of the switches which are sent at intervals by the PFC firmware. I don't remember. Anyway, it certainly doesn't say again that it is off when it is off! Regards, Pete

I've never heard of a way. Mostly it isn't doing anything in any case, and it includes its own error trapping as well. What exactly do you mean by "dynamic weather", and what has that to do with FS2004 getting locked up? Sorry, but you seem to have omitted much more than you are saying. Regards, Pete

Best contact PFC themselves about this. If it is fixed as Elite protocol they may be able to offer a conversion. Can't hurt to ask. Regards, Pete

Er, doesn't it do that? I'll check. I know it works the other way -- the Avionics switch on the Jetliner console blanks the avionics displays AND operates FS's avionics switch too. Can you be a bit more explicit, please? In "Avionics Options" under "COM Radios" there's the full discussion, including the modes operated by the On/Off switches, then, where it actually discusses the avionics options there's the explanation of the check box labelled "COM2 radio selectable into FS: (Avionics stack)", or "COM on/off swaps COM1/2 display: (Jetliner console on FS2002 and FS2004)". The former is discussing the avionics generally whilst the latter is going through the specific checkable options one by one. What do you think is wrong? I can't see anything out of place. Regards Pete

:? You press "Set" to calibrate them and thence presss Ok to exit. You only press Reset to tell FSUIPC not to touch them -- it is the opposite of "Set". That's why the button changes back to "Set" when you press Reset, and why it then tells you that the axis isn't processed. When it says "axis not processed" it means that the axis isn't processed by FSUIPC. Press "Set" if you want FSUIPC to calibrate. It then shows you the calibrated values and when you OK out the calibration will be in effect. It only processes the axes when they have been SET, and it is then when the "axis not processed" message disappears to be replaced by the active calibration values. You don't need to restart. The effect is immediate upon OKaying out of the FSUIPC options. That must be the power of suggestion :) , as if FSUIPC says the axis isn't processed, it isn't processed by FSUIPC. You have to press SET for that, not RESET. They are exact opposites. One SETs the calibration, the other RESETs to FS's own methods. They were the shortest words to fit the button which mean the right things, and opposites. There aren't samples as much as pictures shown with default settings. By default FSUIPC doesn't process the axes. You have to press SET to do that. The RESET button is there in case you change your mind and want FS to control it all instead. Please re-check the documentation. There is a step-by-step guide to calibration there, and the only place it tells you to press "Reset" is in the section on "RESETTING DEFAULTS", where it definitely says "If you want to switch any of this off, either de-select them individually (pressing the Reset button disables the FSUIPC axis processing actions and restores defaults), or ..." Regards, Pete

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