Pete Dowson

Okay. So you want that script to run when you press a key. Fine. Sorry, do you mean that the drop down assignments list has LuaClear? Of course. It also has LuaSet. LuaSet sets one of 32 flags for you to test, and LuaClear clears one of 32 flags. That is all. If you aren't using flags in your script then you don't need to use those, of course. You might also notice that there are other controls in the list too, like LuaKill, LuaValue. Why are you asking specifically about LuaClear Each control has a specific purpose.and they ARE listed and described in the Lua documentation supplied. Pete

No, it is not that I don't believe you, but I am saying that it does work and that there is not (cannot) be any difference FSUIPC can make in different video modes. If it is not working on your system and hanging P3D I think it must be related to either video driver, video settings, or another add-on interaction. Not by me, certainly. There is no way the code can work in Windowed mode and not in full screen mode because there is no difference as far as the FS controls are concerned. It is not FSUIPC which is moving the view but FSX/P3D merely obeying the panning controls being sent. The "random angle" you get intially is probably because of changing from a Windowed view to a Full Screen view of a different size. The FS screen coordinates are then different. If you do not then move the mouse then it won't change, obviously! You just need to re-centre by moving the mouse appropriately to the correct centre position. Thereafter it will be fine. I think you must be preventing this by changing back to Windowed mode again! Don't keep swapping screen modes and you'll be fine. If there were any way for FSUIPC to be notified of a change in Window / Full Screen modes then maybe I could find a way for FSUIPC to recompute the centre position. I may have a look when I get the opportunity. But it isn't really a big issue because most folks use one mode or the other, not changing back and forth. Pete

What do you mean by "latest FSUIPC version"? I am using 4.86 here and Mouse Look works fine in both windowed and full screen modes, in both FSX and P3D. The only oddity is that when you switch between the two screen modes the initial position may be changed if your Window is substantially different in size. (Once you recentre it, however, it is okay forever more till you swap between full screen and windowed modes again). There is no difference in how it works depending on screen modes and FSUIPC is not at all aware of the change, nor does it need to be. Pete

Assign the axis to a Lua plug-in. It's value will arrive as "ipcPARAM" and you can manipulate that in any way you like before posing it on using ipc.control. Why not simply select the "No Reverse Zone" option in the calibration page? That avoids this completely. Quite a few aircraft need such treatment. You'd need to find anythere way (usually a button with repeating "Throttle Decr") You can do that anyway, just using the calibration. Idle is always 0. Pete

Assuming the calibration for the centre is correct (make sure you have a dead zone to cover any possible value coming from the yoke when self'centred'), and also assuming you are only releasing the a?P when you are flying straight (ie no bank), then it must be a problem peculiar to the CS 777. Maybe it is using aileron trim for steering and that is left infcorrectly set, or maybe the flight you are loading for that aircraft has a bad initial aileron trim value? Check the FLT file and see? With just the one plane again? Have you checked the assignments? Sounds like the left brake pedal might be assigned to "Brakes" rather then just the left brake. Double check also for dual assignments. Regards Pete

Yes, you'd need to assign in FSUIPC instead. Regards Pete

I have to guess here as you aren't specific. Could it be you are running FS2004 or before? With a possibly out of date version of FSUIPC? And on Vista, Windows 7 or Windows 8? If so, do two things (1) make sure you are using the latest version of FSUIPC3 (3.999z), and (2) in the properties of the desktop icon you are using to start FS (right click on it for these), choose Compatibility, and set it to run in XP compatibility mode. The problem arises because FS2004 was written before Vista and doesn't understand about the Program Files protections then applied. FSUIPC is doing what it has to to survive correctly in such an environment. Pete

Thanks, I think Logbook corruption occurs sometimes when you have FSX crash on you mid-flight. However, such a corruption prevcents FSX starting up at all, irrespective of FSUIPC being installed. I've never known it to be related to the SimConnect timing bug. Regards Pete

Sorry, I don't understand that. Do you mean you use a Lua plug-in to run some other script? A Lua one too? LuaClear clears a Lua flag for your plug in. Are you setting a flag you want to clear? What is this about a "Key"? Pete

