Pete Dowson

Six -- three with Run and 3 more with RunReady. That should be perfectly clear in the WideFS documentation. Isn't it? FSUIPC allows a further 16 -- up to 8 by Run and another 8 by RunIf. That too is explicitly stated in the documentation -- in fact in the first paragraph about the Programs facility in the Advanced User's Guide. Pete

Sorry, I didn't even know there were FS-controllable operating doors until recently -- I thought those were fiddled special graphics effects using things like spoiler or flap settings. Inside FS I have found just one indicator for doors -- for the main doors only. This may simply be the usual trouble with the interference of multiple controls being sent every second by complex panels -- I assume it is complex panels you are using? The same problem causes difficulties like the acceleration of changes to the heading, speed and other settings (for which I provided a "work-around" in FSUIPC). The difficulty is easily seen if you try to use FS's pushback. You press Shift+P to start the pushback. That's fine. But then you press 1 or 2 to turn you left or right (or whichever way it is). If any other control comes between the Shift+P and that 1 or 2, then you are sunk -- it will not be directed to the correct part of FS. The Shift+P mode is closed, finished, not taking any more input. I think the Doors are controlled by something like Ctrl+E (or is it Shift+E?) then the door number (1, 2, 3 ...). Isn't that right? This will be working the same way as the pushback -- and if any other control is seen by FS between the Ctrl E and the number, that's it -- the selection is done. (The result should then be that the default, the main doors, are operated -- is this so?). I really don't know what the answer is unless you dispense with the panel. It's not really a fault in FS -- though a design that needs a follow up like that is bit flawed in my opinion. For the pushback I did experiment with setting the 1 or 2 as a parameter (programming it in FSUIPC's Buttons or Keys), but that doesn't work. When MS were questioned about this sort of thing, in relation to the unwanted acceleration of A/P values, they did imply that the panels which are doing this continuous sending of controls are really not designed correctly. Of course they didn't outright condemn them as "bad". Regards, Pete

I don't know how the "Flight Keeper" tool is causing FS to crash -- they may be two separate problems, but the "timed out all retries" problem is almost inevitable if the program is loaded before FSUIPC is running -- and FSUIPC isn't running until FS is running and ready to fly. Some FSUIPC applications can be run before FS and sit around waiting till they can connect (and this is good design), but unfortuately many can only be loaded when FS is ready. You can get FSUIPC to load them for you with the stipulation to only load them when FS is fully ready -- see the FSUIPC Advanced Users guide for information on editing FSUIPC.INI, or try the "Run Options" program by Jose Oliveira, also available on http://www.schiratti.com/dowson. Regards, Pete

I have it listed for the next version. Regards, Pete

Yes, you are. The FSUIPC programmer's guide shows what is currently implemented by FSUIPC. As I said, I can consider providing offsets for these, but they won't appear in the Programmer's Guide until I do! How can they? :wink: I referred you to the lists of FS controls I provide. See http://www.schiratti.com/dowson. Alternatively just load up FSUIPC, go to the Buttons or Keys page, and assign a button or key to the controls I mentioned (hint, look for 'T' for 'Toggle' -- they are all in alphabetical order). Pete

How are you trying to copy it in? The way Windows Explorer works, if you try to move or copy a file into a folder where there is already a copy present, it just asks you whether you want to replace it or not. Just say yes, you want it to be replaced. There's no rocket science here, it is just one simple file to be placed in one simple folder. No complications, no registry, nothing further to do. The installation cannot be simpler. What 'game' is this? FSUIPC is desgined to run with Microsoft Flight Simulator, not with any game at all. What is "create game"? Erwhat program are you actually running in the first place, please? Then what do these three lines say? It doesn't sound like anything of mine, to be honest. What other planes? FSUIPC has nothing whatsoever to do with showing planes at all. Are you confusing it with Multiplayer? Ah, so it is Flight Simulator. There's no "create game" in that. You need to install FSUIPC. I don't know what else you have in there or what this 3-line thing is, You need to give more details. Never try to install files whilst the program (FS2004) is running -- it won't let you do that. But at any other time just copy the DLL into the Modules folder. Say "yes" if it asks for confirmation. That's all. Regards, Pete

There are separate Engine Anti-Ice switches already available. Looking at the Panels SDK it looks like both FS2002 and FS2004 also have provision for: PROP_DEICE_SWITCH STRUCTURAL_DEICE_SWITCH but I don't know if they actually do anything. I could "expose" these through FS offsets in the next release if they may be useful. There are controls to operate these too -- check the list in my FS2002 and FS2004 controls document. Look for TOGGLE_STRUCTURAL_DEICE TOGGLE_PROPELLER_DEICE so you can already program these through FSUIPC as it stands, though you cannot read the current setting. Regards, Pete

