Pete Dowson

The instant jump is correct as the Arm position is specific. Not sure that the value -6768 is right though, but it should certainly be near enough. On a scale from -16384 to +16383, the value -6768 corresponds to 4808 on the internal spoiler value (range 0 - 16383). I need to see the log with those options enabled. Also please log the actual spoiler value. You do this in the Monitor facility on the right-hand side of the Logging tab: Offset 0BD0 Type U16 and check "normal log" at the bottom. What confirmation do you have when "armed"? there should be an indicator somewhere in the aircraft panels, depending what aircraft you use. For example, on a B737 it's an indicator on the pilot side of the MIP, above the displays. Pete

The armed position does raise the spoilers very slightly. This has always happened in all versions of FS. A null zone isn't relevant here. The point it setting the Arm zone, which you have done: Spoilers=-2988,-1156,-257,13184 When the axis value is between -1156 and -257, the output to the Sim should be the value corresponding to ARM (4800). Please check this by observing the IN and OUT values you see in the Calibration tab. The log would be of some use if you first enable both even logging options. Pete

... but you've not seen a Pause problem with WideFS before? Surely something else has changed, or haven't you paused for longish periods before? Nothing is WideClient or the WideServer part in FSUIPC has been changed for a very long time -- especially the Network side of things. Is WideClient hanging or crashing? did you check the Event Viewer on the client to see? If it is still running (such that you can close it normally) then it will be continually attempting to reconnect. I see you have two Clients (according to the Server log). Do they both hang or stop at the same time? If only on the one client (with RC) has anything changed recently on that PC? My little Lua FPS display displays FS time, which isn't changing whilst the Sim is paused in any case. But I can see by the slightly varying frame rate that the connection is still live. That and the also slightly changing WideClient frames per second showing the the WideClient title bar. Pete

So you recently update FSUIPC and / or WideClient? Nothing else? Same P3D5 build for how long? Presumably something must have changed? I've seen some reports of odd things happening when P3D5 is paused for a longish time. I suspect something is causing either WideClient or WideServer to timeout. I thought from reading those other reports of anomalies with long pauses that P3D or on of the usual addons is taking too many CPU cycles. As you know, I'm very dependent on WideFS working well and continuously on my cockpit, but since 5.2HF2 I've had some weird things happen on long pauses -- just seemingly not specifically in WideFS in my case. I'm reserving judgement on this until I've installed and tested P3D5.3 on my cockpit PC (up till now I've only had it on my development PC to check that FSUIPC compatibility is maintained). Maybe you could do the same if you can't identify what has changed on your system. BTW one of the very interesting things in 5.3 is a facility to assign different CPU cores to different aspects of P3D activity. Pete

The current version of FSUIPC6 is fine with 5.3. Pete

They are fuel valve states. The Engine Idle/Cutoff fror jets is the mixture control -- full lean for "cutoff", full rich for "idle". That's what the idle/cutoff levers on the throttle quadrant do. The fuel valves normally operate automatically as a result of enabling the fuel flow in this way. Best to just assign your idle/cutoff levers or switches to those mixture controls. If you need to use offsets then they are 0890, 0928, 09C0, all 16-bit words. Use 0 for cutoff, 16363 for idle. Pete

There's a full explanation in the WideFS Technical document, but in essence ask it does is tell WideClient to use a simple PostMessage sequence to feed to a Window with keyboard focus. This seems more likely to work in Win10 because my normal preferred method of using SendInput seems to be broken in the recent versions of Windows. Pete

Do you mean the "Axis ThrottleN Set" controls. Those are the ones used by P3D assignment. In FSUIPC there are three ways of assigning throttles, so you'd need to be much more specific. It is not possible to assign axes in the Calibration tab. Calibration is the process of matching the hardware axis input, wherever assigned, to the full range required by the aircraft. If you assign axes in P3D then do NOT assign them in FSUIPC or you will get conflicts. And some aircraft (PMDG ones particularly) do not like the FSUIPC calibrated axis outputs because they detect the values at a higher level. I don't know any way where assigning and/or calibrating one axis can affect or stop an entirely different axis control behaving correctly. Pete

No, sorry. There's no FSUIPC activity other than what you program it to do, and then it would be by button, axis or keyboard input as the trigger. You could use Event and Axis logging to see if anything is sending an unwanted input, but best not to enable such logging until just before your expect this behavior or the resulting log will be far to big to analyse easily. Pete

