Pete Dowson

Not sure what you mean, sorry. As an installer it doesn't normally need the "run as administrator" trick, but it depends on how you are logged in, and I've noticed, from reports, that some recent Windows security updates have messed things up a little. But the installer should advise you if you need to use that. Right. I'm not there yet ... Since installing/reinstalling only puts the DLL and documentation in place, deleting it and reinstalling it makes no difference whatsoever. If FS works okay without your FSUIPC INI data, or without a joystick driver enabled, then there is something about the joystick driver which is causing the hang when it is being polled. Do you mean keyboard keys, nothing to do with joysticks? There's really no change in the way joysticks are polled between 3.98 and 3.99. You can simply paste any text files into your message. Use the "code" quotes to enclose them (the <> button above) as this makes it easier to distinguish files from text. No, not yet. Can you calrify answers to my original questions, please? i.e. these: 1. Just opening the dialogue and closing it causes FS9 to freeze? 2. Does it do the same in both full screen and Windowed modes? Try both please. 3. Are you saying that FS9 doesn't even work with FSUIPC installed? That it isn't just a dialogue transition problem? FS9 freezes anyway, regardless of dialogue access? I need to know exactly WHAT action on your part causes a freeze. We have to narrow in on the problem. A couple of things also to try: first add PollEpicButtons=No to the [buttons] section of the INI. See if that makes any difference. Then, one way of telling whether it's a joystick driver problem is to set this in the [buttons] section: PollInterval=0 That will stop it polling joystick buttons altogether. If this "fixes" it then one of your joystick drivers is hanging. It may be one you have installed which isn't even being used, an old one. Regards Pete

Sorry, I've no idea about "PlaySound", and do not recognise that L"...." structure. What's the L for? Maybe PlaySound needs exclusive access to the sound device and cannot get it because FS has it too? Didn't you check for an error return, or GetLastError? Surely that's the first step to working out what is wrong? Sorry, I don't know. I added sound facilities into the Lua plug-in libraries in FSUIPC and WideClient and I used DirectSound for that, but I did that because I wanted to offer sound card selection and sound positioning in stereo and 5.1 sound systems. I've really no idea how to make sounds in any simpler way. The code I used was a re-use of similar stuff i did many years ago for an FS Module called "esound.dll". You can play sounds through those added facilities in FSUIPC, by interfacing to FSUIPC and using the offsets for that facility. see the "FSUIPC SOUND INTERFACE" section of the latest FSUIPC for Programmers document. Of course if you used FSUIPC you'd be dependent upon users installing that too. Regards Pete

Such symptoms are almost always due to multiple assignment. Check that the relevant joystick controller is truly disabled in FS if you are only assigning in FSUIPC. You can always use FSUIPC's logging to see what is happening too. Check the axis logging option. Again, in order to determine which control is which, just enable event logging in FSUIPC, then operate the control via the keyboard and lok in the log to see which one did it. I assume you normally use the A or S keys. I always get mixed up between them, but one will probably be View mode and the other View type. Regards Pete

Just opening the dialogue and closing it causes FS9 to freeze? Wow, that's a new one! I've never heard of any such problem as that. The dialogue is a standard Windows one. FSUIPC realy hasn't got much say in its activation and closing. Does it do the same in both full screen and Windowed modes? Try both please. Sorry, are you now saying that FS9 doesn't even work with FSUIPC installed? That it isn't just a dialogue transition problem? FS9 freezes anyway, regardless of dialogue access? Please clarify exactly what the symptoms are and we'll go from there. I could also do with knowing what your previous version of FSUIPC was, because really nothing much has changed in any general areas like dialogue actions and so on. the changes have all been bug fixing and additional user facilities which don't come into it until you use them. Please also list what other add-in modules you have installed. One or two are well known to have conflicts with FSUIPC, at least in their older versions. Actigate.dll, for example, was one such. Regards Pete

