Pete Dowson

If by "local variables" he means "L:Vars", then, yes, FSUIPC can read them via macros and write to them via Lua plug-ins. Well, if you can't get anywhere I'll have a look, but i don't have much time available for such things. For a recent example of someone writing to an L:var see the thread entitled How to assign a variable to an offset Regards Pete

Version 3.93 is very old and completely unsupportable. The earliest supported version is 3.98. I expect this is because the signature on that old version of FSUIPC expired. Right click on the DLL and look in Properties-Digital Signature. Again, without seeing the log, it may be a very out of date version of FSUIPC. Oldest supported version for FSX is 4.60. I think only Internet Explorer provides access to the Trusted and Untrusted Publisher lists, but I'm not sure. Certainly IE is available to you even if it isn't your default browser. Regards Pete

You are telling the event.offset function that your function for processing offset 66C0 is called "L:FT_Ignitionswitch", but it is in actual fact called "IgnitionSwitch" as you can see just above. You can also simplify your code considerably. The value of the offset is provided in the function as parameter 'val' so you can use that directly, instead of reading it again. Additionally, since it is the value you want to write you can write it directly. So: -- Ignition Switch function IgnitionSwitch(offset, val) ipc.writeLvar("L:FT_IgnitionSwitch", val) end event.offset(0x66C0, "UD", "IgnitionSwitch") Regards Pete

Reverse is engaged when the throttle values are negative, not just -4096 which is the maximum reverse JOYSTICK input value. Different aircraft have different reverse thrust limits, defined in their Aircraft.CFG files, so it could be any negative number for full reverse -- and any negative number is some degree of reverse thrust. 088C is the current Engine 1 throttle setting. 0B00 only tells you what the maximum reverse value is for the current aircraft. It is a fixed value for that aircraft and will only be fixed at -4096 if that's the value defined in the Aircraft.CFG file. If all aircraft had -4096 as max reverse, by definition, then it would actually be a waste of an offset telling you that, would it not? Be sure to treat the 16-bit WORD you are reading as signed, otherwise it will look like a very large positive number instead. Regards Pete

If you want to do this in FSUIPC, why is your thread entitled "closing programs in WideServer ..."? I don't understand how you found out how to run programs without also seeing the options listed too. Please refer to the chapter in the FSUIPC4 Advanced Users document entitled Programs: facilities to load and run additional programs which is where you will find the [Programs] section of the INI file fully documented, including a list of option keywords wth two methods of closing programs described! Pete

What are those "internal variables"? Do you mean "L:Vars"? If so, then you can read them and test them via FSUIPC macros but only write them via Lua plug-ins. To use an offsert you'd need a Lua plug-in running which is triggered by a change in your user offset (one of 66C0-66FF), via the "event.offset" function, to send the value to the L:Var via the "ipc.writeLvar" function. Regards Pete

That simply means that the "sound" library isn't defined (i.e. it is "nil"). I think you must be using a version of FSUIPC before the "sound" library was added. If you look at the headings of the Lua library documents you are referring to, don't you see an FSUIPC version number? Try the interim FSUIPC update available in the Download Links subforum. Regards Pete

If you mean FS controls for the FS2004 GPS, I don't think there are any. Or at least none that work properly. You will probably have to either program your own GPS as well, or find a way to use the correct keypresses. Check out "Key2Mouse" for a program which does mouse clicking for you. Regards Pete

What message? You never said there was any error message. I am finding it very difficult to help you without information. When you say you "did download the new one", which "new one" are you talking about? The install log you pasted shows: which is the earliest supported version in any case, not the 4.638 version I pointed you to and asked you to try! Furthermore, the same install log shows: so your previous attempts were with a VERY old version indeed (July 2008)! Where did you get that? What do you expect to show? Sorry, you need to explain yourself more. I'm not getting enough information to help at all. Is there an FSUIPC4 Log file in the FSX modules folder? If so, show it to me, please. And what is that you appended after the Install log? It looks like an FSUIPC4.INI file -- a rather old one I think. Maybe also from 4.30? Best you delete that I think. If there is no FSUIPC4.LOG file then FSUIPC4 has never been loaded and run. In that case you probably have a faulty DLL.XML file -- which is one reason I asked you to try 4.638 (it fixes bad DLL.XML files in ways which the earlier installer didn't). So: 1. Please state what this "message" is you say you now get. 2. Please state what you mean by "Fssuipc is installed correctly but nothing shows it.". 3. Please check to see if there's an FSUIPC4.LOG file. If so show it to me. 4. Please do try 4.638 as I've asked you before. 5. If all else fails I need to see the DLL.XML file. You can find that in "C:\Users\Frans\AppData\Roaming\Microsoft\FSX ". Why not? What stops it? It sounds like you have a bad FSX install altogether! Did you run FSX before installing SP1, to make sure it was okay first? Folks say you need to run FSX between each stage. Regards Pete

Unfortunately, because you started a new log (why?), I cannot see the name of the aircraft loaded, but: UI see you have: Does it REALLY start with "D75N1"? Or is that just a substring within the name? If it is then you need to change ShortAircraftNameOk=Yes to ShortAircraftNameOk=substring which is recommended in any case. No. Keys are those things on your keyboard, not buttons. There are no button presses in this log fragment, or you didn't have that logging enabled. Regards Pete

What controls are you using for the lights? Don't they work with the normal FS-assigned shortcuts? If there are light switches on the panel for the aircraft, try enabling Event logging in FSUIPC, then operating those switches with the mouse and see the Log to find out whether any even was used to operate them. If so, those'll be the ones you need to assign. Regards Pete