It is not possible using my VXD which only works with Win95/98/Me. I know that Ralph of R&R (EPIC makers/designers) was intending to extend the Windows driver he developed for the USB EPIC to handle the ISA version too, but I've not heard that he did actually complete this yet. You need to inquire directly to him, or at least to Flight Link, the distributors. There is also an EPIC web section in Avsim, called bluesideup I think (try http://www.avsim.com/bluesideup) which may help. Regards, Pete

Yes, I can understand that. In my case I've been well and truly tied into MSFS for many years -- right back to FS4 in fact when I did my first FS "hack" to get my EPIC fully working with it. If MS ever gets fed up with FS and stops developing it, I will have almost a garageful of junk! :) :? :o Regards, Pete

Why not simply go to FS's Options-Settings-Assignments, select the Joystick tab, find both brakes there, and delete the assignment? Then, to be safe, close FS, reload. Check if FS has reassigned them automatically -- if so do they work? If they weren't reassigned, go back to the Assignments, assign them -- and also check that the sensitivity hasn't been reduced to zero (I've had that happen to me on some axes). Regards, Pete

Not sure what you mean by this. There's not been one instance yet where amicable agreement on terms has not been reached very quickly. I expect the other party to be honest and fair, and trust in their judgement as to what sort of reimbursement is reasonable and realistic. Same with the methods of payment. Please, in the first instance, download the FSUIPC SDK from http://www.schiratti.com/dowson and read the Access Registration document. Section 4 is relevant. Then contact me on petedowson@btconnect.com. Regards, Pete

Why? Don't you think my driver for FS is good enough, or is it because you want to use this with games as well as serious simming? :wink: Well, the "S" in "USB" means "Serial", so of course it is. But in addition the 9-pin COM port is RS232-type serial and seen as a COMx device in Windows, and the USB port is handled by a driver which also makes it look like a COMx device. Makes life a lot easier for us programmers! This is not unusual for all sorts of devices -- I think you'll find PDA cradle links, though now almost universally USB, actually use the same technique. Well the Cirrus II has built-in throttles, the standard 6 linear pots with driving rods -- you mean there were no lever sets supplied? They are mechanical devices which bolt on. Odd that they'd not include at least one. Regards, Pete

I don't use keyboard controls, but I am aware that some of the A/P holds do mean "hold at the current actual value", not as you may think, "hold at the A/P set value". Certainly CTRL+R for speed hold and CTRL+Z for altitude hold work like that. CTRL+H doesn't do it though -- that respects the heading bug/value. The "AP Airspeed Hold" control retains the AP setting, however, so you could re-program the CTRL+R keypress in FSUIPC to operate that control -- it will then do the same as clicking the button on the panel. Regards, Pete

I've not really tried this (I use PFC throttle quadrants -- the turboprop ones have gates and you have to push the lever sideways to get them below these). However, I would have thought you'd need something harder than rubber bands. I would get a softish pencil eraser and experiment cutting different pieces -- something from the rounded corners might be best. You could cut a groove in the non-lever-contact side to make it easier to glue firmly on the edge of the slot. Another way would be to actually screw some sort of hinged gate across which you have to move out of the way -- but that's a bit of an engineering job and presupposes enough room and a good strong (metal?) housing. Regards, Pete

This is all down to the multiplayer link, which I'm afraid I know absolutely nothing about. Maybe someone who knows about these things will chip in here with some advice, but otherwise you may be better off posting this in a virtual flying or Squawkbox forum. Evidently the FSUIPC part is all working -- it is just answering SB's questions about your own position and so on. Incidentally, a more appropriate thread title might be necessary to get the people who know these things to read it. As it is it seems to be directed only at myself. :? Regards, Pete

The advice I've given to others trying to place a reverse zone on a normal throttle axis is to glue a small piece of soft rubber or similar onto the slot as a kind of "gate" -- not stopping you pulling back, but just something you can feel is there so you know not to pull back further. No problem, just glad the penny dropped eventually! :) Regards, Pete