That's fine, but version 4.26 is years old and I cannot support old versions. Please update to the current version (4.70). You don't lose any settings, it just gives you an updated module and documentation, plus many new facilities and fixes. I know that with FSX Microsoft added a steering control, but I've never tried it so I don't know if it actually operates the nose wheel on aircraft. I wouldn't really be looking at the outside when trying to taxi in any case. I've always assigned my tiller to the "steering tiller" control in FSUIPC (using "direct to FSUIPC ..."), which really is just another rudder control, but one which you can calibrate differently, so to give possibly more control. When both the tiler and the rudder are assigned and calibrated "direct to FSUIPC calibration", FSUIPC balances the actual rudder control between the two -- whilst on the ground with an airspeed of less than 60 knots (adjustable by parameters) the control is gradually transferred from one to the other. I assume that for FSX's own tiller you assign to the "Steering Set" control, but you'd need to calibrate this in the Windows game controllers, not in FSUIPC, as it doesn't include coverage for that axis. The "steering tiller" calibration in FSUIPC is for its own steering till axis just mentioned. Where are you finding a problem? Regards Pete

Aha! So you DO really want to use the FS controls for trim up and down. In that case just write the appropriate control values to offset 3110, the one i referred you to. You can use that for any FS control (and most FSUIPC added controls). You can find the control values in the controls list installed in your FSUIPC documents folder. BTW i still don't understand what "3370 series" is. I did Google it, but only came up with something about "Fiberlink 3370 3G/HD/SD-SDI & Data Series (3370 Fiber Optic Transmitter)". Regards Pete

Good. It is using a sequence of Autobrake Decrements and Increments to get to the correct position. Thanks for posting this follow up. Regards Pete

As Ian says, if it is not a standard joystick or other USB device which Windows handles (like keyboards, mice, and external storage devices) then it needs its own driver, which Saitek should have provided. Whether Saitek also provide tools for controlling it differently I don't know. If you are into programming you could use the HID facilities in the Lua com library to write a plug-in to handle it. But first you'd need to hack into the protocol using something like the Aggsoft Advanced USB port monitor (http://www.aggsoft.com). Regards Pete

Hmm. not seen those before. Depending on how many L:Vars there are it can take some time. The Lua plug-in runs in the background and has to first catalog all of those it can find before reading their current values. You are also right in surmising that if there are no L:Vars associated with the current aircraft that there will be nothing shown on the screen. That's a control built into FSUIPC and log s to the FSUIPC log. It doesn't display anything on screen. No idea, sorry. Regards Pete

Why don't you want to use the FS controls for it? Generally trim is not controlled by buttons, but by a trim wheel. Some aircraft have electric trim also using buttons on the yoke. What is it you wish to do, use a trim axis (like a wheel), or two buttons? There are, of course, offsets listed which reflect the current elevator trim value, and which can by written to with a different value to change it. You can find those easily enough by searching the offsets list for "trim" (you'll also find aileron and rudder trim of course). If you merely want to send the FS trm up and trim down controls from a program you would send those controls via offset 3110, which accommodates any controls along with an optional parameter (though those particular controls take none). There's nothing to indicate a button up or down other than reading the button states, as FSUIPC does. If you want to test joystick buttons from your own program you would use either the "joyGetPosEx" Windows API, or the more modern DirectInput interface, which is a bit complicated. If FSUIPC is scanning the joystick in any case (because you have made some button assignments for it) then there are offsets in which you can read the button states. But why do you want to do this? If I understood what you are trying to achieve maybe I could provide more explicit help. What's "3370 series"? Sorry, you've lost me there. Regards Pete

Can you tell me where you are reading this example? It isn't something I recognise. Maybe I forgot? A pointer woudl be useful please. What exactly did you assign to F5 and F6, and why two assignments? Did you try the directly assignable FSUIPC control for logging L:Vars as described in the L:Vars section of the FSUIPC Advanced Users guide? Well that log shows the Lua plug-in being loaded and terminated forcibly (presumably by a "Luakill"?) before it gets the chance to do anything. Well, maybe, but let it run. If there's a lot of L:Vars it may take it a few seconds to read them all initially. You've terminated it in less than 5 seconds after it started. Regards Pete

Grumpy? Who's grumpy? That's one of the seven Dwarves, not I! ;-) I think you must be reading my words the wrong way! I looked back and noticed a smiley was missing where I thought I'd put it. (corrected now). Is that why you thought I was attacking you? I do wish folks would lighten up sometimes. This is supposed to be fun, a hobby. Pete

