Pete Dowson

I'm back and it is fixed -- MakeRunways version 4.87, available in the subforums and the usual links. Pete

There is a list of offsets for the PMDG 737NGX is your FSUIPC Documents folder. In a Lua program you read offsets using the ipc.readXX set of functions (where XX is the type, like UB, UD etc). Of you can use event.offset or event.offsetmask to react to changes. Pete

Is this with a prop plane, or jey? With a prop, as you increase throttle for takeoff the "propwash" from the prop is disproportionally down one side (normall the left), so you need to use more and more right rudder to compensate. Not sure why the throttle calibration would affect anything you describe. If you assign and calibrate in the Sim then you need to follow normal Game Controller calibration instructions. If you are using FSUIPC then there is a step by step list of things to do to achieve proper calibration of any selected axis. See the User guide, calibration chapter. Pete

No, but you can mix "direct" and "normal axis" controls. But even so, carb heat is an on-off control, isn't it? Not an axis control with variable settings. At least not in the prop aircraft I fly. The problem, and it isn't made clear in the documentation at present, is that FSUIPC only stores the axis values for those axes it scans, and it only scans those which are assigned. This is for efficiency, as it tries to scan frequently enough to avoid missing much. Of course if necessary you can assign to any innocuous axis control -- i.e. one having no effect or application in any of the aircraft you use. Pete

As well as what John says, generally, whether moving to a new system or merely re-installing windows, attention needs to be paid to the Joystick device identification. The way a device is recognised uniquely is via a thing called a GUID, which is a really big number generated and assigned by Windows when it first sees the device. Those numbers will be different on a new machine or after re-installing windows. Assignments are much easier to sort out again, without re-doing them all from scratch, if Joy Letters were assigned beforehand. Then all the individual assignments use the letters instead of the numerical joystick ID. Then, after moving things over or re-installing, it is just a matter of editing the assignment of letters to devices in the [JoyNames] section of the INI file. John or I can help you sort this out now, which is why he's asked for some files from the new PC. Comparing the assignments between those and the old ones will provide the solution.

Ah, no. There is no Client to Client sharing of globals, only Sim PC globals transmitted to clients. and not vice versa nor between clients. You'd need to use offsets instead. FSUIPC contains these values, and all clients can read and write them. Offsets 66C0-66FF are free for users to use for anything. Pete

One question: is the S axis assigned in FSUIPC? If not, does the Lua code work if you do assign it? I've a feeling it needs to be assigned to be recorded, but I've not checked the code yet -- tomorrow. The difficulty for us is that we have no "S" axis device between us, so it is more complex trying to set up a simulation for it. Pete

Even if FSUIPC was being asked to do something with a radio frequency, it would effectively do nothing if there was no change. I think, more to the point, why does ProATC/X think that the radio frequency has changed? In the extract you show it only logged one true change after all. So, sorry, I have no idea what it is doing nor why it is logging this. Pete

