Pete Dowson

That's okay, thanks! If you could show me the log too (whether it works or not): enable Button / Key logging (only). Pete

No. There is nothing supported in older versions which is not supported in new ones. I have never heard of a program issuing such an error! Is that the real wording it shows? Please be explicit. Are you using a registered install of FSUIPC? Maybe your system date is wrong or your Key is in error. Both can give misleading results. Try removing your FSUIPC KEY file from the FS Modules folder. If it then works you either have an invalid key, or your PC system date is set earlier than your purchase date. Pete

Well it does matter to me as I have a policy of only supporting the stated supported versions -- namely the one on current release or interim updates made available since then. I do this explicitly to encourage people to keep up to date. It makes less support load in the long term. Hmm. "AP panel altitude hold" certainly does here for default aircraft, including the Cessna 172, and in fact this control has been in continuous use doing that on many cockpits now for many years (since FSW95 days at least). Here's a log entry showing me clicking it with the mouse: 146860 *** EVENT: Cntrl= 65799 (0x00010107), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_HOLD The same control sent from a button or keypress does the same thing. Maybe you need help from the author of the "Aeroworks B200"? I'm afraid I don't know what that might do, but try logging -- switch on Event logging and you will see the control name or number for each FS panel button which issues an FS control. Er, offset numbers? You are confused! Offsets are addresses of values in memory, offset from a base. They deal in VALUES, not CONTROLS. Please never mix them up otherwise you will most certainly get into a mess. Do you want to use offsets, i.e. from an FSUIPC application program, or controls, i.e. from buttons or keypresses? I've no idea what SIOC does. The offset related to the heading bug is a an area of memory containing the actual heading value. To increment it you read it, add something to it, and write it back. FS control numbers are assigned by Microsoft (they are "KEY EVENT" numbers in their gauge programming kit), and i provide a complete list in my documents. FSUIPC controls are ADDITIONAL to the ones invented by Microsoft, and they are all listed in the Advanced Users documentation. Please be sure to be using a supported version of FSUIPC next time you ask a question, please. Pete

Okay -- found it! It's a bug. It only obeys the first line, UNLESS the very first Macro in the MCRO file is also multi-lined. Evidently in my multi-line tests I used files with only multi-lined macros in them. Good catch! I'll fix it today. Look out for new interim updates for both FSUIPC3 and FSUPC4 in the Updates Announcement later. [LATER] Okay, it's up. 4.428 fixes this. Regards Pete

What does that mean? :shock: For all the standard analogue axes on a digital PFC system you should be using the calibration facilities in the PFC.DLL. FSUIPC cannot see tham in any case unless the PFC driver can read them. Sorry, you are not making sense to me. Please go back to square one. Look in the Modules menu, select the PFC entry. You should get a dialogue box come up in which you can calibrate and assign the yoke, the pedals and brakes, and the 6 axes on the throttle quadrant, for which you can choose an existing configuration or make your own. Make sure you select the Cirrus console in the console options. You shouldn't have to use FSUIPC for any normal axis use whatsoever. Please check inside the PFC Zip file. You'll find a User Guide for the PFC driver which explains all the options at your disposal. I think you must be missing all this, somehow. :-( All axes can be seen by FSUIPC but you shouldn't be using them. Why are you using FSUIPC even for those when they are supported in the PFC driver? Sorry, but If it works on default aircraft then the problem you have is with the add-on aircraft. I've no idea what the add-on aircraft is doing. You need to talk to their support about that. Regards Pete

Those should work. Maybe it is too fast for the gauge, though that seems very unlikely -- after all it isn't calling the second routine till the first one returns. I don't have the MD11 to try this on, but I'll check it on the 747. Can you dprovide a little more information please? 1. Version of FSUIPC. (You only said "latest FSUIPC4" -- that's meaningless. Please always give version numbers!) 2. If not the real latest increment (4.427), please try that so we are on the same base 3. Enable Button & Key logging in FSUIPC's Logging tab, operate the LLdown macro and show me the logged results. Thanks, Pete

Right, so isn't the answer to just operate as FS does, i.e. obey the last one you see change each time? Ignore axes until they change. Then it doesn't matter. Regards Pete

But did you cut and past the name and the email address too? All three parts MUST be identical to those given. If the key is rejected then it doesn't match the name and/or address. Oh, BTW, it is WideFS 7 for FSUIPC4. WideFS 6 is the FS9 version which works with FSUIPC3. Pete

Yes, but that's only the same sort of thing as Fly-by-Wire for Airbuses. Why not use the calibrated final values for the throttles -- i.e. the values which would have been written to the throttle offsets if you hadn't disconnected them? They are provided in offsets 332E - 3336. Regards Pete

Why aren't you using the PFC driver facilities? The FSUIPC axis assignment should not be needed at all, all the standard needs are catered for in the PFC driver already. And do please test on default aircraft. I really cannot support complex add-on aircraft as I have no idea what they do. Get it working on default aircraft and, when it is, contact the add-on support to find out why it doesn't work on theirs. Regards Pete

No. The window is part of the saved flight file, not the panel files. It is actually an FS window akin to the ATC menu, and its state (position, size, docked / undocked) is part of the Flight information, in the FLT file. So all you need to do is size and position it how you like, and save a flight with ti so. In fact the Flight file can save different docked and undocked positions and sizes for these types of windows. Look in your FLT files. FS doesn't associate it with a panel. Regards Pete

Why not simply act upon the values supplied for the throttle POST processing -- i.e. actual controls (key events) FS uses for the same things? Why worry about where or how it is arranged that they arrive or processed, it's the final values which do arrive which matter, surely? Regards Pete