No. They are separate logs created each time you press the "New Log" button. Please don't do that unless it is suggested as a way of keeping the logs smaller. 1. Your default (non-profile specific) axis assignments are only for Aileron, Elevator and Throttle. You haven't assigned any axis to Rudder, which is why you have no rudder control. 2. Your axis assignments for the Connie have very strange Delta values: [Axes.Connie] RangeRepeatRate=10 0=0X,1,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0Z,3225,D,4,0,0,0 -{ DIRECT: Throttle }- The normal Delta is 256, meaning that the value is only used when it changes by 256. The settings of 1 for Aileron and 3225 for Throttle are both rather ridiculous. I suspect you've been messing around on the axis assignments tab without realising what you are doing. Please just follow the instructions in the user guide. And, again, you haven't assigned the rudder! Pete

Are you calibrating them in FSUIPC? Calibration doesn't care what the range of the inputs are because it scales them to reach the correct maximum and minimum values required by the specific control being sent to the Sim. With a throttle being set with both forward and reverse ranges, the maximum thrust for reverse is never the same as for forward thrust -- the Aircraft CFG file specifies the limit, defaulting to 25% (so -4096 instead of -16364). It isn't really very clear from your post whether a) you are assigning and calibrating in FSUIPC b) what controls you are assigning to c) what calibration options you are setting. Perhaps you should ZIP up and attach your FSUIPC6.INI file, so we can see what you are doing. Pete

I succeeded in using "PostKeys=Yes" to get keystrokes into Notepad, but only if the latter had focus. As you say, it looks like the SendInput method to a specific program is blocked by Win10. But you could try it with no "RunN" parameter on the WideClient KeySendN= parameters, so the keys are specifically sent to the program. Pete

Just ZIP files up for attachment. They are just text and do ZIP up really small! I don't know what a Ko is (a knockout, or a threat in a game of Go perhaps?), but a kb is a kilobyte -- i.e. 1000 (Kilo) bytes (the unit of size in computer memory and files -- one byte contains 8 bits). Pete

If it is a proper USB Hid device then it is likely that it is also a Joystick type device, which would mean that it would be plug-compatible with FS as it is, with no need for one of my PFC drivers. The fact that it boasts "compatible with X-Plane and FSX" would seem to point that way. But, as John says, you should be asking PFC -- after all you are buying it from them. I've not seen any new equipment from PFC for many years. Pete

A full log is what you get if you don't edit the log file, nor ask FSUIPC to start a new one -- as you did before uploading the Log you attached. This is shown here (the red line): User Name="donald torres" User Addr="lmartinez072717@gmail.com" FSUIPC6 Key is provided WIDEFS7 not user registered, or expired 268547 System time = 05/11/2021 03:54:31, Simulator time = 14:01:14 (19:01Z) 268547 FLT path = "C:\Users\User\Documents\Prepar3D v4 Files\" [Continuation log requested by user] If you don't press the "New log" button then the log will start from when FSUIPC starts, and give some extra vital information. Pete

No, sorry. The only way would be to disable all the others. And then you'd have to take the data and merge/replace appropriately in your previous file set. You'd be basically doing a lot of what the program does, but manually. And it would take you longer than just letting the program do it all. Surely your system has the odd ten minutes spare from flying to let the program run fully? Pete

Sorry, I thought the normal way for RCV4 was working for you -- i.e sending your reply on the FS PC, not via SendKeys. The VjoyOffsets facility is for those applications which can (maybe alternatively) expect a joystick button press. Pete

This is the data MakeRwys extracts for WAWI: Airport WAWI :S03:41:38.3263 E138:56:14.0481 2799.12ft Country Name="" State Name="" City Name="Wurigelebur" Airport Name="Arsbol Airstrip" in file: Official\OneStore\fs-base\scenery\1004\APX85330.bgl Runway 20 /2 centre: S03:41:38.3263 E138:56:14.0481 2799.12ft Start 20 : S03:41:32.1714 E138:56:17.0173 2791.99ft Hdg: 205.6T, Length 1577ft Computed start 20 : Lat -3.692030 Long 138.938171 Start 2 : S03:41:44.4813 E138:56:11.0807 2791.99ft Hdg: 25.6T, Length 1577ft Computed start 2 : Lat -3.695929 Long 138.936310 Hdg: 205.648 true (MagVar 0.000), Grass, 1577 x 83 ft *** Runway *** WAWI0200 Lat -3.692030 Long 138.938171 Alt 2799.12 Hdg 206 Len 1577 Wid 83 *** Runway *** WAWI0020 Lat -3.695929 Long 138.936310 Alt 2799.12 Hdg 26 Len 1577 Wid 83 Perhaps you wanted Wawi airport, Pemba,: Pemba Airport (IATA: PMA, ICAO: HTPE) is an airport in the Zanzibar Archipelago located on Pemba Island. It is also known as Karume Airport and Wawi Airport. It is located approximately 7 kilometres (4.3 mi) southeast of Chake-Chake, the capital of the island. The Zanzibar government is looking into the possibility of renaming the airport to Thabit Kombo Jecha in recognition of his role in the Zanzibar Revolution.[3] That is listed for MSFS as: Airport HTPE :S05:15:26.5174 E039:48:41.0105 77.00ft Country Name="" State Name="" City Name="Pemba" Airport Name="Chake Chake" in file: Official\OneStore\fs-base\scenery\0704\APX58330.bgl Runway 3 /21 centre: S05:15:25.9991 E039:48:41.1375 77.00ft Start 3 : S05:15:47.8977 E039:48:32.1125 80.00ft Hdg: 22.3T, Length 4972ft Computed start 3 : Lat -5.263531 Long 39.808826 Start 21 : S05:15:04.1005 E039:48:50.1628 80.00ft Hdg: 202.3T, Length 4972ft Computed start 21 : Lat -5.250914 Long 39.814030 Hdg: 22.313 true (MagVar -1.600), Asphalt, 4972 x 94 ft *** Runway *** HTPE0030 Lat -5.263531 Long 39.808826 Alt 77.00 Hdg 24 Len 4972 Wid 94 *** Runway *** HTPE0210 Lat -5.250914 Long 39.814030 Alt 77.00 Hdg 204 Len 4972 Wid 94 Pete

