Pete Dowson

By "constantly pressing" do you just mean "pressed" or "on", or pressing repeatedly, as in "on off on off ... etc"? Do you just mean using its position as a conditional to select different functions on others? What is the siginificance of the emboldening here? And why use flags when, if the mode buttons are held on, or pressed, you can just use the button state itself as the condition? seems more complicated to use flags. Now I'm completely lost I'm afraid. Are you saying that in addition to the three modes selected by the 3-way mode sleector (buttons 23-25) you want other buttons or knobs to also act as mode selectors? Multiplying 3 x n different uses? I looked at the log but I'm none the wiser. I can see that you have the "F" for flag set in all of your conditions -- which surely isn't needed if the selecting buttons stay pressed or on. I also see you using button 16's flag BUT you seem to also be manipulating it directly, as here: 27=P0,16,C1005,16 -- OKAY, it toggles Flag 16 This is a rather odd thing to do, considering that pressing 0,16 toggles its flag in any case. You want to toggle it twice? Usually the Button Flag controls are used for extra flags, on buttons you don't actually have (out of the 512 possibles). You never really want to use them for buttons you actually do have unless you never want to use those buttons. as the documentation says, here: From those parts of what you say I think I understand, I think you only really want to make conditions based on the state of a button or switch, in which case you should use its Flag, just the button itself (+ for on, - for off). Regards Pete

There's nothing in any part of FSUIPC or any other add-on I know which will change how an autothrottle works within the coding of a particular add-on aircraft. It is nothing to do with any external controls, which become ineffective. The only control is the airspeed or climb/descent mode selected. If you have a problem with specific add-on aircraft you must deal with the support persons for that aircraft. The axis controls assigned and calibrated via FS or FSUIPC are for manual control.. I am suspecting that there are parts of the aircraft automatic control that you are not familiar with and are therefore not setting correctly. For example, with Boeings, depending on the vertical or speed mode selected, the speed to be achieved may be dependent on the setting on the MCP speed dial, but equally may be settings in the FMS -- for level change and V/S modes the airspeed setting may be overridden. One of the problems of flying a large variety of different aircraft is that you may never become fully familiar with any of them. In the specific case of an Airbus with throttle-lever controllable thrust modes, I cannot advise in detail as I am not familiar with Airbuses, and I do not have any Airbus add-ons to even look at. But if they need specific keystrokes or controls sent to them to set modes, and you want to do that with the throttle lever, then you need to look at assigning those keypresses or controls to assorted axis zones on the right-hand part of the FSUIPC axis assignments tab. Regards Pete

How do you do that? I've no idea. Regards Pete

Version 4.60? If earlier, please update it with the currently supported version. Not normal unless the Saitek software is diverting the use of the button to other things. If FSX sees the button, so will FSUIPC. Why? What's the problem? Just because it is English? I can't improve it unless you can be more specific. Pete

By "trust" do you mean "thrust", or more commonly, "throttle"? No access? Do you mean no success? There's no way FSUIPC or anything else will let you dynamically change an axis assignment whilst flying, only when changing aircraft (and then only FSUIPC, not FS). You'd have to write a little Lua plug-in program to send the value of variable ipcPARAM to either throttle or spoiler axes according to a button or switch setting, then assign your axis to execute that Lua plugin instead of to any FS control. Regards Pete

Give me some numbers, and show me the [Axes] section of your FSUIPC4 INI file, please. What lights? What make of avionics stack is it? Really there can be no possible relationship between assigning axes in FSUIPC and your avionics, unless you've been assigning axes to send assorted avionics-related controls! If not, you most certainly have something else going on there with your hardware. Nothing whatsoever will "come up" in the assignments sections unless you have made an assignment! You must have made assignments already and forgotten! The picture you showed earlier showed that you assigned all 4 "Throttle N Set" controls to the Z axis. Didn't you delete those (uncheck the radio buttons left of each)? It is meant to do what it does -- to show you existing assignments, and to let you change them or make new ones. It sounds as if you have got yourself thoroughly confused, maybe plunging into things without thinking. If you don't know what you've done and don't want to undo it correctly, just delete the FSUIPC INI file and everything in FSUIPC will revert to defaults, with no assignments at all. It does just what you tell it to! It is only "sensitive" to your requests, nothing else. A log file is only useful if it logs anything relevant, which this one doesn't. Better if you pasted in your INI file so I can see what sort of mess you have got it in, and advise accordingly, though from what you say I suspect it would be simplest and quickest for you to simply delete it and start again. Delete it BEFORE running FSX, not whilst it is running. Regards Pete

But you certainly do NOT need to "kill" any file. The installer uses the file to populate the fields, just to save you entering in the details that have not changed, but that in no way prevents you CHANGING them! Pete

