Pete Dowson

There's an option I incorporated for that which according to testers worked fine. have you tried it? It is listed in the Button Programming section of the Advanced Users guide (around page 19). It is called "EliminateTransients". Not if an application or assignment is requiring this. It isn't a value being passed which changes views, it is a control -- same as you pressing a button or key to do it. But FSUIPC doesn't do anything like that by itself in any case. If FSUIPC intercepted and stopped such controls you wouldn't be able to change views at all. I don't think you'd want that in any case. What selection menu where? If the yoke is causing transient button pressing, which I believe was the problem, then the button it is pressing is obviously assigned somewhere to some view control. You are evidently not un-assigning that button somewhere. In that case you obviously have the culprit button so assigned in FSUIPC. Try simply deleting the button assignment in the FSUIPC.INI file. No. Yokes cannot send "variable offsets". It is a known problem where it sends a short-lived button press. It is so short-lived it cannot possibly be from a human -- that is why the EliminateTransients facility works. There is also an "IgnoreThese" facility for Buttons, also described in the Advanced user's document (same page in fact), but you do need to know which button it is first, and you would then lose the use of that button for other things -- like the views you appear to have assigned it for! Why not first try going to FSUIPC's button assignments and seeing which button it is which appears without you pressing it, when manipulating the yoke? Pete

You mean 9C 00 (AT off) and 9C 01 (AT on) I think. The TO/GA buttons should give 9C 00 (off) and 9C 08 (on). The second value is actually a bit-field, so 09 would mean both on, and there are other bits used for anti-ice and EICAS switches. Despite my statement that I understood, I have evidently misinterpreted pretty much most of what you said it seems. I thought all this exchange was concerned with the extra buttons you had on yours for TO/GA? From what you now say, it seems that this: was really meant quite literally -- that the TO/GA buttons, the lower ones, were actually being switched by my AT Disco / TOGA option! That is the complete surprise to me as that option is designed to switch the AT Disco buttons, not the TO/GA ones which normally don't exist on the Jet console. Therefore I now believe the entire confusion is due to those two pairs of switches being plugged into the wrong sockets under the quadrant -- or at least, wrong in comparison with my understanding and how they are plugged in on the Jet cockpit. In other words the PFC driver is seeing your TO/GA buttons at the AT/Disco buttons and vice versa. This is why I said: and continued on discussing, to my mind, the supposed problems with your TO/GA switches! :-( Never mindI'll harangue Eric about all this next time I see him! Regards Pete

Surely the pedals and wheel would be separate axes in any case? Generally the wheel is the X axis, or aileron and the pedals are either two separate axes or one (Y) according to Logitech driver settings. Why would you need a special controller? And what do you use for elevator? Strange. What about the other pedal? On my Logitech Formula Force EX the wheel is X but the pedals can be set either to be one axis (Y) or two separate axes (Z and something else I don't recall). I think most driving pedal sets allow either one axis for both pedals (because some driving games do require that), but also allow them to be separated for more sophisticated simulations like GP4, so you can hold brake and high revs simultaneously. Certainly the current Logitech drivers for my pedals provide both options, and can automatically select the mode according to the program being run. Sorry, I've no idea what that's about. How can you possibly make one single pedal into a useful rudder control if it is not made self-centering? You need to be able to have it neutral with no pressure applied, so you need it sprung down half-way. Regards Pete

Version 3.85 has been superseded by 3.90 and is no longer supported. As it clearly says, the version of FSUIPC you now have installed is so old that it does not even recognise the 9.1 update of FS2004, and is therefore telling you that your FS is incorrect for that version, which it is. If the check was not there and that ancient FSUIPC was allowed to carry on running it would give you inexplicable crashes instead. I don't think that would be preferable!? When FS2004 came out there was no knowledge of the 9.1 update as it didn't exist then. So the version of FSUIPC then could not check for a 9.1 release. All it can do is see if the FS version number matches what it should have been -- the message you see clearly states all this! All you need to do is stop using a 5 year old (at least) version of FSUIPC and install the currently supported one. I expect that really old 727 add-on is the true culprit -- it must have a really bad installer which doesn't even check that you have a later version of FSUIPC before overwriting it with such an old one! Pete

Well it certainly must be possible, because other programs do such things, but the whole area of Internet access from programs is unknown to me so it would mean taking the time out to investigate and learn new stuff. I'm not adverse to that, but generally find it more useful to get on with FS related developments. I'll certainly bear it in mind and might be able to fit it in one day. Thanks, Pete

Must be related to the aircraft. As far as I know the AP doesn't use the rudder at all. And I would never have noticed because I never fly outside the cockpit. I'm not sure why you are posting this here. Seems more something for general FS9 users. try the FS2004 Forum? BTW if you ever do want to report something about FSUIPC I will need the version number confirmed, not just "latest" which is pretty meaningless. ;-) Regards Pete