Sorry, I can't really help. I've never used any of the SDK stuff, and I think VS Express is a lot different from VS Professional which I use. However, whenever I have built a project and received a list of errors I've found the error messages quite useful, and just get to work eradicating each problem in turn till there's none left. Sometimes it's a matter of getting the build properties right, or the includes and LIB references. It's part of programming life I'm afraid. My biggest headaches seem to come when upgrading from one version of VS to the next. VS2003 to VS2005 to VS2008 to VS2010. Each one has caused reams of errors to appear in projects which previously compiled with no errors. It's a matter of working out why, for each, and fixing it. No, for three reasons 1. I've never actually written a gauge. I worked out my code by hacking and disassembling FS modules. I only found later that gauges were so similar. 2. I don't use C++, only C and ASM. I prefer ASM really, but C is acceptable. I don't like getting too far away from the machine level. I grew up as an engineering test programmer on mainframes. 3. Any example i could possibly find will fail on every compiling system except the one it was built for. Maybe it only needs a few tweaks to make it work, but it will still fail initially. It doesn't really look like you've got many problems to solve according to that picture. Most look to be due to it seemingly not recognizing that "GAUGE_NAME" has been defined. I don't understand why though. Sorry. Well, I suppose it would be the one Microsoft used to develop the SDK stuff. Does it say anywhere? But you should be able to adjust things for any IDE, or at least any Microsoft one. Regards Pete

I told you persistence pays in this problem. It's purely a timing thing. And once it works it continues to because by then the "trust" entry has been made in the FSX CFG file. Well, don't come here asking any more questions about FSUIPC, then. ;-) You just deleted where to go to get answers! What's the point of doing that? :rolleyes: As far as the FSX system is concerned, the ONLY part of what is installed by the FSUIPC4 installer which is being used is the FSUIPC4.DLL module itself. The rest is only for your use. So deleting the reference documentation is just your loss. I would strongly advise you to re-run the FSUIPC4 Installer. It won't take you back to an older version, but it will restore the documentation that you may one day need. Apart from that I am pleased you got past the problem. Regards Pete

There aren't any. It's handled locally in the gauge. You could see if a mouse macro would work. I don't recall off-hand whether it would or not. Note that in order to ascertain if an FS control is useful with switches like that, you simply need to enable Event logging in FSUIPC, then operate the switch and check the log to see if a control was sent. Regards Pete

I expect it is either not a joystick device (according to Windows), or is assigning to button numbers beyond the 32 that FSUIPC can see. Sorry, but I'm not sure how I'm supposed to know. I don't have such a device and I've certainly got no relationship with Saitek at all. But I thought you just said it couldn't. Can Flight Sim see the buttons? No. FSUIPC has no display facilities whatsoever except in the Lua library for GoFlight devices. Sorry, i don't know the device at all. This is a question for Saitek I believe. Regards Pete

As I feared, I suspect that's because the Lua program you are calling looks to be quite long and has to be loaded, compiled and executed for each line in the INI. A shorter one with just the entries you want might do the job, but I doubt it. In the end the only sane way would be to program the sequences themselves properly in a Lua plug-in. Maybe an appeal to the original Lua programmer for the one you are using might elicit results. I'm sorry, but I'm giving up now. I don't want to be accused of maltreating you again as is bound to happen with your way of not reading my answers, so it's a sorry good bye from me, and good luck. Pete

I assume you mean a "current heading hold"? Which aircraft do you want this for. It isn't a feature on Boeings as far as I know. You always set the heading bug before pressing the heading button. If it isn't actually implemented in the aircraft of your choice you've need to have a little Lua program which read the heading offset, converted it from FS units to an integer, and wrote it to the AP heading bug offset, then enabled the heading hold. In some aircraft merely enaging the A/P holds wings level, so that acts as a sort of current heading hold, though it wouldn't correct it if it got blown about. The "CWS" ("control wheel steering") facility on some aircraft (Boeing airliners included) would also do it because that holds heading and altitude manually set using the control column. There are controls for the wing leveller, so you could try that. There are actually two distinct heading hold controls in FS -- "AP Hdg Hold ..." and "AP panel heading ...". Now I seem to remember that these used to perform the two different functions -- the former merely held the current heading and the latter held the bug heading. I don't know how many versions of FS ago this was, but I see in FSX they do the same thing. I don't know about FS9. Regards Pete

Yes, exactly what i said and why I didn't! I don't know why you are re-stating the obvious? Pete

