Pete Dowson

Yes, try removing the unwanted extra "=" you have in those. Compare with your successful line and you'll see the difference I'm sure! You might need to use " " around the complete pathname because of the spaces in the path. You tried " at one end. Not sure why you thought only one at the end might help! Pete

4.853 is the current main Installer version, which includes all the documentation and ancillary files. The updates in between main re-installs are provided in the Download Links subforum, which you already know because you quoted it above. You even found the latest version as you confirmed when you said Why din't you "grab" it? Why are you so confused? You were pointed to the Subforum over in AVSIM! And Graham gave you a direct link just after your original post here. Why didn't you use that? I don't understand why you are missing all these pointers and helpful links! Pete

Things don't stand still. Version 4.859i was when that SIM1 frictions facility was first incorporated. Other things happen, the version 4.859j then k are released with other changes and improvements, and now we are on 4.859m as Graham said. Soon I expect it will change again. All you need to do is always use the latest. Regards Pete

I've nevere heard of that one! What is reporting this, and when? Do you have an Install Log? You being the administrator isn't the same. The elevated privileges needed are simply obtained by right-clicking and selecting "run as" then "administrator". However, the symptoms if it doesn't get enough is that it cannot write to the FS folders when FS is installed in Program Files, which it is by default. There's never been an "insufficient privileges" error that I'm aware of. In that case your Modules folder is not protected and the current Installer really doesn't need any privileges, and doesn't ask for any. The 4.853 installer is not substantially different from any previous installer, so I don't understand what you are seeing. I need more information. Regards Pete

There's no "WD". Plethora? Where else but the Lua library documentation? All the functions supported by the FSUIPC Lua libraries are documented with explanations in the Lua Library document, in the Lua Plugins package in your FSUIPC Documents subfolder. Or download the latest package from the Download Links subfolder. Regards Pete

This is a SimConnect problem which affects a very few people, but it is nonetheless very annoying. There is a thread in the FAQ subforum called FSX fails to run after FSUIPC4 first installed. Please read that. BTW I'm pretty sure OpusFSX doesn't use FSUIPC. Regards Pete

I've changed them slightly again, though the settings you will want to use will be the same. In 3.999y4 and 4.859m, which I'll upload later after a little more testing, the MaxSteerSpeed parameter has all these facilities: 8 The facility to 'blend' FSUIPC's steering tiller control into rudder control as speed whilst on the ground increases has been improved for airliners with a set of facilities to restrict the rudder effect in different groundspeed ranges. The simplest of these facilities keeps the rudder at 10% of its input until half way to the full threshold speed, then increase linearly to 100% This is intended to make reasonably easy to check the rudder pedals whilst taxiing without causing bad swerves, and also allows some use of rudder even at very slow speeds at the end of the landing ground roll. The value of 10% minimum comes from the 737NG where at taxi speeds the rudder deflection is a maximum of 7 degrees compared with 67 degrees fully. To make FSUIPC do this blending instead of the normal 0-100% linear method simply change the MaxSteerSpeed parameter in the relevant [JoystickCalibration] section of the INI file to a negative value, eg -60 for the default 60 knot threshold. A more complex specification can be provided which allows the user even more scope. The MaxSteerSpeed parameter can be given as MaxSteerSpeed = Qn1,n2,n3,n4 where n1 to n4 are numbers used as follows: If n1 is not zero, then rudder effect is 0% (ie eliminated) until a groundspeed of n1 knots. Then the effect rises linearly from 0% at n1 knots to 10% at n2 knots. If n1 is zero, then rudder effect is 10% until the groundspeed reaches n2 knots. n2 is not allowed to be zero. If n3 is not zero, then rudder effect rises linearly from 10% at n2 knots to 30% at n3 knots, then linearly again from 30% at n3 knots to 100% at n4 knots. If n3 is zero, then rudder effect rises linearly from 10% at n2 knots to 100% at n4 knots. n4 is not allowed to be zero. Note that apart from the option for n1 and n3 to be zero, n4 > n3 > n2 > n1. You should see that the option: MaxSteerSpeed=-60 is in fact the same as specifying MaxSteerSpeed=Q0,30,0,60 There is one shortcut. MaxSteerSpeed=Q is the same as specifying MaxSteerSpeed=Q10,20,30,60 Note that both tiller and rudder need to be assigned in FSUIPC by the "direct to FSUIPC calibration" method, and both be properly calibrated, for any blending to be active in any case. Have fun! Pete