Must be related to the aircraft. As far as I know the AP doesn't use the rudder at all. And I would never have noticed because I never fly outside the cockpit. I'm not sure why you are posting this here. Seems more something for general FS9 users. try the FS2004 Forum? Regards Pete

I just downloaded SceneGenX here and it works here too. But in that case how does it work on that PC with 3.81? Or are you saying you didn't re-check with such an old version? Regards Pete

strange. Can you enable FSUIPC's IPC read and write logging (on the Logging tab), then try SCENEGENX and close FS. Show me the Log (or send it to me Zipped if it is too big). Regards Pete

There's no change which would have done that unless that program simply doesn't like the version number! What are the version number(s) of these "older" FSUIPCs it works with? The interface is the same for all programs, so if it doesn't work for that it wouldn't work for any, which is patently not so, in general. Are you a Registered user? If so, try removing the FSUIPC.KEY file from the FS Modules folder, to make it temporarily unregistered. Then try your program. If that then works, you have a registration problem. ZIP up the FSUIPC.KEY file and send it to me at petedoswon@btconnect.com and I'll check it here. Regards Pete

Amazing that they add these things and don't tell me! And if that was 4 years ago that was about the time I was adding the jet cockpit stuff, I think. I don't think you are reading my messages -- I did understand you perfectly as you will see. I also suggested this: "Maybe you told the PFC driver that you had a 737NG cockpit last time? Which you seem to have missed? I most certainly haven't changed anything to do with any switches on the jetliner (or jet cockpit) for years, so I've no idea why you see any difference. If the hardware is okay, then it surely must be some setting you are omitting, such as the console selection? [LATER] I just checked my code. As far as I can see (I cannot test on your hardware from here), I do have code in place to send the switches to FSUIPC even if it isn't a jet cockpit selected. The differentiation comes AFTER the sending of buttons to FSUIPC. And, as I say, nothing has changed in this area for years -- and it's the same on PFCFSX.DLL as PFC.DLL. Soare you sure the buttons are working correctly? Use "Test" mode in the PFC driver to see if they register on the right-hand side of that option page. Maybe the plug has come loose in the socket below the quadrant? So you did get the TO/GA buttons working? Can't you explain what you did to "fix" things, then, please? Regards Pete

How are they assigned -- direct or via FS controls? Have you disabled your controls in FS? Are you using some other software like Saitek's control program? What did you change to bring this about, or have you never had it working? Always test with default aircraft first. If you are using a fancy add-on aircraft it may be interfering. And please always quote VERSION numbers -- what version of FSUIPC? Pete

I didn't need the screenshot. That message isn't one of mine. evidently one of the things you are getting FSX to load is an FSUIPC client application. Perhaps an aircraft panel or a DLL. It seems most unlikely that whatever says it can't link to FSUIPC was quite happy linking to it when it wasn't even there! There aren't different versions for registered and unregistered users, there's just the one which offers more or less facilities. If you were using FSUIPC before, without registration, how can you be sure that FSUIPC was the last addon you added to FSX? Something is obviously trying to use it and failing. Don't you know what you've added to FSX? What was FSUIPC doing for you BEFORE you registered it? It must have been there for a reason, for something you are adding or using. Something loaded by default evidently -- maybe your default aircraft panel? No, that is very bad. When you find out what it is I should contact the author and complain about that. If the only change between before and after is that you registered FSUIPC, then there's a good chance that the registration is in error. Check that by temporarily removing the FSUIPC4.KEY file from the Modules folder. If you then don't get that message, then your key is bad. Either it is not a legal one, but one generated by a pirate key generator, OR it is one purchased AFTER the date your PC is set to. So, check your PC's system date, make sure it is correct. If it is correct then Zip up your FSUIPC4.KEY file and send it to me at petedowson@btconnect.com and i will check it here. Regards Pete