Not a "dumb" but someone who evidently hasn't the patience to read all of the words and instead just ploughs ahead regardless. I know. I pointed out that, though Andy posted macros for you, you thought they were INI file lines. I explained things to you, I enumerated solutions, and you simply ignored half of what i said. Patience has limits. I'm simply not going to continue repeating and expanding on things if you can't be bothered to use a little more time and effort, and read things properly. I thought, as I said, that this must be down to lack of English, but from your latest tirade this is evidently not the correct diagnosis. :-( I'm sorry, but I'm not responding any more in this thread. It has taken enough hours of my life without any reward for either of us as it is. My 'corrected' lines from Andy's post, included in one of my replies, should make it work for you. If not, please seek help elsewhere. Pete

Two points there: 1. I cannot possibly support version 4.20, it is years out of date! If you want or need FSUIPC4 installed then you MUST update to 4.70 or later. 2. There is absolutely no way FSUIPC is needed to view other planes on-line as there are no facilities whatsoever in FSUIPC to provide this capability. Your on-line application MUST be using SimConnect for that. There is nothing FSUIPC can or will do unless you or a program asks it to. It is simply an interface. It does nothing at all by itself. No. I've seen reports of bouncing planes but they always seem to come down to a discrepancy between airport ground levels. Maybe your IVAO program wants you at a different altitude? Please contact IVAO support. Tell them, to start with, that they should certainly NOT be installing such an old FSUIPC version as 4.20. Also ask them what they use FSUIPC for, as I cannot imagine why they install it. SquawkBox and FSInn, the other major on-line flying programs certainly do not. they use FSUIPC3 on FS9, but SimConnect on FSX. Regards Pete

I wrote FSUIPC but I don't know anything about it "coming with IVAO". No. FSUIPC4 does nothing unless you ask it to, and if you haven't paid for a Registration and set up parameters in it to make it do something, it does nothing. It is just an interface into FS for other programs to use. Please be aware that, in any case, I cannot support any old versions of FSUIPC4. I don't know what version you are using, but the earliest supported version for FSX is 4.70. If your copy of FSUIPC4 is being installed by some other program it is likely that it is completely out of date, so do please check. Additionally, as far as I am aware, IVAO is an organisation, like VATSIM, for on-line flying. It isn't a program, so it won't be installing anything. I *think* the program they use is called IVAP (but i'm not sure), and, as far as I can determine, that program, for FSX, uses SimConnect to talk to FS, not FSUIPC4 at all. In fact FSUIPC4 cannot be used for any form of multiplayer, and I assume you need some multiplayer capable program in order to see other fliers. So all in all I think there's something strangely amiss in what you are installing. Shouldn't you check with IVAO or IVAP support? Regards Pete

Yes, but he didn't put your macro code into a Macro file for reference in his INI file, he put your macros into the [buttons.Jets] section of his INI file where they'll be rejected as invalidly formatted lines. Macros go in macro files. I don't think he'd know either way as it isn't his Lua at all, it's one he got from the User Contributions subforum. If I thought he could handle Lua file editing I'd have explained a much more efficient way of accomplishing the whole thing in any case. I was going to follow through with such, as I hinted at right at the start, but since he understands hardly anything I write, or possibly simply doesn't read much of it, it really would be pointless. I hope he can find someone who can speak his language. Regards Pete

The joystick calibration tabs do NOT read any joystick axes at all! They only show the values of the assorted controls in FS itself. If moving your throttle makes the ailerons move then you either have the throttle assigned to the ailerons, in FS itself or in FSUIPC's Axes assignments tab, or your hardware is malfunctioning and you are getting cross-feed from one axis to another. There are really no other possibilities. Regards Pete

Sorry, not knowing anything about the Level-D 767 nor FSConv I can't really help. But test the switches on a default aircraft. All FSUIPC can do is detect the switch operation and allow you to make an assignment. The rest is exactly the same as assignments to any buttons or switches. There are references to good beginners books on the Lua website, which is referenced in the Lua documentation installed in your FSUIPC Documents folder (in the FS Modules folder). I'd recommend the first few chapters of "Programming in Lua" by Roberto Ierusalimschy, published by Lua.org. For application in FSUIPC the main reference for the Libraries added is the document in your FSUIPC documents folder, plus the numerous examples provided there too, and a lot more help in the User Contributions subforum here. Regards Pete