Pete Dowson

Make sure you are using the latest FSUIPC3 (3.998q), then, after you get the error, go to the Windows error log and retrieve the details. (Right click "My computer", select "Manage" then System Tools-Event Viewer. The error will probably be in the Application section. Get the mofule name (DLL) in which the error occurred, and the address and error codes. Also, see what Air Hauler was doing last in FSUIPC by using the ipc Write logging, as alaxus suggested. Regards Pete

By "WideServer" in this list I assume you just mean it's enabled in FSUIPC4? You don't need WideServer.DLL at all. Those should just be =Yes. The application name isn't relevant by then. Is WideClient still running on those? It might simply be that because you have the Close parameters wrong, the activity of the PM applications is stopping WideClient closing, or it is closing and leaving the applications running which stop Windows closing. It is possible, I guess, though WideServer does delay the server shutdown a while to ensure the signals do arrive at all clients. Check the client wideClient logs to see if it was received. Have you tried the Broadcast mode facilities available wiith the latest versions of FSUIPC4 and WideClient? It only sends one copy of everything rather than separate copies to each PC, so may resolve the problem by being faster. I don't use the PM shutdown facility, but the WideServer shutdown hotkey. That certainly gives things time. But to be sure, I don't have FSX shutting down , only the clients, and then shut down FSX separately. But I do all this because I'm usually wanting to analyse or change stuff on the Server. Regards Pete

Yes, you can use Lua to send any FS or FSUIPC control plus parameter (excepting the Offset controls, where there's no need because the Lua ipc library handles offsets directly). Just use the ipc.control function with the KeySend control number (1006, as listed in the FSUIPC advanced users manual) and the KeySend number, 1-255. Or of course you can simply assign all of the KeySends to the one button by editing the FSUIPC INI file. This method would actually be faster and easier to set up. Regards Pete

I'm not sure what you want to do with that offset, so I don't know which FSUIPC command you need to use (set, setbits, clearbits, togglebits, or one of the inc/dec ones), but 2 bytes = 16 bits = "word". (one byte = 8 bits = "byte", 4 bytes = 32 bits = "double word " or "dword" for short). Pete

Thank you. Please send to petedowson@btconnect.com. Regards Pete

If there is no Modules folder, than you have not installed FSUIPC4. Please look inside the FSUIPC4.ZIP file. You will find a short document about Installing and Registering FSUIPC. Please read that. It tells you what gets installed and where everything will be after installation. Pete

I would think that with only two keys, A and B, won't both directions be indistinguishable or does the input always stop on a B going one way and A going the other? If, like most rotaries, you can't control the stopping position, the sequence wither way could be A B A B A or B A B A B ... If it is always going to be A B one way and B A the other, then, yes, you could use flags. If these were button inputs it could be done easily with button flags, but FSUIPC provides no such programming facilities in the INI for button presses. Yes, assuming you do have identifiable sequences, it should be possible via Lua. Use the event.key function to let a function receive they keypresses and send the appropriate controls or whatever. Regards Pete

The error message is not one from FSUIPC but presumably from PlanG -- your subject title is misleading. If it worked okay before you entered the registration, but not after, then there are three possible reasons: 1. You are, in fact, using an out of date FSUIPC, one possibly installed incorrectly by an add-on and overwriting your 3.99 version. Check the version actually in use by going to the FSUIPC options, or looking at the Log or DLL properties. OR 2. The date of your computer is incorrect and is actually BEFORE the date of your registration, making it look invalid, OR 3. The registration itself is actually a fake one, made by a pirate key generator. Please also try using the very latest update, from the Download Links subforum here (3.998q). This gets around some nasty additional traps Microsoft added recently to its Windows security measures. Regards Pete

What is the context please? FS9 or FSX or some other? Why using offsets not controls or axes? Do you want to be able to calibrate, and have tiller/rudder control transfer as speed increases? Pete

Three points on this: 1. There's a later update which I'd like you to try first -- 4.754 -- available in the Download Links subforum here. There are usually updates there. 2. The InitDelay is in seconds, with a maximum of 120, so that attempt to change things wouldn't have worked in any case. 3. Crashes and hangs at the point you describe are most usually due to clashes with other add-ons and removing or changing or updating the other will also avoid the problem. One frequent cause is an outdated version of actigate.dll, but also one version of fscopilot.dll caused similar problems. So please make a lit of such add-ons, or show me the DLL.XML and EXE.XML files so I can see what else there is. The wrong versions being quotes after you installed SP2 are suspicious of a corrupt FSX installation. I assume you did install SP1 first? I can't really advise further till I see the Install and FSUIPC logs. You can paste them into a message here. don't try attaching them. Regards Pete

No, the code should be the same internally for these actions. I will investigate, but please first confirm you are using the latest interim versions (3.998q and 4.754), and then enable Button logging and show me the logs for both. (add LogButtonsKeys=Yes to the [General] section of the INI file before starting FS). Regards Pete

Did you try doing what I suggested with the DLL.XML? Please see my last reply. So where do these things come from? RXPG1AE.EXE - system error The program can't start because cdp_annun_box_sim.dll is missing from your computer. Try reinstalling the program to fix this problem. How is that EXE getting to run, and why can't it find that DLL? I really can't help you solve that one -- only the person responsible for the error message will be able to say what is going on there. Regards Pete

What do you mean "some of the most essential files don't show up"? What files, and where are they supposed to "show up"? Can you be a little more clear please in explaining your problem? Regards Pete

FS does not re-scan devices after it has initialised, so if joysticks are not connected at load time, or disconnected and reconnected later, they cannot be used again (with FSX assignment) until you restart FS. With FSUIPC assignment, late connected or re-connected devices will work again if you visit the Axes tab in FSUIPC options -- it rescans each time you do this. You don't need to make changes, just call up the tab and ok or cancel out. Regards Pete

Do you mean no crosswind component at all, that your surface winds always line up exactly with the runway you choose no matter which one? If so something must be deliberately programming that effect! Regards Pete

Nevertheless, unless there is a hardware fault causing button presses or other axis inputs to occur when moving the tiller axis, there must be something else assigned to that axis. Show me the [Axes] section of the FSUIPC INI file. You could also use FSUIPC's logging facilities to see what is going on. Enable both Event and Axis Event logging, then move the sterring tiller to obtain the diff brakes message. check the Log to see what was sent. Yes, it could well be so. Is is aircraft specific? Try it on a default aircraft. Regards Pete

That was corrected several releases back and is certainly okay in the current interim version 4.754 released on the 21st December. Regards Pete

No. Lua scripts can do almost anything. Whether they access offsets or press buttons or send keystrokes is only determined by the code therein. Very few add-on aircraft use FSUIPC these days, especially on FSX. The offsets normally available in FSUIPC apply to FS internals, not add-on internals. Most add-on features have to be accessed via keystrokes or local panel variables ("L:Vars"), though sometimes, if the gauges are written in C/C++, mouse macros work. Regards Pete

If RC4 is crashing there's no change I know of in any version of FSUIPC which will stop it. you need to supply a Log to JD and he will solve it. All interim updates for FSUIPC are provided in the Download Links subforum. Look above, at the top of this forum and you will see it. There are all sorts of other helpful things there too, always worth a browse. This is the only "website" I have. it sounds like you are referting to the Schiratti site. He hosts my main releases. I can't update that so often. Yes, as also seen in the download Links subforum. Regards Pete

I don't know "decoda". There's the LuaDebug option in FSUIPC which gives you a trace by line numbers, but which can probably be improved -- the Lua source is included. But I mainly rely on simple logging -- adding ipc.log lines in salient places to tell me where the code is going and what the important values are.getting set to. Simple syntax errors are logged in any case, as I said. [LATER] I juist googled "decoda" and see it is payware, with quite a hefty fee for commercial use! The reason it doesn't work with FSUIPC is because it needs to hook into the Lua functions compiled into FSUIPC, which it cannot do without a lot more assistance. i read quite a bit through what it offers and I really don't feel it justifies the effort nor the price. Regards Pete

Actually, I may not need to. I thought of a very simple way to do this sort of thing, very flexibly. First, make sure your FSUIPC installation is up to date -- latest versions are supplied in the Download Links subforum. Then save the following as, say, "multiaxis.lua" in your FS Modules folder: function applyaxis(val) cntrl = ipc.readUD(0x66c0) ipc.control(cntrl,val) end event.param("applyaxis") [/CODE] and edit the FSUIPC INI file, adding this section: [b][Auto][/b] [b]1=Lua multiaxis[/b] (if you already have an [Auto] section, add the line with the next available number). Now run FS. Go to FSUIPC axis assignments and assign the axis you want to switch as an "FS control", choosing this one from the drop-down list: [b]Luavalue multiaxis[/b] Then go to the Buttons assignments and assign the buttons you want to use for selecting the axis use, on the right-hand side, as follows: [b]Offset dword set,[/b] with [i]Offset[/i][b]x66c0 [/b]and the [i]Parameter[/i] set to the value of the FS or FSUIPC control you want the axis to send. The controls are listed in a List installed in your FSUIPC Documents folder, in the Modules folder. You can use any control, but obviously only axis controls make much sense. Those are all either named [b]"Axis ..."[/b] or end in "[b]set[/b]". There are more controls, added by FSUIPC, and listed in the FSUIPC Advanced User's guide. [b]BUT[/b] the ones you really want, for the purposes you chose, are currently only published in the "Changes" document included with the recent FSUIPC updates (see Download Links). They are numbered [b]64101 to 64144,[/b] and the ones you want are: [b]64136 steering tiller[/b] [b]64123 flaps[/b] [b]64122 spoilers/speed brakes[/b] Once you've done all this, exit to FS, select a mode using the buttons/switches you assigned above, then go into FSUIPC joystick calibrations and calibrate the axis for that selection. You'll need to exit to change the mode to calibrate each separately -- FSUIPC doesn't obey the button presses when in the options (for pretty obvious reasons). Note that this technique is extensible for any number of different uses for the same axis and, by using different offsets (66C4 is the next -- the range 66C0 to 66FF is free for users, giving 16 possible DWORDs to use) and renamed versions of "multiaxis.lua", can be applied to any and all axes. I've tested all this with FSUIPC [b]4.754[/b] and FSX. Have fun! Regards Pete

Okay, then it should be easy enough with a plug-in. I can help but not till I return. Sorry, I don't use and am not involved with Linda, and do not have a copy of the documentation. I think they provide support via a website? I don't realy know if its handles axes, it might only be button programming. Regards Pete

Is the mode selector visible in FSUIPC's Buttons & Switches assignments tab? If it is then it would be reasonably easy to program what you want as a Lua plug-in. If not it might get a little more complex, using the USB HID programming facilities in the Lua com library just to determine the position of the mode switch. Have you checked whether something like LINDA can help with this? (See sticky thread above). Otherwise I can help (assuming the mode selector IS accessible one way or another), but not until I return from Christmas/New Year holiday on January 6th, 2012. I leave this Thursday morning. Regards Pete

Yes, I use a couple of Leo Bodnar cards in my cockpit. Very easy to use and automatically providing assignable and calibratable inputs via standard joystick methods. Regards Pete

I've just withdrawn it. I'll upload another in a few minutes. Please destroy that one, else I'll have ot increment the version number again. The FS98 compatible values for wind turbulence in FSUIPC1,2 and 3 was 0, 64, 128, 192, 224 and 255 -- 6 values. Because FSX only had 5 I tried to apply those to get the same sort of 'feel' as in FS2002 and before, so used 0, 64, 128, 192 and 255., just missing out the 224. However, I just realised i'm multiplying by 64 but not checking for > 255, so I've had to fix that -- many programs will assume it fits in a byte (though documented as 2). So, the "proper" version 4.754 will give *64 but limited to a max of 255. Pete