There aren't any FS9 commands for LNAV / VNAV, because FS9 itself doesn't provide such modes. You'll need to see if there are keystrokes in the 777 add-on for those which you can use, or else, with a registered install of FSUIPC, whether they are responsive to the mouse macro facilities. Regards Pete

Good. I take it you still want the reverse zone? If not you would find it easier to simply check the option for no reverse zone, and then there would be no centre zone to set, just a max and min. The option for 'no reverse' are on each of the 4 throttle / 4 mixture / 4 prop pitch pages, and are independent for each of the three controls. Regards Pete

Well you can by editing the INI file and making the additional assigns by hand. But I would instead recomment simply making a new multi-line macro and assigning to that. Just edit the Macro file. The format for single lines in n== For multiline is would be n= n.1= n.2= and so on. as per Advanced User's documentation. Your macro actions can contain any keypress or control actions: this isn't just about "mouse macros". Macro files are for anything. For more advanced options, with decisions, loops, reading FSUIPC and FS values, displays, asking user for input and so on, you use the Lua plug-in facilities instead. Regards Pete

Only the INPUT values are set "arbitrarily"! The calibrated output value, the one sent to FS, for IDLE, is ALWAYS exactly zero! Reverse thrust is -ve, forward thrust is +ve. it really is that simple. That is exactly the way the "THROTTLEn_SET" controls in FS work -- there is no reverse range on the "AXIS_THROTTLE " controls anyway. I've no idea what the authors of this aircraft have done, but the problem is certainly nothing to do with uncalibrated "arbitrary" values! :shock: regards Pete

No, the model railway is in a downstairs room, at the back of the house. I have still to find time to re-program that, it is still run through an Amiga! The upstairs room houses my 737NG and Piper Arrow III cockpits! ;-) Regards Pete

Two important points here: 1. You have a generic all-engine throttle calibrated on Page 1 as well as two independent throttles on Page 3 of FSUIPC's calibrations. You shouldn't do that. Either use one throttle or separate throttles. 2. You seem to be missing the point of the separate engine calibration facilities. When you look at the calibration page, don't you see "Reverse" on the left and "Idle" in the centre? There are reverse, centre and forward zones for throttles, mixture settings and prop pitch. The part of the lever movement you are "missing" is that which, with an appropriate equipped aircraft, you get reverse thrust, conditioning or pitch settings. You appear to have rather ignored the instructions, the steps to successful calibration, provided in the FSUIPC user guide, as you most certainly have not calibrated a centre IDLE zone at all -- the two centre values appear to be defaulting! The whole point of providing a method of setting the centre/idle values is so that you can put that where you like! You've just left it where it happened to fall -- 1/4 of the way on your lever movement, apparently. Please please please do look at what the screen shows and make use of the documented facilities to achieve EXACTLY whatever it is you want to do! If you want no reverse zones on the axes, just check that option. If you don't see the option to do this, you have an old version of FSUIPC and need to update. Regards Pete

You have a throttle quadrant with a built-in radio? Wow! That's unusual! Sorry, no. I don't know anything about Symulatory or their software. Please check with their support. And, incidentally, my program is called FSUIPC, not "fsuips". Regards Pete

These are the INput values? The OUTput should be from -16383 to + 16383. Are you not seeing that? Have you not calibrated, leaving a small "dead" zone at each extreme to ensure you can reach the minimum and maximum values? It will if that is what it sees. When you assigned the axes in FSUIPC's Axis assignments, did you assign "direct to FSUIPC" or to the normal FS axis controls? Try assigning them direct, THEN calibrate in FSUIPC. It sounds as if you've not done this. If you still have problems, please show me the [Axes] and [JoystickCalibration] sections from the FSUIPC4.INI file (in the FSX Modules folder). Regards Pete

No, don't do that. Make the assignment and calibration settings for the Citation aircraft-specific. Then FSUIPC will switch to them only when you load that aircraft, and you'll still automatically have your other settings for the other 20 or so. You might also investigate the Profile facilities I added for this in recent updates -- see the Updates announcement. There's a user guide for profiles in the downloadable Zip. Regards Pete

I hope some other Citation users will come to help you here, because I don't know. From the response you got from Eaglesoft it sounds like they actively intercept the generic single throttle and use that, which really prohibits having reverse on the same lever. Of course you can retain your existing throttle setup for other aircraft and have the Citation done differently by making the assignments and calibrations in FSUIPC aircraft or profile specific. But that doesn't help with the Citation. Regards Pete

Looks goodexcept you spelled FSUIPC as "FSCUIP" in the title. ;-) Pete

Not really, as I don't know vb.net at all. How is that type "SimConnect" defined? Is it supposed to be the handle (which is a pointer in Windows terms) to an open SimConnect connection? And what is "Nothing" defined as -- is that similar to the "NULL" of C/C++ ( which is defined as a zero void pointer I think)? If the location assigned for "SimConnect" is in your program, and it is something to which "Nothing" can be assigned, the obviously it should not be able to cause an error. But in any other case I would certainly expect there to be an error reported, and it may simply be that in the XP case it is in error but the memory wrongly addressed is read/write enabled, possibly by being within the range of a chunk so assigned. Isn't VB.Net a Managed (i.e. partly interpreted) language? If so, it must be quite difficult to debug these things easily, with so much of the memory access buried deep in the interpreter? Regards Pete

I might possibly be able to help if it said the connection to FSUIPC was not ok, but .dat files are nothing to do with FSUIPC or anything related to it. You need to ask Arrestor Cables 2.6 support for help. Pete