Pete Dowson

Use the Reverse option. In P3D is you aren't using FSUIPC, or in FSUIPC's calibration tab. (BTW the User Documentation is your friend here, and there's are pictures). If it is jittery then either is it dirty or faulty, or the power suppply is fluctuating. If you mean changing the response, then again look at the Calibration. As well as doing proper calibration with dead zones you can set response type by using the right "slope" for you. There is a "smooth" option, but it isn't recommended except in really bad cases, as in order to smooth things several successive input values need averaging, making the response slower. It might be okay for airliners, but certainly not for stunt aircraft, aerobatics, or fighters. Pete

No, and the FSUIPC Installer removes it. Also I believe the next update for P3D4 will delete them. Those entries are made by windows when a program crashes on exit. Windows blames the last component of that program still running, which is sometimes a thread of FSUIPC -- things like tidying up WideFF connections, Lua plug-ins and so on, is done whilst P3D is closing. Some Lua plug-ins, like those used by LINDA for some devices, use other external DLs and device drivers which sometimes don't shut down properly. Check the Windows Event Viewer to see if Windows has logged crashes or other errors in P3D. They will be the reason and may help identify which add-on is really causing the problem. However, quite often P3D seems to "crash to desktop" as if it has closed, and with no error information at all! Pete

I don't know that plug-in, but I very much doubt that it needs LINDA. As far as I know LINDA is a way of assisting in interfacing hardware, not driving specific aircraft. But do double-check. To stop it running, just as a test, all you need to do is rename ipcReady.lua. Then if you do find you need it it will be easy to re-enable. First, with so many devices you really should be using Joy Letters, not relying on the ID which Windows assigns which can change and ruin your assignments. Please see the chapter in the User Guide about this. Second, I can't tell from the log. Of the 8 devices recognised by FSUIPC, one or more are reconnecting, but FSUIPC only sees the re-connection, not the disconnection, and then does a complete re-scan to make sure its list is correct. (I will look to see if I can make it log which device reconnects). So, whilst I can't tell you from the FSUIPC log, you could find out with my HidScanner program, which logs all the details of all HID devices (not just joystick types), and then goes quiet until one connects again -- when it logs just that one. So yuo will see, but of course only if it happens outside P3D. Get HIDscanner from the Useful Additional Programs thread in the Download Links subforum. Pete

You also appear to be running LINDA, though you don't list it. As I said, the crash appears to be in some Lua plug-in, and LINDA uses plenty, and it even starts itself with a large Lua -- even though you say "The only LUA plug-in I'm using is "trimNGXtimer.lua" to use my Sitek wheel trimmer with PMDG 737NGX". The Log shows LINDA being loaded early on Also the log shows one (or more) of your USB connected joystick devices is contunally disconnecting and reconnecting. don't you notice any hesitations or stutters, because when that happens FSUIPC by default automatically rescans and reconnects all devices! That's pretty worrying. I'd check all your devices (you seem to have plenty). If you are not actually using LINDA for anything, stop it running. If you are then make sure it is fully up to date. LINDA loads itself via the ipcReady lua file. Maybe, if you discover it is a problem with LINDA you could report with a title indicating this, because then Scott, who supports LINDA, will help sort it. Pete

I need more information, please: FSUIPC Install log and FSUIPC5.LOG, both from the P3D Modules folder, plus a list of Add-Ons being used other that FSUIPC5 (don't forget FSUIPC is merely an interface for other programs and assignments). It would also be good to see a description of what led to the crash. Were you flying for hours beforehand? Did it occur during load of P3D or soon after? Please put yourself in my position who sees no such reports from others. I need to know what is unique, different, in your case. From the crash address it looks like something in a Lua plug-in, so information on what plug-ins you are using would help. Pete

FSUIPC knows nothing about where you are and cares even less. there is no code within it which would act any differently no matter where your aircraft is. You mean the DLL.XML. Seems like you are using (or have just reinstalled) P3D4.0 but are using FSUIPC 5.122. You must use P3D4.1 for FSUIPC 5.122. (Yes, I know you say it is P3D4.1 but see other threads where folks say this). Please find the FSUIPC and Installer Logs in the P3D Modules folder and show them to me. Pete

Well, that was evident with the Throttle3 test, but not the Spoiler test, which showed no sign of any untoward values arriving into FSUIPC from the joystick interface in Windows. I didn't continue looking for the third axis test, as two completely different symptoms, indicating different things, seemed to be enough. I'm sorry, but on the evidence of the logging I can say the problem isn't from within FSUIPC. I don't know what else to say. Pete

No problem, but I'd still like to know what buttons were or were not shown on the Registrations screen, in comparison with the pics in the Install PDF. Pete

What buttons are there on the Registration page? Anyway, the Log shows you have a proper Install in any case, so by aborting the Registration by escpaing from it you have effectively done the same as pressing the button! Pete

Well, it is only a connection between FSUIPC and the client PC, so "connected" means .. it is connected. If your FSUIPC application is not working, is it saying it cannot find the sim, or FSUIPC or what? Note that some applications, though thry use FSUIPC, also need to access the Sim's own folders which of course, are on the WideFs server PC. I'm afraid you might need to get help for application programs from the application's own support. If either of the Logs indicate an error let me see, but otherwise you should be okay. Pete

Good. So WideFS is now working for you. Sorry, I've no idea what that is. Is it an FSUIPC application you are trying to use on the client PC? Pete

You didn't answer my other quesdtions, but from the Log I gather the problem Quadrant is that FSUIPC has as Joy #1, with Spolier, Throttel1 and Throttle2. The Spoiler is not calibrated in FSUIPC at all, even though you have it assigned "direct to calibration"! I'm a little surprised it gets through at all, but i think that might be a difference between the 32- and 64-bit implementations. These lines show the first Spoiler reading: Read joy 1, Buttons=x00000000, POV=-1 301547 Axes: X=30703,Y=65535,Z=65535,R=0,U=0,V=0 301547 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 301547 *** AXIS: Cntrl= 66382 (0x0001034e), Param= -494 (0xfffffe12) AXIS_SPOILER_SET showing that an inpuy of 30703 (supplied by DirectInput) gives an output to P3D of -494. So it appears to be reversed? The first discrepancy is here: 301782 Read joy 1, Buttons=x00000000, POV=-1 301782 Axes: X=25543,Y=65535,Z=65535,R=0,U=0,V=0 301782 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 301782 *** AXIS: Cntrl= 66382 (0x0001034e), Param= -2827 (0xfffff4f5) AXIS_SPOILER_SET 301782 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 3612 (0x00000e1c) AXIS_SPOILER_SET Now, that second Spoiler control is most defitinely NOT from FSUIPC. So, either you have not turned off Controllers at all in P3D (and I don't mean just unassigning things, that isn't good enough), OR you have some other software or addon running with is doing its own thing with these inputs. The rest of the spoiler axis test is good, smooth, until whever else is doing things suddenly "catches up" with this burst, a few seconds after FSUIPC's controls are sent: 305625 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 7530 (0x00001d6a) AXIS_SPOILER_SET 305657 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 12382 (0x0000305e) AXIS_SPOILER_SET 305719 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 14613 (0x00003915) AXIS_SPOILER_SET 305797 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 15640 (0x00003d18) AXIS_SPOILER_SET 305860 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 16111 (0x00003eef) AXIS_SPOILER_SET 305922 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 16328 (0x00003fc8) AXIS_SPOILER_SET 305985 *** AXIS: Cntrl= 66382 (0x0001034e), Param= 16384 (0x00004000) AXIS_SPOILER_SET where the final value, 16384, coincides with an un-reversed X input of 65535 just before. I looked at the Throttle 1 test (axis Y on Joy#1) and that looks fine, no discrepancied, but then, after what looks like a spasm or jitter on all three axes on the OTHER quadrant, you went on to test Throttle3, which is on the other quadrant! The first oddity on that is very different: 314469 Read joy 0, Buttons=x00000000, POV=-1 314469 Axes: X=32768,Y=65535,Z=65535,R=0,U=0,V=0 314469 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 314500 Read joy 0, Buttons=x00000000, POV=-1 314500 Axes: X=0,Y=65535,Z=65535,R=0,U=0,V=0 314500 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 314516 *** AXIS: Cntrl= 65822 (0x0001011e), Param= 16384 (0x00004000) THROTTLE3_SET 315672 Read joy 0, Buttons=x00000000, POV=-1 315672 Axes: X=32768,Y=65535,Z=65535,R=0,U=0,V=0 315672 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 315688 *** AXIS: Cntrl= 65822 (0x0001011e), Param= 8192 (0x00002000) THROTTLE3_SET Suddenly that axis (X) defitely returned a zero (0, as you see. FSUIPC is not able to do that. The log line is showing the complete return exactly supplied by the USB device, for all axes and buttons and POVs. This example does suggest either a device fault, or USB, or a connection problem. Anyway, as well as this, I think you still need to answer those questions i posted before and which you seem to have skipped, i.e. and You go on to say: which is odd because you have no profiles defined. Why, if all things were good in FSX/P3D3, did you not simply use your existing INI (and any Profiles folder) in FSUIPC5? You only needed to rename the FSUIPC4.INI as FSUIPC5.INI. Pete

No. As I said, I have nothing planned for FSW at all at present! Pete

FSUIPCClient uses FSUIPC, so since there is no FSUIPC for FSW it isn't really usable. Pete

Sorry, no. There's no friction access via FSUIPC5. Please see the topic "Missing in FSUIPC5", in the FAQ subforum. Pete

Something is wrong with the P3D4 installation. The AddOns menu we are talking about is always in the main menu bar, and it would be the right-most. As Thomas pointed out, the log clearly shows that FSUIPC did add it. The rest is up completely to SimConnect. I am using P3D 4.1.7 Pro and it is fine on both Win7 and Win10. You could try enabling SimConnect logging (see the FAW subforum for details), and see if SimConnect is logging any sort of error there. This might also show whether other add-ons are loading and causing some sort of SimConnect conflict. Otherwise, I fear it is either a matter or doing a completely clean re-install of P3D, and/or reporting this to L-M. But what sort of conflict can be unique to just your system I can't fathom. Pete

Apart from the strange 89 minute discrpancy between the startup of WideClient compared to the Server: ********* WideServer.DLL Log [version 7.074] *********Blocksize guide = 8192 (double allowed)Date (dmy): 17/01/18, Time 15:52:38.401: ********* WideClient Log [version 6.999z4] Class=FS98MAIN *********Date (dmy): 17/01/18, Time 17:21:23.491: the real thing of note is this: which implies that the ServerName and Protocol lines in your INI file aren't being seen. Are you absolutely sure that the INI file you are showing me is from the same folder as the LOG file? because that "Need details ..." message only occurs when there's no such parameters. It also looks like your two systems are in different Workgroups. If they were in the same group then those parameters could be omitted, because then the broadcast's sent by the server (every 1000 mSecs, as logged) would tell the Client where to connect and how. So, try changing one or the other to be the same. You do this as follows: Win7: Control Panel ->System -> "Computer name, domain and workgroup settings"-> click "Change settings" on the right. Win10: With the right mouse button click the Start icon and choose System. Then same as above. Pete

No. Sorry, whilst a value is reserved, there are currently no plans to support FSW. If it were ever supported it woud not be FSUIPC5 in any case, but another, new, product. FSUIPC5 is intimately tied to P3D4. Pete

I have one Saitek Quadrant and it works fine with Win10 and P3D4. Are the three axes which are okay all one one of your Saiteks? Is the arrangement with one saitek plugged through the other, so sharing the same USB port? If so, which of the Saitek's is the one suffering? You only mention "calibration". Do the values jump around in the Axis assignments tab? FSUIPC is doing nothing different from other programs, just using the standard DirectInput calls into Windows. I don't know any other way without trying to bypass the joystick interface and going direct to the USB level (which is already possible in FSUIPC via a Lua plug-in). And it certainly is not doing different things for different axes. Is, perhaps, which axes jump around dependent upon which control they are assigned to? Or is it the same three no matter to which they are assigned? The logging has no axis logging exabled, so it isn't useful. Park all axes in a "stable" position (usually one extreme or the other) to eliminate as many unwanted log entryies as possible, Just enable ais logging in the Logging tab, then operate each of the rogue axes in turn, slowly fromm one end to the other. That will log the calibrated values only, not the input values, so you could, before loading P3D, add these lines to the [General] section of the INI file to get such extra data: Debug=Please LogExtras=x1000 Pete

The problem is probably that only the part of the given parameter between the first pair of " are being used. Have you tried removing the " " pair in the middle of the string? That shouldn't be needed unless iVAp needs it. The only other alternative would be to move the package to a path with no spaces. Installing things in "Program Files" is nearly always a bad idea for all sorts of reasons. Pete

No, you misunderstand. Rotary encoders are NOT analogue inputs. They effectively give two buttons one in each direction! That's the whole point of using rotary encoders, as I thought I explained in my previous reply. Pete

If you must use potentiometers it is best as assign movement of the potentiometer one way as the Increment and the other way as the Decrement, otherwise, even with proper scaling and a suitable analogue axis assignment: 1. It would be almost impossible to select a position for a precise value, and 2. Not all values are valid in any case, and you'd need to be able to deal with that, and 3. The upper and lower limits will vary from aircraft to aircraft, which isn't easy to deal with either. Far better for those adjusters to use rotary encoders, those with two button-type outputs which pulse depending on which way you turn the knob. As you are building your own device yuou'll find that gies you much more satisfying results, akin to the real controls on an actual MCP. Pete

Strange. Are they making them differently now? The Combo was one of the few panels provided to me by VRi. They were all at the same speed. I don't remember offhand what speed that was. (I'm out all day today I'm afraid). What is their software set to? Pete

I've move your support question to the SUPPORT FORUM, so it can be answered. You posted it n the "USER CONTRIBUTIONS" subofrum which is a reference library of contributions by users! Both WideClient and the WideServer part of FSUIPC produce Log files to show what is going on. Please show me those and the WideClient.INI file so I can check them for you. You can use the <> button above the edit area here to paste in the test copied from those files. Pete

What? FSUIPC5? You still haven't described whatever problem you think you have. Please read my previous questions again. If you have a problem with FSUIPC5's Installer, then say so, describe what the problem is, AND show me the contents of the Install log which is produced -- that is what it is for. Either way, this thread is a waste of time until you say what it is you are doing and what is going wrong! Pete