No, sorry. It does sound rather odd. But I've done no work with FS2004 for several years now. All the FSUIPC3 updates have been for user facility enhancements, not any more foraging in FS9. Regards Pete

Yes. Pete

I'm not clear why you'd even think of FSUIPC? Are you setting these things in the FS Weather menu? Why would FSUIPC be involved? Regards Pete

"Flights" don't link to FSUIPC or WideClient! And none of my software contains such a message! So you need to find out what program or add-on is telling you this -- it isn't FSUIPC or WideFS or FS itself, but something you are running or have added. You need to work that out then ask their support what is wrong with it. Regards Pete

That is NOT a good idea. Plug them in to separate ports and never swap them about. Assign specifically in FSUIPC's axis assignments and it will take care of the swapping for you. Calibrate specifically as well to suit the different controls and different aircraft. Disable joysticks in FS. That's because there were no Profile facilities in 4.40. There's a whole Chapter about them in the 4.50 user guide. Yes, in general it does matter. There are facilities in FSUIPC 4.50 to keep track of your controls in case you do move them -- you'd need to enable that if you want to use it. FSUIPC would then refer to your controls by letters, A, Betc (or whatever you choose). This is possible, but it isn't as good as simply leaving them plugged in. Aren't the wires long enough for you to leave them connected but shoved out of the way, under your desk or somewhere? Best to use the Profiles. Set up one profile for one set of controls, using your favourite aircraft for those, then ditto for the other set. Thereafter assign each aircraft you fly to one or the other. This won't work very well if you don't keep them all plugged in. You'd probably have to close FSX down and restart it each time you changed, in order to get them recognised again. If they are left connected everything becomes automatic according to which aircraft you load. Regards Pete

There are no notes with FSUIPC which explain the Lua language -- you need to refer to their website where the documentation is pretty good. The FSUIPC notes only describe the additional library functions provided by FSUIPC. What is actually confusing for you? I need to know about things like that so I can write clarifications into it. That is the only way I can improve it. Where are you reading that a 1 will disconnect the rudder? That is bit number 0. According to the offsets list the bit for the rudder is bit 2, in other words 2^2 or value 4. Okay. There are two different ways of doing this. You can make a rather complex loop to watch the button and do the timing of 9 seconds. Doing it this way you can have just the one Lua program and call it "ipcReady.lua" so that it runs when FS is ready to run. If it is programmed with the actual button number you want to use then you don't even have to assign anything to it -- it will run and loop continuously, sending a value to offset 310A whilst the button is pressed, sending 0 when released, and sending nothing otherwise. It would "sleep" most of the time to avoid impinging on FS performance. However, much easier to program would be a simple loop setting the offset, assigned to your button in FSUIPC, which tests not the button but a flag, which is set by assignment when you release the button. This simpler solution would look something like this: [EDITED ON 5th MARCH to correct omission of last line] seconds = 9 -- counter for 9 seconds while ipc.testflag(0) == false do -- loop until flag is set (all flags are clear when a Lua program starts) if seconds == 9 then ipc.writeUB(0x310A, 4) -- update the offset every 9 seconds seconds = 0 -- restart the 9 second counter end ipc.sleep(1000) -- give up the processor for a second seconds = seconds + 1 -- count that second end ipc.writeUB(0x310A,0) -- restore the rudder operation before exit Save this as, say, "NoRudder.lua", then assign your button press to "Lua NoRudder", and its release to "LuaSet NoRudder" with parameter 0 (for flag 0). Written this way it could take a second after you release the button before you get the rudder back. If that's no good, reduce the sleep time and increase the count proportionally. For example a sleep of 100 milliseconds would need a count of 90 to get to 9 seconds. Okay? I hope this all makes sense to you? Regards Pete

