Pete Dowson

Got them, thanks. I'll try to make time to look at it in the next few days. Else it won't be till mid Jan when i get back. Regards Pete

For some reasonn you posted your support quesry to "User Contributions" subforum, where it won't get answered. I've moved it here for you. You always need to quote the VERSION NUMBERS. "Latest" is rather meaningless I'm afraid. The version numbers are very easy to find, they are always visible somewhere -- options, logs, properties, etc. The information needed will be in the WideServer and WideClient log files. that's why they are produced. Regards Pete

I think there is a way of getting into the GPS module from C/C++ as well as from XML. But it is an interface I am not currently familiar with, so it would require some research first. I may be able to look at it next year (I am away till mid-January in any case). It will not be trivial, maybe two or three weeks work, and I'm not really sure it is worth the effort. After all, it has been around for several versions of FS (not just FSX) but yours is the first ever request for it to be supported. Remind me in mid to late January and I'll take a more serious look. Sorry, I don't have time beforehand. BTW I am not going to do any more serious development work on FSUIPC3, only FSUIPC4. So I hope you are talking about FSX or Prepar3D. Regards Pete

The notice you get doesn't mean there's an error, only that the button has two or more assignments. That's allowed. You can have as many as you want. But then they have to be edited directly, in the INI file, because with the options dialogue you wn't be able to control which you change. There was no attachment, but no worries. Just paste it into a reply here. Regards Pete

I've had a preliminary look in preparation for testing. I note from the PDF documenting LuaCOM that each thread running the DLL needs COM initialisation and closure (CoInitialize() and CoUnitialize() APIs) before and after. My code isn't doing this at present. Is it something you've taken care of somehow? Possbly for some reason in FSX it wasn't needed but P3D does differently? Also, I will need to test using the same LuaCOM.dll as you. Are you using the one I linked to at the end of my Lua Plug-Ins doc? I can't see a ready-made DLL there, only the sources which would need making. I found binaries on http://www.tecgraf.p.../~rcerq/luacom/ but which one of these? "Files can be downloaded from the links below, or from LuaForge. Manual, including release information (PDF, zipped HTML) Binary Distribution Package, for use with the LuaBinaries distribution Binary Distribution Package, uses new package proposal (including static libaries and a DLL not compatible with LuaBinaries) Binary Distribution Package, linked with patched IUP 2.2.2 (including static libaries and a DLL not compatible with LuaBinaries) And what is "LuaBinaries"? Maybe you could link me to the one you are using? Regards Pete

There are several ways, at least in C/C++. I'm afraid I don't know VB, but I'm sure it must support Arrays? You only need an array of two integers, with 1070 in the first and the parameter in the second, and use a length of 8 (2 x 4) bytes. Also, you can write 3114 with the parameter, then 3110 with the 1070. Only 3110 acts as the 'trigger'. The real "write" is not done until you do the FSUIPC_Process call in any case. Are you just starting to learn VB? Please do look up arrays. I'm sure they must be supported. But of course you can! WideClient supports Lua too, in fact almost all of the library functions are identical -- a few are omitted as being non-applicable, and others more useful outside of FS are added. Certainly I have plug-ins using 1070, for instance, from clients. Please read the Lua documentation installed in your FSUIPC Documents folder. Regards Pete

Please see the FAQ subforum. Thee's some assistance there -- two threads in fact. You'll see them from the thread titles. Regards Pete

Hmm. Strange. I'm not sure what is going on. I can't imagine why the process being P3D instead of FS would make any difference at all to this, as that just doesn't come into it. You seem to have tried all the sorts of things I would have tried. I'm not sure how I can help really as the code which does this stuff is part of the standard Lua 5.1 interpreter which is bundled into FSUIPC. I really haven't worked through all of its internal complexities. I'll try to test it myself, but I'm not sure when I can at present. If I can't fit it in before Wednesday next then I'm afraid it's not going to be till mid-January, as I'm away for a while. Regards Pete

Try using the Event and Axis logging in FSUIPC -- see the logging page -- it may show how it is implemented. Otherwise maybe either a "mouse macro" may be made to work (if the gauges are made using the C/C++ gauge SDK), or possibly a Lua using local gauge variable writes (L:Vars). You can log L:Vars in FSUIPC too -- there's an assignable control in the drop downs. Regards Pete

In that case it sounds like there's something wrong with the value en route from the device. FSUIPC does not influence the IN value, that is either the value from the joystick, direct when assigning in FSUIPC, or the value for the actual control when assigned via FS/P3D. The value assigned via FSUIPC can be modified by extra parameters in the FSUIPC INI file, but only by scaling and transposing, not by suppressing changing values. What device is it you are using? Does it have its own software? If so, maybe it is some setting in that? The choice of where you set things up is really up to you. There are advantages to doing assignments in FSUIPC, mainly about having different assignments for different aircraft. But there can be disadvantages too. generally it is best to either do all axis assignmnets in FS/P3D and none in FSUIPC, or all in FSUIPC including buttons and switches, and disable controllers altogether in FS/P3D. If you don't disable you can get conflicts without realising it because f auto-assignments in FS. Regards Pete

Are you talking about the input value, or the calibrated output value? If it's the IN value doing that then those are the values being received. So in that case, how are you assigning? In FSUIPC or in Prepar3D? If in FS, to what are you assigning and in which mode? If in FS, then have you made sure the sliders are set correctly -- null zone far left, sensitivity far right? If you are talking about the OUT value, then you have calibrated incorrectly. just calibrate properly following the numbered steps. The central null zone is set by the two centre values when calibrating. Also make sure the Slope is set correctly. Maybe you have selected an excessively flattened curve there? Pete