Isn't this getting an error? It should do. Did you check the Log, where Lua errors are posted? f = assert(io.open("C:\Program Files (x86)\NaturalPoint\OptiTrack Camera SDK\samples\VectorTracking\headtrackstream.txt","r"))[/CODE] As in C/C++. the "\" character is an escape character, used to inserts controls like line feeds. To get a real '\' in the string you have to use "\\". Pete

The PMDG NGX is extremely sensitive to turbulence, variance and gusts. You will either need to suppress these (see the check boxes in FSUIPC options, just under and in the same box as the smoothing options), or adjust the dynamics of these effects in the FSUIPC4.INI file -- the parameters are: TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,10,10 Please read about these in the FSUIPC Advanced User's guide. I think there may be recommened values posted somewhere in the PMDG NGX support forum. Regards Pete

What do you mean by "do not start at all"? I can't help without more information. Pete

I cannot support any version 4 other than the latest -- 4.86. Pete

Please do not make such silly wild accusations about FSUIPC without at least being specific about what you really mean and with actual VERSION numbers. "Latest" is NEVER enough information! There cannot possibily be anything FSUIPC is doing about your "lack of speed and climb ability". That has to be nonsense. FSUIPC has nothing whatsoever to do with aircraft modelling and performance! Pete

Sort of. At the time of implementing the facility it was derived for the amount of contiguous space available, that's all. Unfortunately FSUIPC's offset-based interface, which all started by in FS98 days with direct access to the FS "GLOBALS.DLL" data, the 65k limit was far in excess of needs. It became restrictive because everything is predicated on a 16-bit value. I just turn off the ATC voice in the Sound menu, and never use the ATC call-up key/control. You can of course ntercept the keypress and do something else with it, like nothing. Pete

As documented, Mouse Macros only work on gauges created with the standard FS C/C++ gauge SDK. Microsoft's own aircraft hardly use that at all, with all their gauge code built-into the main code instead. For default aircraft use the FS controls instead. For some add-on aircraft mouse macros do not work either, as they are, these days, often written in XML. For those you may be able to use L:vars instead, sometimes. Pete

There's a Lua plug-in example in your FSUIPC Documents folder which creates a file with all sort of information about the current situation. You should be able to adapt that easily to output the values from the documented PMDG NGX offsets. (See "record to csv.lua"). Pete

I am not familiar with either of those products and cannot support them. Don't they have their own support forums? Regards Pete

In FSX/P3D only, then, as Paul says -- offset 3BF8 is the number of positions available, NOT the current position. For the flaps angle, do as Paul says, but for the flaps handle position (0,1,2,3 ...) you need the one byte offset 0BFC. This is also only valid for FSX/P3D. Pete

It sounds like there is an error in your registration. As Ian said, the user name must be the same for bothe FSUIPC and WideFS. The email address can be different, but not the user name. Actually Ian that is not exactly true. You can register and use WideFS without also registering FSUIPC, if you do not need the FSUIPC user facilities. However, you are certainly correct about the user name which I would guess is the problem here. The VRI facilities in FSUIPC do need a correct FSUIPC registration. Regards Pete

No. Sorry. Pete

Sorry, I can't really help as I have neither PMDG aircraft nor Saitek controls. I would be surprised if Saitek were using a rotary encoder if there are fixed (notched) positions, so you should be able to assign. If it is truly an encoder and you can only detect up and down, then of course you could have a macro which did autobrake inc or dec. There's no mouse emulation. Do mouse macros work on the autobrake in PMDG? If not check the list of controls in the PMDG NGX SDK documents (at the end of the .h file). Also, you might be better off asking this in the NGX ad/or Saitek forums. Regards Pete

Very strange. I'm pretty sure no traffic-adding program has any bearing on what WideFS is doing. Maybe it is using the same TCP/IP port numbers as WideFS? You can change those -- in the WideClient.INI and in the FSUIPC.INI (for FSX/P3D) or WideServer.INI (for FS9). Try that. You need to update it if you want support, that's all, as I can't support old versions. The method is by downloading the WideClient ZIP and putting the EXE wherever you want it, overwriting the older one. There's no installer, none is needed for such a simple process! Pete

Aircraft modelling is all in the Aircraft files -- CFG, AIR and MDL. I use a modified version of the default 738 with good realistic modelling. Extras are provided by TSR software, which covers the auto-braking behavious and other things not otherwise simulated properly by FS itself. Pete

No. Sorry. Pete