That looks better. The elevator is a bit off-center -- maybe the pot has turned in its mounting -- but if it works smoothly enough both ways that shouldn't matter. Regards Pete

For that you could try simply reading the fuel levels and re-writing them if they change by any unreasonable amount between two reads. You can do that from an application program or even more efficiently with a Lua plug-in. Regards Pete

Correct. There's no way the system will allow a different name for the two parts. I did change it to accept the more common problem, that of a different email address, as folks change their email reasonably often. But name changing, no. There has to be a limit on how users are identified. And it is a far more flexible system, tying it to a person, than limiting it to a specific PC only and having to have new registrations for upgrades and so on. You'll have to fill in a problem ticket at SimMarket and see if they will re-issue you a registration with the same name as you used before. Pete

Not via FSUIPC, no, not at present. I'll certainly look again to see if I can re-introduce the facilities in FSUIPC4, as far as possible compatible with those in FSUIPC3. But I seem to remember that it isn't easy. FSX doesn't appear to use the standard Windows menu systems which I intercepted in previous versions. I'd have to dig into it a bit. [LATER] Ugh! I looked and remembered then exactly why I removed the stuff in FSUIPC4. All of the Menu stuff in FSX is handled through a construct called "IME" (Input Method Editor), and I just can't get into it to intercept anything, let alone change what it displays. Sorry. I remember now, I spent a week on this originally, working all hours, and got no where. I don't want to re-visit that I'm afraid. Regards Pete

I know, that is precisely why I suggested that you paste the text into a message instead. Did you miss my last reply? I also suggested trying the 4.638 installer. Did you do that? Pete

No. FSUIPC4 and WideFS7 have been sold in exactly the same way since release, as has FSUIPC3 and WideFS6. And FSUIPC4/WideFS7 have only been available, of course, since the release of FSX in late 2006. Perhaps you changed your email address since then and they are registered with a different one? Didn't you back-up your FSUIPC4.KEY file as advised? Regards Pete

They are text files. Just paste them into your message and that'll be fine. You can also, for tidiness, enclose them in "code" quotes -- the button looking like <> just above the edit area here (one before the right-most). Meanwhile, there is a later Install package (for 4.638) available in the Download Links subforum. You could try that too. Pete

You are lucky I eventually spotted this message. You should use a new thread, not append to one of a completely different subject. What gives you that message? I don't recognise it. What does "after installation wide fs got registered" mean? How did it get registered? Older versions are not supported. For FS2004 you should be using 3.98 or later. For FSX you should use 4.60 or later. It sounds like you are trying to use FSUIPC3 keys for FSUIPC4, or WideFS6 keys for WideFS7. You cannot! Regards Pete

Well, the first shows pretty much uncalibrated default values. I'm surprised you've not calibrated properly and allowed some dead space at either extreme. And the default centre values are seldom correct for any axis. I assume you've merely set the extremes again? not allowed a little dead space to account for variations as recommended? You don't say where you've assigned these. If in FSX then its "sensitivity" slider will change the range FSUIPC sees. It needs to be on max. If it is, or you are assigning via FSUIPC, then all I think is happening is that you didn't re-calibrate in Windows "game controllers" after updating windows. It probably reset them, maybe even changed the drivers being used. Are they CH ones or Windows defaults? Regards Pete

External data transfers are dealt with properly already. The only problem was with your Lua plug-in, because their offset requests aren't "held off" like those from external applications. I don't want to delay the start of applications unnecessarily because many take a while to initialise, unlike Lua plug-ins. It works fine as it is. Regards Pete

Okay, but you've not registered it and used it to assign or calibrate your controls? If you haven't, then it isn't involved. If you have then it sounds liker you've made a mistake, or maybe assigned the controls then moved / reconnected the USBs, which will change the IDs. If you have multiple connections it is best to use the joystick lettering facilities in FSUIPC -- there's a chapter about it in the user guide. Then FSUIPC can track them when they move connections. Regards Pete

Merely installing FSUIPC will do nothing. An unregistered install of FSUIPC does nothing apart from supplying an interface into FS for application programs. A registered install of FSUIPC doe nothing to or for joystick device connections unless you ask it to. Whenever coming here for support please always state the precise version number of FSUIPC you are using. If this is older than the earliest supported version (currently 4.60 for FSX) please update first. Regards Pete

Version 4.57 is well out of date. The earliest version supported for FSX is 4.60. Please update if you want support. Apart from 4.60, which was released nearly a year ago, there are much later updates available in the Download Links subforum here. Regards Pete

What's wrong with going to FSUIPC's Buttons & Switches tab and assigning F2 to that button on the left-hand section? Or, more efficiently, if it is "throttle decr" you want it to do (the default FS assignments for F2) use the right-hand side and assign directly to "throttle decr". Of course it can. Look in the FSUIPC Documents folder, in your FS Modules folder, and find the Buttons section in the User Guide. In general, though, you only really want to assign buttons to keypresses when the keypress is being used as an extra control by an add-on. All of the default FS-assigned keypresses are simply assigned in FS itself to send FS controls, so why not assign the button to the FS controls in the first place? It is obviously going to be more efficient to send the control that send a keypress which FS has to look up to find out what control to send! Er, there aren't many keys FSUIPC can't set, and none of the F-keys are among them! Sounds like either your keyboard is broken or something else you are running is stealing the keypress before FSUIPC can see it? Anyway, it is best to use the control for what you want to do, not the keypress. Regards Pete