Are you using Win10 on the client PC? If so, that may be the problem. Something MS has done in Win10 prevents keystrokes being sent to other processes. See this: https://www.tenforums.com/software-apps/49635-sendkeys-not-working-windows-10-a.html and also: There is an alternative which should work: using a Virtual Joystick. My VJoyOffsets program acts as an FSUIPC client program, reading offsets which provide the data for button presses and axis values. Please see http://fsuipc.com/download/vJoyOffsets.zip. Documentation is included. Pete

It is certainly looking that way. But I had a further think about this. There is an existing alternative which should work: using a Virtual Joystick. My VJoyOffsets program acts as an FSUIPC client program, reading offsets which provide the data for button presses and axis values. Please see http://fsuipc.com/download/vJoyOffsets.zip. Documentation is included. Pete

Well I assume by now you've tried all three different ways they can be configured on the WideClient PC. There's something on your Client PC which stops all attempts. Sorry, I don't know what and, worse, I don't know how to find out. Pete

FSUIPC won't interfere unless you've something in your settings which leads to some action. I'm afraid I can't offer any help with no information provided -- like how you are try to squawk ModeC and what the result should be. There are facilities aimed at Squawkbox for using an offset that program used to read, as described in the Advanced User's guide (page 13): NoActionOn7B91: This can be added to the [General] section of the FSUIPC4.INI file, and set to 'Yes', to prevent FSUIPC4 setting the SquawkBox 4 transponder mode when an external program writes to offset 7B91. This gets over a problem with, in particular, the OpenCockpits driver, which seems to try to handle both SB3 and SB4 transponders by writing to 7B91 and dealing direct with SB4 at the same time. The FSUIPC4 parameter does not stop the FSUIPC-added SB4 transponder controls from operating, however. and of course these are two added FSUIPC controls to operate this: 1001 PTT on (for Squawkbox 3, Roger Wilco or AVC Advanced Voice Client) 1002 PTT off (for Squawkbox 3, Roger Wilco or AVC Advanced Voice Client) As far as I know FSUIPC and VPilot don't have any common interface -- unless they also followed Squawkbox's methods. Pete

Several points here: KeySend = 84,26 can never be selected as there is no KeySend number. Yes, +16 for release, but it is also + 8 for press only -- otherwise you get a press and immediate release. So, assuming you are assigning KeySend1 to the press of your PTT button, and KeySend2 to the release of your button, then you should have these: KeySend1=84,18 KeySend2=84,26 Please do refer to the examples in the WideFS Technical guide (eg page 16). You've not shown me your assignments in FSUIPC so I can't check those for you. These are my KeySend assignments for P2A: UseSendInput=Yes KeySend110=112,16 ; F1 Press PTT for P2A KeySend111=112,24 ; F1 Release PTT for P2A KeySend112=121,16 ; F10 Press Sayit for P2A KeySend113=121,24 ; F10 Release Sayit for P2A KeySend114=117,16 ; F6 Press Sound device for P2A KeySend115=117,24 ; F6 Release Sound device for P2A They work well and consistently for me. For logging you can use Log=KeySend. The "DebugAll" is really for all encoded frames being received from and sent to the Server. Pete

I thought you'd sorted RCV4 using local sim PC responses. not via KeySends. What's your other (new) problem? I don't see it explained here. Pete

I think you are confused. The 84,10 you want is part of the parameter for WideClient, on the client PC. In FSUIPC you merely choose SendKeyt with a parameter 1-255, giving up to 255 actions possible in the clients. It is in the WideClient INI file you tell it what action to take, like pressing a key combo. Please do review the supplied documentation. Pete