The King Air, to take an example, has no separate reversers -- they are simply the zone on the throttle below the "idle" position. On the real things there is a notch which prevents accidental reverse being engaged when you pull the levers back. The reverser levers on jets such as the 737 and 747 are actually separate levers which only become accessible when the thrust levers are pulled back to idle. To simulate this I provided a way of using a separate axis, assuming you have one spare. With most of the extra axes supported by FSUIPC (but not by FS itself) -- the rudder and aileron trim, the flaps and the cowl flaps -- I don't assign a "spare axis" by default, because it is impossible to tell what might be spare. However, in the case of the reverser axis, because it really is only applicable to jets, and because jets don't need a mixture axis, and because the reverser facility was in high demand, I assigned the mixture axis by default for jets. Sorry if this confuses you. For most it made things easier, that's all. It saved having to work out an axis control number and edit the INI file for those who simply wanted to add a reverser lever to their jets and had, for instance, a CH USB yoke with a mixture axis going spare on jets. It's odd that you use the term "feather" with reference to the mixture axis -- feathering is what you do with the props. It is even the word used for the minimum Prop setting in the Options (the values set are for "Feather", "Min" and "Max"). The Mixtures page allows you to set "Min", "Idle" and "Max". These terms are those I was advised as correct by turboprop fliers. Anyway, assuming you are mixing up mixture and prop settings, you can do exactly the same to get a reverse zone on the throttles. The three values you set are named "Reverse", "Idle" and "Max". Isn't this clear enough? Take a look through the assorted pages in the Joysticks section. Try pressing "Set" in each one (you can't do any harm -- just press "Reset" afterwards and you are back to where you were, or simple cancel or ESCape from the options altogether for no changes at all). All three axis treatments are the same inside FSUIPC -- it's actually all the same code! Yes, there is. It is page 3. You must have gone past it to set your Mixture (or more probably Props) on the following two pages. As I said, with a single all-engine throttle you get to use the 4 separate throttles page by mapping the single one -- there's a checkbox for that. Don't blame me for this method, by the way. In their wisdom Microsoft didn't provide a reverse range on any of the all-engine controls, but did on all the individual engine controls. Pages 3 4 and 5 provide the full range with reverse etc. The single all-engine controls do NOT offer reverse, or feather -- look at the single all-engine Mixture and Prop settings (page 2) for example. You are really confusing yourself by not looking at this stuff and reading about it. Please, please, please check the documentation, the bit that says: "If you have a single throttle control and you’d like to have an idle and reverse zone on this, then in the throttle part of page 1 select the “Map to 4 throttles” option. Then turn to page 3 of 6 and calibrate your throttle using the throttle 1 axis. The other three will match exactly. Choose the minimum (full reverse) and maximum (full forward) in the usual way, but then make a centre ‘idle’ zone wherever you want it on your lever’s movement—close to a détente or other stop if you have one." Did you not see this at all? It is there, in the Joysticks section, and has been for years. I thought I also pointed out the method to use in a previous message in this thread. :( Regards Pete

Fuel in FS jets is operated by the mixture control. See offsets 0890 (engine1) etc. There's one for each of 4 engines. Check FS's own controls for jets -- if you've ever operated the fuel cut-off in an FS jet you will have used the mixture rich/lean controls. It's been like that in more FS versions than I can remember! :wink: Pete

I don't understand what you mean here. If you are operating the throttle axis then FSUIPC will see it in the throttle section. If you operate a mixture axis it will see it in the mixture section UNLESS you opt to "Set" the Reverser, in which case the mixture axis will operate the reverser. Even that can be changed by editing the INI file first. No. What "control" is it that you think is on the mixture control? If you've calibrated a reverser there and not changed the INI file defaults, then, yes, FSUIPC uses the mixture input. It was chosen because that's not used on jets. However, the King Air is a turboprop, not jet or turboject -- you will need the mixture control to control the mixture! You need to calibrate reverse zones on the throttle and prop axes, not add a separate reversing lever -- look at the throttle quadrant in FS's own King Air, see the reverse zones. It is those you want to be able to use. The separate reverser axis input supported by FSUIPC is for jets which do have separate reversers. Sorry, I am really at a loss to know what you've done. I suggest you do two things: (a) make sure you get the latest version (3.212), as version 3.21 had some problems with joystick calibration in any case (b) delete the entire joystick calibration section in your FSUIPC.INI before loading FS, the start again from scratch. What's the problem you have with the documentation, please? If you are not flying a jet, it is best to completely forget the reverser axis. You don't need it, shouldn't be using it. If you want reverse zones on the throttle and/or prop axes, follow the documentation -- in FSUIPC to obtain a reverse zone you have to use the individual engine controls, not the all-engine ones. With single axis inputs you use the facility to Map the single axis to the 4 separate ones. This is explained. Ouch! That is completely wrong. It takes away the throttle axis for normal use then! The whole point of the separate reverser axis facility is for when you want to use a separate reverser axis. If you want to use the SAME axis you have to calibrate a reversing zone on it! The facilities for calibrating throttles with reverse zones has been in FSUIPC for about 4 years, and has been used successfully by many folks simply following the documentation. I cannot understand how you are so misconstruing everything. Please forget ENTIRELY all about the separate reverser axis -- if you have no spare separate axis to assign to it it is of absolutely no use to you whatsoever! Regards, Pete

If you want Magnetic Heading -- the one which would be displayed on a calibrated gyro-driven heading indicator, you need to read both the aircraft heading from offset 0580 (whch is TRUE), and the magnetic variation from 02A0, then do the calculations to get MAGNETIC. If you want to make this incorrect for gyro drift when the pilot has not adjusted it to read the same as the magnetic "whiskey" compass when last flying straight and level, you need to also add the current drift amount from offset 0C3E. Modern jets wouldn't need this as the setting is automatically adjusted -- but the drift will be zero then in any case. If you want the "whiskey" compass heading, which will not be showing you actual headings in a turn, only when flying straight and level, then you need instead to read the double floating point value at offset 02CC. You don't need to do any calculations with that one. I think that about exhausts the varying "headings" you can deal with! :) Regards, Pete