The AdvDisplay program is redundant and has not been used or supported for several years. The display is now built into FSUIPC and is a regular FS window. Regards Pete

It's the latest full version with Installer, yes, and that version most certainly does accept different email addresses for FSUIPC and WideFS. I'm running it myself with two different email addresses. Please re-run the Installer and try again. Please read the Installation asnd Registration guide supplied with the Installer in the same ZIP. Pete

Thanks for the clarification. I must admit I was pretty confused. I hope Paul manages to work out what is wrong on his setup. Regards Pete

You must be using an old, unsupported version of FSUIPC, because all recent versions allow a different email address for FSUIPC/WideFS. Please update and check the Installation guide where this is made clear. Pete

I've added new offsets for these in versions 3.989k (for FS9) and 4.636 (for FSX and ESP). Please see the Updated Modules thread in the Download Links subforum. Regards Pete

Okay. Done. I've made it automatic when WideFS s not registered. Try version 4.636, now downloadable from the Updated Modules thread in the Download Links subforum. Regards Pete

No, but it sounds like the same thing that is causing the FSUIPC attempt to get the folder attributes to hang. I am sorry but I really don't know enough about Windows internals to be able to help at all. Possibly trying a Windows repair, from the Windows install disk, might help, or, if the damage has been done by something being installed which affects lower level modules (like, maybe, video or other hardware drivers), you could possibly try to find a rollback restore point which would undo the damage. Otherwise, I've a feeling that it's a Win reinstall job. For information, the "GetFileAttributes" call which is hanging FSUIPC is in the KERNEL32.DLL windows module, so using repair to get Windows to re-install its copy of that might help. Of course it may not be that module directly as it probably calls a host of others. And it could be a data corruption rather than a module one in any case. I was going to offer a facility to make FSUIPC ignore "Users" shares, in case it was specifically related to using that name, but if you've found the sharing problem applies to other folders too I don't think it is worth trying. If you do want an option in FSUIPC to ignore sharing altogether (so not using WideFS for anything) let me know. In fact I suppose I could make it automatic -- if WideFS is not registered, don't get UNC paths. What do you think? Of course it doesn't fix your problem, just goes around it, maybe. Regards Pete

There's never been any facilities in FSUIPC to "make button pushes with the mouse". I think you must be confusing different software? I do not know what you mean by "mapping a throttle to an idle button"! What's an "idle button"? How are you mapping a throttle to it? I've no idea what "dodosim" is, but if it's an add-on aircraft, please always tests things with a default aircraft first. [LATER] I just Googled "dodosim" and found it is an add-on helicopter. Do helicopters have "idle" buttons? What do they do, and how are you mapping a throttle to one? Do you mean that you've broken your throttle lever? Otherwise I'm afraid you'll have to explain yourself a little more. Perhaps you mean you need to re-calibrate? Have you tried to do so? Note that changing from a 32- to a 64-bit operating system in no way affects anything in FSUIPC. If you wanted to retain your FSUIPC settings all you needed to do was preserve your FSUIPC4.INI file which contains them all, plus of course any macro files and Lua plug-ins you may have created . Regards Pete

Right. The offset definitions derive from FS98 days where that probably wasn't simulated. However, I can obtain the separate deflections in FS9 and in FSX. I'm not sure which version you are needing. It isn't a difficult job in either case, it just means finding another free 8 bytes for the double value. It just has not been requested before. Note that, for FSX, the value at 0BB8 is derived fromthe Left aileron position only, whilst the 2EA8 value is what SimConnect calls the "average", so you could actually derive both values. In FS9 it won't work though as there 2EA8 currently provides the left deflection and I've no idea how 0BB8 is derived. Let me know. It isn't a big job -- I can include it in the next incremental interim releases if needed. Regards Pete

I don't know. Maybe they use one or more of the assorted velocity and acceleration values -- offsets 3060-30B8 and 3178-31D0. Some of those (but not all) are effective when written to, probably the ones saved in the FLT files, since they are re-established when reloading flights. The others are probably effects not causes. Regards Pete

Okay. That log line is made immediately before a call to Windows, to the API named "GetFileAttributes", using that path above as the name. In FSUIPC the line immediately after that call is another log line, looging the attributes being returned. It doesn't get there. There's something wrong with Windows which is causing windows itself to crash or hang on that call. Please try sharing the Flight simulator Files path itself, with any name you like (FSPLANS is usually a good one as I said). Meanwhile I'm going to try and reproduce the problem here by forcing the "Users" sharing to be used. ... .[LATER] Tried that. No problem here. This is with Win7, 64-bit Ultimate version. So, I'm sorry, but it is either a windows bug specifically in the version of windows you have, (which seems unlikely) or a Windows installation error or file courrption on your system. If the work-around, sharing the FSX files folder, doesn't work, I can't see an answer other than repairing or reinstalling windows. Possibly, if you are not using and never will be using WideFS at all, i could have a special INI file option to tell FSUIPC not to bother to convert paths to UNC form. This would simply keep them all local to the FS PC. Regards Pete