Yes, But check that you have WideLuaGlobals=Yes in the [General] section of the FSYUPIC INI file. How are you loading the COMP1 lua (I assume that's the flight sim one?). The one loaded by WideClient will run directly WideClient connects. This line in COMP2 is redundant: Depart=ipc.get("Depart") but I don't see anything wrong. Are you using up to date versions of FSUIPC and WideClient -- the Global facility was a later addition. Pete

There's been no change at all in the Registration system in FSUIPC4 or WideFS since 2016. So, you must be making a mistake. Either use the same FSUIPC4.KEY file from your 2016 installation, or enter all the details exactly correctly in the Installer. They'll be your original 2016 details, not today's if you've changed anything. Pete

No. All the examples are there for users to open and learn from. Each function used is either documented in the Lua Library document, or is a main Lua function documented on their website. I don't know XML scripting -- my only contact with XML is just for parameter files, i.e. an alternative to CFG and INI files. The Record to CSV example isn't like that. It records a list of values at fixed time intervals, which is why it isn't event driven, though it could be by using event.timer. In your case it seems you just need to have events for each of the values you want to record and timestamp. If these are all offsets then use event.offset (or event.offsetmask to select a flag in a byte of flags). Each function would test the value received and if it is to be logged, read the current timestamp using ipc.elapsedtime, or reading one of the offsets providing different time values from the sim (for the sim Zulu time, as you say). An event-driven plug-in is best loaded by an entry in the [Auto] section of the FSUIPC INI file. Pete

Isn't that software primarily built upon Project Magenta and dependent on it? What is reporting that and when? Nothing in the files you've provided shows anything about it. WideFS is registered, certainly, and appears to be working okay for one of your PCs. Looks like the other can't get adequate access. Are you running a firewall and haven't allowed these connections? Firewalls in Windows are default enabled. All this, as well as the other problems do suggest problems with your Network. Is yours a newly built setup, using such old software (the TSR stuff was withdrawn years ago).? If not, what have you changed recently to cause you problems? The logs aren't particularly helpful. This entry in your Comp1 pack is odd: 2683 Error on client gethostbyname() [Error=11004] Valid name, no data record of requested type I've never seen that error (reported from Windows, not WideClient) before. Try using the SrverIPAddr parameter instead of the ServerName, so that "gethostbyname" can be bypassed. Maybe do that in your other WideClient.INI files too. Pete

Both "S" and "T" are recognised by the ipc.axis function. The omission in the documentation dates from the FSUIPC3 implementation, so apologies. The document will be fixed. As to why it didn't work or, rather, did, but returning the fixed value 16191 (?), that needs checking here. The treatment of the S and T axes is no different in the code to the other 6, so it doesn't make sense, We'll have to find a device with an S axis to test. So it's good that you have an alternative suggestion. Pete

In that case you aren't looking at very good airport diagrams! What are you using? There are several programs which will display the airport details exactly asin your sceneries -- e.g. FS-FlightControl, and Aivlasoft's EFB which get their information from your sceneries. Navigraph and Aerosoft also provide charts both on-line and via applications but they will be for the current state of those airports. Well there are plenty, -- different websites for different areas. Not all free, and remember current real airport charts will only match your scenery if you are using an up-to-date addon airport. The default scenery is way out of date. Pete

for taxiing, I assume then that the brakes "seeming to block" is the parking brake? If so then it is released by pressing the toe brakes. That is a correct action, and should certainly be simulated by the PMDG model. Null zones are most certainly settable in FSUIPC when calibrating. You simply move the brake axis to the postion where you want braking to start before pressing the minimum button! As well as this, FSUIPc offers more in that you can choose a "slope" to adjust the sensitivity in the first part of the movement without losing full force braking when pressing fully. Pete

I've moved your support question to the support forum so it can be answered. The FAQ subforum, where you posted, is a reference section. The events are being caused by another add-on, possibly the aircraft you are using (check with a defalut), but also possibly by another application -- maybe something to do with VRInsight (I see two VRI ports you've defined fail to open. There are also 5 Lua plug-ins running, as indicated in the termination sequence: 181704 Lua threads being terminated: 181704 0 = "C:\FSX\Modules\MAxisThrottle.lua" 181891 LUA: "C:\FSX\Modules\MAxisThrottle.lua": killed 181891 1 = "C:\FSX\Modules\DC_F14D_CMDS.lua" 182079 LUA: "C:\FSX\Modules\DC_F14D_CMDS.lua": killed 182079 2 = "C:\FSX\Modules\DC_E2C_CMDS.lua" 182266 LUA: "C:\FSX\Modules\DC_E2C_CMDS.lua": killed 182266 3 = "C:\FSX\Modules\E2CECU.lua" 182438 LUA: "C:\FSX\Modules\E2CECU.lua": killed I'm afraid I dodn't know any of those so I don't know what they do. Pete

Is the INI file being written at all? does the date change? Is a LOG file produced? Pete

No demo. Sorry. Pete

No, in all current versions of FSUIPc4 and 5 the email address can be different. It is only the user name that should be the same. Pete

I've never actually used a wheel on such things. but each short press of the + or - key should only send one increment ir decrement control. Acceleration occurs when two or more of those occur close together, like a double click. I can imagine that happening quite easily with the mouse wheel, but you should be able to deal with it by slower pressing on the keyboard. You could enable event and key/button logging options 9two check boxes in the FSUIPC Logging tab, then checking the log after unwanted acceleration occurs. By (temporariliy) running the sim in Windowed mode you could enable console display too on the loging tab and see what happen as you press the keys. Pete

That action is optional and in recent versions it is defaulted off. See your FSUIPC5.INI file. The parameter, in the [General] section, is: RestoreSimcWindows=No Change it if it is set differently. Pete

Assuming you are issuing single keypresses or connands, then that must be to do with the way some add-on aircraft do things. You'dl need to ask their support. Otherwise it may be to do with how you are making these requests to the panel. you don't say. In fact you don't say even whether you are assigning buttons, keypresses, or whatever, or whether in P3D or FSUIPC. On 32-bit versions of FSX and P3D that was a fiddle done by patching code inside the sim. But that isn't possible in P3D4. Sorry. In any case that option was to allow "accelerated" (10) updates to those values when only single ones occurred -- because of interference from many additional controls intervening. It isn't related to your hardware, but your add-on aircraft which you don't even mention) or settings (which you also don't mention). Pete

So why are you posting again only an hour afterwards? It just makes more work for us in support. Please see your thread. Pete

No, sorry. It is just a straightforward SimConnect widow. FSUIPC just requests Simconnect to show it, and the rest is up t o P3D4. I'm afraid i've no idea what "scaleform" windows. The only window facility I am aware of is the SimConnect one. Ah, that's to do with Gauges displaying their own things. It isn't a Simconnect feature. You'd need to explain to L-M that it is a plain SimConnect_Text call with type SIMCONNECT_TEXT_TYPE_MESSAGE_WINDOW. If it displays okay in non-VR mode then it is definitely something you need to sort out with L-M. If not, then check the options in the P3D4 user options dialogue -- there's one about information text which if you want displays in Peeds to be ticked. You unitck it if you want then divered to another windows or PC using FSUIPc facilities or "ShowText". Check also the FSUIPC documentation about the options for displays on its from options screen, the ones below the 2about2 section. the RC instructions should tell you about setting those. Pete

Key settings? Do you mean keyboard assignments? Why would they have any affect if you aren't using them? I never bother unassigning default keyboard settings. If you mean jostick settings, then you do really need to disable controllers in the sim if you are assigning in FSUIPC. Both FSX and P3D have a habit of doing automatic re-assignments, especially if they see the devices as "newly connected". Do not simply unassign them. If you've previously assigned that profile for that aircraft it will be loaded for it. To save having to do that you can simply use a common abbreviation for the name same as 737NGX. You need to edit the aircraft list in the [Profile.<name>] section, where all the nmaes with that profile are listed. Pete