Really? That's news to me. Sorry, but that is their doing. I cannot support their website, you need to go to their support. All my software is supplied in the Schiratti site or here, in the Announcements. Can you report all this to PFC please, either via their direct support email or their forum. You have a version of the console which supports the 737NG cockpit throttle quadrant? Does it have detentes on the flap lever too? I didn't know they made any changes there at all -- they don't seem to tell me much! :-( In this past you mention, what was different? As far as I recall, the TO/GA buttons on the quadrant are only supported on the Jet cockpit. I wouldn't have supported them on the jetliner console because as far as I knew they couldn't exist! That's why I provided an option to treat the AT Disco buttons as TO/GA -- more valuable there because the AT arm switch is close to hand anyway (or is that removed from the console now?) Maybe you told the PFC driver that you had a 737NG cockpit last time? Really these are all things you should talk to PFC about. Especially if they change things without telling me -- I can't really offer support that way. Maybe you ought to mention this to them too, please. Regards Pete

Okay. Sorry for getting a bit irritated with you. Good flying! Pete

Where are you reading that "aircraft specific" is wrong? I don't understand you at all I'm afraid. Please READ THE CHAPTER ON PROFILES! It is called "User profiles for all control settings" on page 26 or thereabouts. It is even listed in the Contents page near the beginning! It tells you what to do! That is what documentation is for, to help you do what you want to do! FSUIPC defaults to only providing aircraft-specific options, not Profiles, because there are thousands of users already using the aircraft-specific facilities. Changing over is not automatic. You have to select it before running FSX, EXACTLY as described in the Manual. Sometimes I wonder why I bother writing documentation. :-( Pete

That's the install log I asked for. Okayso the INSTALL of FSUIPC4 failed! Why are you running the installer for version 4.40? It is NOT compatible -- the signature check will fail, because I've had to change the signature to that of simFlight! Please run the Install FSUIPC4 program which comes with version 4.50, then show me the install log! You should NOT try running FSX with that DLL until that problem is resolved. But you ran the Installer for 4.40 after you installed 4.50. I need to see the result of the 4.50 installer, not your later attempted install of 4.40.. This is where you are making no sense at all I'm afraid. There is NO installer for PFCFSX. You cannot possibly run it as it doesn't exist. PFCFSX is just a DLL which you copy into the Modules folder. The fact that you got a message stating that you have a later Version of FSUIPC is only ever from the FSUIPC4 installer. You appear to be first running the FSUIPC4 installer for version 4.50 then the FSUIPC4 installer for version 4.40. PLEASE DO NOT DO THIS! There is no program which installs PFCFSX.DLL for you. If there's a copy of PFCFSX.DLL there you must have moved it there yourself. I repeat: THERE IS NO PFCFSX INSTALLER!!! Please go back and run the installer for FSUIPC4 version 4.50. Then install PFCFSX.DLL manually, as it says in the user guide. Just copy it into the modules folder as instructed. No I did not! I asked for the Installer log -- please do read what I write. you did actually provide the installer log as I asked in any case, but foorgot the normal FSUIPC4.LOG, the normal run-time log which is the one showing what FSUIPC4 is actually doing. Once I know you know what you are doing, which doesn't appear to be the case at present I'm afraid, we can proceed to looking at whatever the problem you have is. Until then it is rather pointless I'm afraid. So, step by step: 1. Install FSUIPC 4.50 by running the 4.50 version of the FSUIPC4 installer. 2. Do NOT run any other program yet!!! 3. Install PFCFSX from the ZIP by copying across the DLL into the FSX modules folder. 4. NOW run FSX. Do NOT run the FSUIPC 4.40 installer again as you have been! If you still get a problem, please assure me you are not running some other installer which I don't provide, and show me the two logs I asked for -- the FSUIPC Install log and the normal run-time FSUIPC4.LOG. I am not interested in your PFCFSX INI or PFCFSX.LOG files, they are not relevant. Pete

Well, nice for me, but why buy it again when you already bought it? Just download and install the current release! Pete

Good, glad you got it sorted! Pete