Hmm. Interesting that you've shared "Users" as a whole. But the registry entries look fine. FSUIPC isn't getting past the Users entry in any case. It is somehow crashing when trying to verify what looks to be a correct path to your FSX files folder: \\JERRY-PC\Users\Jerry\Documents\Flight Simulator X Files\ The very next action is to get the "file attributes" for that path, to make sure it is a valid path and that it is a directory,, not a file. Then, that's it ... ... so I am still a bit at a loss as to what is happening. I'm going to try one more iteration, one slightly tighter logging. If this shows, as I suspect, that Windows is crashing or hanging when I call it to read the attributes for that path, then I have no answer other than there's something wrong with windows. If it isn't solvable with this share name, perhaps you could try sharing the Flight Simulator X Files folder itself, say as FSPLANS, a name many programs like. But before that, please download FSUIPC 4635c by clicking this link, and copy it into your FSX Modules folder. Then edit the FSUIPC4.INI file, adding these two lines to the [General] section if you have removed them since the last test: Debug=Please TestOptions=x400 Then run FSX, get the crash, and show me the FSUIPC4.LOG. Thanks Pete

You use the FSUIPC entry in the AddOns menu, exactly as described in the documentation. It's a bit late now referring to a specific thread. Best always, in any case, to describe your own problem in your own thread. Obviously your problem was different, maybe reading FSUIPC3 documentation (relevant to FS9 and before) instead of the correct FSUIPC4 user documentation installed for you into your Modules\FSUIPC Documents folder? Regards Pete

I don't think you can set the user aircraft airspeed in FS9. Yes, there are a lot of improved facilities in FSX. Regards Pete

Thanks, but no, we'll get more info from the extra logging I'm doing. I'm now half convinced there's a Registry problem, but what it could be I don't know yet. Please do two things this time. First, before running FSX, run the registry editor so that you can extract the relevant section for me. you may need to be the Administrator for this: Start button, enter "regedit" and press return. In the Explorer-type path system on the left, select and open up HKEY_LOCAL_MACHINE then SYSTEM then CurrentControlSet then Services There'll be a lot of those. Scroll to find LanmanServer Then select Shares within that, and with it selected, go to the File menu, select Export, and save as, say "MyShares" to somewhere where you'll be able to find the resulting file. Close Regedit, find the file, open it with NotePad, and cut and paste its contents into a message here, please. --------------------- Please download FSUIPC 4635b by clicking this link, and copy it into your FSX Modules folder. Then edit the FSUIPC4.INI file, adding these two lines to the [General] section if you have removed them since the last test: Debug=Please TestOptions=x400 Then run FSX, get the crash, and show me the FSUIPC4.LOG. Thanks, Pete

Okay, I checked what happens with the PFC throttle quadrant in the FSUIPC4 axis assignments. It all seems to be working. Left-to-right the levers give axes X Y Z R U and V. Move one, assign it, Press RESCAN, move the next, assign it and so on. Same method for all hardware axes. No need to use "Ignore" buttons unless the axes are jittery -- when not calibrating leave them parked at one extreme position or the other. Regards Pete

You can assign in FSX and still calibrate in FSUIPC. You must simply not assign the same thing in both places. You can un-assign everything in FSX and leave the controller enabled. You just risk FSX sometimes seeing the device as newly connected and reassigning automatically. But that shouldn't happen if you leave the units plugged in all the time. I've never used mouse look so I've really no idea what it does, but it sounds like a possible candidate for an add-on program. Was it a feature of FS9 and before? How/why do you use it? There's almost no mouse handling in FSUIPC at all and I'm rather loathe to add a load of new code unnecessarily, but tell me more and I'll think about it. Assuming that this is not simple cross-interference caused by having the same axes assigned in two different places, it''s "jitter" which can be caused by many different things: 1. dirty, bad or faulty throttle potentiometers, 2. variable voltages 3. bad connections, inside the device or in the USB routing 4. temperature, humidity, stuff like that. Regards Pete

Hmm. That's odd. They are all assigned specific axis offsets for FSUIPC to read. Let me check and get back to you. They are confirming exactly what I said, that you need to assign to the standard FS controls, the "Axis Throttle N Set" controls. That's all they mean. [LATER] Okay, I checked what happens with the PFC throttle quadrant in the FSUIPC4 axis assignments. It all seems to be working. Left-to-right the levers give axes X Y Z R U and V. Move one, assign it, Press RESCAN, move the next, assign it and so on. No need to use "Ignore" buttons unless the axes are jittery -- when not calibrating leave them parked at one extreme position or the other. Regards Pete