Is it seen as an axis in FSUIPC's axis assignments tab? If so, please just refer to the example for this very application in the FSUIPC user guide. It's in the chapter on Axis Assignments, on about the 5th page therein. It's the part related to the "zones" facility, on the right-hand side of that tab. Regards Pete

How are these condition levers controlled? How are they assigned? If they are simulated in FS using the mixture controls, have you considered the use of Ctrl+Shift+ F1 to F4, which I think are the default keystrokes for mixture? Or is the "normal flight position" engaged by using a particular value for the axis? If so you could use an assignment to, say, AXIS_MIXTURE_SET (or AXIS_MIXTUREn_SET for engine n) with the parameter set to the correct axis value, which you'd need to determine using the normal mixture lever control. Note that any jitter input from your real mixture lever would mess this up, though. You would need the lever(s) to be in a good stable position or state. Sorry, that has me thoroughly confused. Regards Pete

Yes, that certainly should be true, though I don't think I've tested it explicitly. Regards Pete

The display will close when the thread is closed -- i.e. when the plug-in terminates, no matter how it does so. The thread is not closed when there are events being awaited, it is simply suspended awaiting them. Yes,. I'll have a look, but if I can't squeeze it in over the next few days I'm afraid it won't be till late January. If you don't hear from me before the end of next week, remind me after Jan 15th in case I forget (though I wil write it down in any case). Regards Pete

This is because there is only one communal Lua window which actually exists all throughout the session, and is simply shown or hidden by Lua actions. The "own display" is part of the Lua thread itself and cannot continue to exist when that thread no longer exists. No. The best I could do is probably to implement a new event which occures when the user closes the window. Then you could use the event to remain running, even not doing anything else but waiting for the event, till the user closes it. If this would meet your need let me know and I'll take a look. Regards Pete

Thanks for your suggestions. I will think about your ideas, certainly, but I'm a little reluctant to make any drastic changes. The problem is that all these facilities have been gradually bolted on a program which is getting on for 7 years old. Every bit of tinkering I do is liable to make the whole edifice crumble if I'm not careful. This is one of the reasons I added Lua plug-ins, to let users add their own facilities instead. I've also got the problem of trying to keep FSUIPC3 and FSUIPC4 more of less compatible parameter-wise so folks can move to fSX from FS9 easily. This has usually meant doing the same changes on even older code (15 years!) with more potentially disastrous results. I would also like most users to be able to do most things without actually editing INI files, and I would find it really messy trying to manage some of your ideas via the dialogue system without substantial changes. Regards Pete

You don't really need to do this unless you've already added the aircraft to the wrong profile and you want to correct it. In that case just delete it in the list in that [Progile.<name>.] section in the FSUIPC.INI file or FSUIPC4.INI (depending which version of FSUIPC you are using). Then as follows. If you haven't assigned it yet, just load it into FS and go to an assignment or calibration tab in FSUIPC options for which you've already created the profile, and add as per the user documentatin. Regards Pete

It isn't a hidden file. But it isn't produced until you have run FS with FSUIPC installed, just like the Log file. There's no installed INI. Doing that could upset a lot of folks who've spent a lot of time getting their settings just right. Pete

There's no overall "sensitivity" adjustment as such, just the slope facilty to allow you to flatten the response in the centre with corresponding increase at the extremes, or (to do the reverse of what you want to od), steepen the response in the centre and correspondingly flatten it at the extremes. Just adjust the slope in the calibration to suit your needs. Regards Pete

You posted in the FAQ subforum. I've moved it here to the Support Forum so it can be answered. No, because they aren't really doing much most of the time. and with real-time flight controls like trim, throttle and (especially) yoke you could do without the extra possible latency added by the network. WideFS doesn'tt natively support control axes in any case, though it can be done using a Lua plug-in. Also FSUIPC / WideFS don't support some of the Saitek units directly, especially not the displays. I think Saitek supplies its own drivers for these, though there's also a package called SPAD which may help - see http://fstools.weebly.com/. Regards Pete

Assign in the "FS control" mode to Steering Set, then, not in the "Direct To Calibration" mode Steering Tiller. In Axis assignments, move your tiller, clear the assignment, select FS control mode and scroll down the list to find Steering Set. THAT's the FS control, and THAT's the only one not linked to the rudder! The FSUIPC steering tiller uses the rudder to steer, because in all versions up to FSX that was the only way to steer! Only in FSX and P3D does the FS steering set control exist. As I said, obviously badly, use the steering set, not the FSUIPC steering tiller! Pete

Download Links is one of the 4 subforums listed at the top of this Forum. You should never have any trouble seeing them. If you managed to find your way to post your messages here you must have passed them, they are right at the top! The INI file is NOT provided by me, it is in your FS Modules folder!!! Everyone has his own settings saved there! It would be futile for me to provide one which suited no one! And why are you jumping around kinks anyway, when everything is presented clearly in front of you? Just look, please! Pete

The FSUIPC "steering tiller" always moves the rudder. There's no way around that. Only the new FSX steering set" control dsteers without moving the rudder. So why did you change? Pete

Ether you have sever jutter and need to clean or replace your joystick, or you have conflicting assignments - i.e. something else also connected /assigned to the elevator. Pete