Even more intriguing now, actually. I think things must have changed somewhat. RyanAir now follow Boeing recommendations in this matter -- see the extract from their current checklist below, which is from the official Boeing one. Additionally he explained "when you move the rudder pedals then the nose wheel will NOT steer if you keep the tiller in position, because the tiller is the only direct control for the nose wheel and can not be overridden by the rudder. So if you move the rudder then you will see on ground that as well the tiller will move magic to the nose wheel position because its actuator has a direct wiring connection to it (a bit more complicate but in a simple way seen). And that means if you move the rudder pedals you can just keep the tiller in its position to let the Nose wheel NOT steer." This is actually relevant in the before-taxi scenario, i.e. while static, because of the possibility of the toeing gear still being connected, or, if not, scrubbing of the nose wheel tyres on the ground and the unwanted additonal wear this would cause. So the problem in FS is that unless the creator of an add-on aircraft can do it (if it is possible), the nose wheel cnnot be held straight whilst the rudder is moved, so that part of the real thing cannot be executed. Additionally, I have had it confirmed that at all speeds less than 30 knots the rudder maximum deflection is 7%, which is about 10% or its normal max of 67%, so my original 10% minimum to 30 knots was correct. Regards Pete =========================== My red highlighting From actual Ryanair Checklist 3.11 Before Taxi Procedure – Pilot Flying <RYR> Flight controls ...........................................................................................................Check Make slow and deliberate inputs, one direction at a time. Move the control wheel and the control column to full travel in both directions and verify: • freedom of movement • that the controls return to center Hold the nose wheel steering wheel during the rudder check to prevent nose wheel movement. Move the rudder pedals to full travel in both directions and verify: • freedom of movement • that the rudder pedals return to center

Yes, good idea! Pete

Checking the Gauge SDK it says for one of these A: variables: "The A:GENERAL ENG FUEL PRESSURE, is a simulation variable (there are many hundreds of these, listed in the Simulation Variables document)." Now these are SimConnect values which are almost all mapped to FSUIPC offsets, so they should be accessible using the various ipc.read and ipc.write functions. Choose the one which suits the variable type. All of the FSUIPC offsets are listed in a document called FSUIPC4 Offsets Status, which is in the FSUIPC SDK. If you search that for "prop sync" you'll find is as a 32-bit Boolean value (i.e. 0 for false, 1 for active) at offset 2EC8. So you read it with ipc.readUD and write it with ipc.writeUD. Regards Pete

Nevertheless, something is blocking the access. Maybe you have a firewall you don't know about? The "connection refused" failure means simply that the connection was refused. That's all Windows tells you in such circumstances. There's nothing WideFS or I can do about it. Regards Pete

One way is to make sure the flight is saved with the panel showing. Anyway, I don't think there's any difference between P3D panels and FSX ones, is there? Both have FS commands to do this. "Panel 1" to "Panel 9" for the first 9 as listed in the view menu for them and notmally assigned to keyboard Shift 1- Shift 9, and also Panel ID Open, Panel ID close, Panel ID toggle, each of which takes the panel's ID as parameter. IDs are standard for standard panels but are otherwise defined in the PANEL.CFG file for the aircraft. There is a list of the standard panel IDs named in the PANEL.CFGs someplace. To send controls automatically on a change of aircraft you can use the [Auto ...] section facilty for each aircraft or profile, with a line which executes a macro containing the control operation. Alternatively, to do it on a flight being loaded, you could have a Lua plug-in running (initially loaded from ipcReady.lua) which worked on an event.system(FLIGHTLOAD, ...), and sent the appropriate controls then using ipc.control. Regards Pete

Interesting as I am pretty sure it is Ryanair pilots my contact deals with! I'll pass on to him these conflicting reports! ;-) Pete