Yes. Sorry, what do you mean, here? If you want to be able to use your throttle lever for reverse, merely map it in FSUIPC to the 4 separate throttles, then calibrate for reverse and an idle centre on the 4-throttles page. The "reverser" axis facility in FSUIPC is for those folks who want to retain the complete throttle axis movement for forward thrust control, and set reverse throttle separately. The default assignment in FSUIPC for the reverser axis is, in fact, the Mixture axis, but this is not relevant in your case, and anyway you can change that easily enough in the INI file, as described in the Advanced User's guide. The FSUIPC facilities allow you, the user, to decide what to do with your controls. It is really nothing much to do with the aircraft. There is usually a reverse setting for propeller pitch on turboprops. FSUIPC allows this to be calibrated too. Perhaps this is confusing you? It is certainly not true that FSUIPC "expects" reverse control to be there. It doesn't care where or how you want to assign and calibrate your controls. Regards, Pete

Signed means the number can be negative (i.e. less than zero) or positive (greater than zero). Those terms are pretty ordinary English words really, not at all technical. An example of a positive number is +1, whilst -1 would be a negative number. Headings are not generally used in a signed sense -- a heading runs from 0 to 359 degrees (plus fractions of course). But the magnetic variation might add to or subtract from that depending on whether the local mag var is to the East or West, and whether you are converting from TRUE to MAG heading, or from MAG to TRUE. Offset 02A0 contains only the magnetic variation, NOT the heading. Please refer to the table in the Programmers Guide where all this is clearly defined. I think you need to understand what you want to do and what the terms mean BEFORE you start actual programming. Do it on paper, with a pencil, some paper, and a map. Learn a little navigation the manual way first, and everything will soon become clear. There are some very good books on all this. It sounds like you are trying to run before you can walk. Regards, Pete

It must have been some sort of timing thing then. Maybe the polling in 3.21 was just coincidentally at the wrong time compared to the driver for your joystick. I've made all the default pollling, both in the options and in normal usage, twice the speed now, in 3.212. That should avoid such things in future. Thanks for letting me know! Regards, Pete

The aircraft heading is as supplied by FS without any calculations being done by FSUIPC. There will be no difference at all between versions 2.xx and 3.xx. The difference you are seeing is probably because you are checking the values in difference places -- the magnetic variation varies a lot all over the world. If you want the magnetic heading you need to convert from the true heading you are reading. See Brian's post, that should help. Regards, Pete

I've done some experiments with assorted USB-connected joysticks and can just occasionally get inconsistent recognition of button presses. I think maybe this is a timing issue -- possibly the differences between previous versions of FSUIPC and version 3.21 has made this worse. I have withdrawn 3.211 and made changes to speed up the button polling by default, both in the Options and in normal use. As far as I can tell there is no way it will miss them now -- I will release 3.212 soon. Meanwhile, you could try adding "PollInterval=30" into the main [buttons] section of your FSUIPC.INI file. This won't help in the Options screen (it isn't used there), but it may do in normal use. If it doesn't help, then possibly neither will 3.212 -- I would be completely mystified then! Please let me know. Regards, Pete