In that case they are probably standard USB joystick type devices and don't need PFCHID. The USB devices PFCHID is designed to support only partially look like joysticks to Windows / FS.. Pete

Sorry, WideClient doesn't feature any debugging facilities. It isn't really interactive like FSUIPC is. Can you debug on the FS PC? Otherwise you'd need to simply add your own "ipc.log" lines to log progress and values. Regards Pete

Thank you! You too! Pete

Ah. PFCHid.dll is intended for their USB consoles, primarily to drive all the switches and so on. The auto-assignments you are getting are for the quadrant only. Quite honestly, I don't know. Are there instructions with it? The console I have is the Cirrus Pro. You need it for that. I don't know all their products and variations. Does yours have switches etc assigned automatically, via PFCHid, or are you seeing them and assigning them in FS or FSUIPC? If you don't install PFCHid does it all work? Seems like the axes should at least from your assignments above. Do the axis 17 ones respond in the axis assignments if you "ignore" the "Q" joystick ones? I think if I remember rightly, with PFCHid reading the quadrant you're supposed to assign to the axes it sees, these joystick 17 ones, else it assumes a default quadrant, a twin turbo or something. I'd have to check. Regards Pete

Axes 17-19 are either real PFC serial port connected devices with my PFC or PFCFSX driver, or "virtual" axes being injected into fSUIPC from add-on software or plug-ins via offsets 3BA8-3BC4. If oyu haven't installed such drivers, seems you have some other add-on writing to those offsets? Regards Pete

If both are connected at the same time then they should have different joystick numbers, from 0 to 15. What do you mean by "( number of joystic)"? Is this related to FSUIPC or WideFS at all? Regards Pete

I'm baffled as to how a "reinstallation" could make any difference, as all that does is replace the FSUIPC DL with another exactly the same -- if the original was corrupted in any way its signature check would fail and it would say so and not do anything. However, I note that in your posted INI file you now have no axes at all assigned except for the one Profile, "SAAB 340B" which you are using for the MJC 8-300 Q Qantas as well as the Saab 340B Rex. So I suspect it is due more to a tidy up of the INI than anything else. Regards Pete

Pete

Throttle4 Set is a normal FS control, the "K" stands for "Key Event" (the internal names for FS controls start "KEY_...". I think this dates back to when they were only keyboard controls). So, just send it using ipc.control(<number>, <parameter>). The parameters will be the 9 or 8 and you'll find the control numbers in the List of Controls in the FSUIPC Doecuments folder. Alternatively, instead of using Lua, you could simply assign direct to Throttle4 set in the FSUIPC Buttons and Switches option tab. Regards Pete

Good. Thanks for letting me know. Pete

Please see the FAQ subforum, entry entitled "READ THIS IF YOU LOSE YOUR FSUIPC or WIDEFS keys " Regards Pete

I've added more facilities so that folks can configure this even more flexibly. By setting the MaxSteerSpeed=Q (with no numbers) I set 4 (Q=quad) zones for the rudder influence. By default these are 0% up to 10 knots linear 0-10% from 10 to 20 knots linear 10-30% from 20 to 30 knots linear 30-100% from 30 to 60 knots This is also equivalent to the parameter given as MaxSteerSpeed=Q10,20,30,60. Use that format to change the thresholds. If you specify any numbers you must give all 4 and they must be increasing. The tiller effect is still linear 100% at 0 knots down to 0% at the max (60 knots by default). The original MaxSteerSpeed=60 and MaxSteerSpeed=-60 are also still available. I'm not releasing this generally yet. To try it download FSUIPC 3.999y3 Let me know. I've not made the same changes to FSUIPC4 yet. [EDIT] BTW, just got this from my fried who trains real pilots: "For Airbus you check the rudder while taxiing but for this you have a disconnect button on the tiller to disconnect the nose wheel from rudder. For Boeing you check the all controls before taxiing ones. Because Boeing doesn't have a disconnect button or switch for nose wheel wouldn't be able and also it is not allowed to do so." Which aircraft are you flying? Regards Pete