Pete Dowson

So it is definitely the add-on aircraft setting 25% when it sees FS or FSUIPC setting idle thrust (90%). What a daft thing to do! As you say, you'd need to change the calibration numbers to stop idle ever being set -- one way is to reduce the -16384 limit in the calibration section of the FSUIPC ini file to something lower still, which is never reached. Pete

That is simply not true. The installer will only refuse to replace a LATER version, not an earlier one. If you are finding that isn't happening for you then the only possibility is that you are running an installation which is not Registered in the Windows registry, so the FSUIPC doesn't install there. Show me the Install log file if you think there's something different going on. Pete

Version 4.937 was released long ago, way before P3D version 2.5 was even thought of! You MUST check for the current supported version of FSUIPC before posting such reports. The current version, 4.944a, does support P3D 2.5, and previous versions have done since the day of its release! Pete

No, it's definitely a problem with the installation of the X55 which does seem to happen regularly on Win10 and has been reported before. Please see the FAQ subforum thread "Fixing joystick connections not seen by FSUIPC"

That's correct. and will normally be calibrated to 0, which is the normal FS idle. Like the Saitek throttle. Yes, that's what i thought. So it must be the button action which is doing it ... Well, the button isn't activated. You need to log axis Events as well as the discrete events, please so we can check that the axis values being sent are correct. Are you sure it isn't the add-on aircraft you are using, treating an idle (zero) input as something special? Pete

Thanks for the info. News to me! Pete

The problem is that when it saves the flight, SimConnect times out. It looks like it takes seconds with the sim, or at least SimConnect frozen. It is doing it every time it saves a flight. See: 1224109 **** No SimConnect events or states being received! Re-connecting now ... **** 1224218 SimConnect_Open succeeded: waiting to check version okay 1224218 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 1224218 Initialising SimConnect data requests now 1224218 FSUIPC Menu entry added 1224218 C:\Users\Desk-Rob\Documents\Flight Simulator X Files\AutoSave Wed 140550.FLT 1225000 System time = 16/09/2015 14:06:03, Simulator time = 06:54:40 (05:54Z) This effectively restarts FSUIPC each time. I suspect this is related to your PMDG aircraft. Please first test with a default aircraft. It the performance of your Win10 systems in saving flights is as bad as others are reporting, I'm surprised you can tolerate the hesitations in flight whilst they occur. The PMDG aircraft make that 10 times worse. You can make FSUIPC more tolerant of bad Simconnect responses. I'll tell you more after you test with a default aircraft. Pete

FSUIPC reads buttons and axis values using the same system. Something must be wrong with the Installation of the joystick. Do FSX/P3D see the buttons? Do either of them see the throttle lever(s) -- you don't mention the axes. What stick have you got which you say works? Pete

Okay. Can you both please try 4.944d, an interim update in which I've changed to "DeleteFile" instead of "remove", to see if that helps. Download the DLL only from FSUIPC4944d_TEST.zip and copy it into the FS Modules folder. If it still fails to delete older files, please show me the FSUIPC log file -- it should contain some ***ERROR Autosave ... entries which will give me the reported error number. Pete

Hmm. It looks like the standard ANSI library function "remove" isn't working in Windows 10. That's a bit of a shocker! I'll try the lower-level function "DeleteFile" instead, and also log it if it returns an error. Bear with me, I'll just build an interim version for you to test. Pete

No. Wideclient just presents an FSUIPC interface to FSUIPC applications. FSUIPC applications have to use very Windows-specific API functions in order to operate that interface. It just wouldn't apply to any other operating system. What you want is a networking app at each end, the one on the FS PC being an FSUIPC client. You could even use a Lua plug-in at that end to send and receive data -- see the examples of networking plug-ins provided with FSUIPC. In particular see the slave/server networking to link two PCs running FS, one being slaved off the other. Pete

The filetypes are normal. FS saves three files for every saved Flight. Some add-on aircraft also save files -- PMDG aircraft especially. Are all of the file NAMES the same format, i.e. all with day number and time in the name? The only relevant part of the INI is this: [AutoSave] Next=1 Interval=60 Files=5 SaveOnGround=Yes AutoSaveEnabled=Yes 1=Tue 213333 2=Tue 213432 3=Tue 213532 4=Tue 213631 5=Tue 213731 6=Sat 181634 7=Sat 181734 8=Sat 181833 9=Sat 181933 10=Sat 182033 This shows that you used to have it set to 10 files, so at least half the files would have been from before you changed to 5 files. FSUIPC cannot make retrospective corrections to the saved files. Best to delete all the saved files when you change the options, then things won't get confusing. I don't know. That's why I wanted to see the fileNAMES, not the file TYPES. Pete

What is the INput value from the axis at the aft detent? Are sou sure there isn't a button there, as on the Saitek throttles, and that button is assigned to a control which is causing that action? Enable Button and Event logging in FSUIPC and see what is happening, as there is no way FSUIPC will be doing this without good reason. FSUIPC does no such things. Axes are just numbers which change as you move a lever, Calibration merely maps the input range to the desired output range, and you are in full control of that. Pete

Please show me the filenames of the 9 FLT files, and also the [Autosave] section from your FSUIPC4.INI file (in the FS Modules folder). Incidentally, the 737NGX saves files too. FSUIPC simply sends Delete File commands to Windows in order to delete the oldest set when it requests FS to create new ones. It would be a bit disastrous if Windows 10 doesn't allow files to be deleted by programs. Pete

Are you sure they are all FSUIPC-generated flight files? Can you show me a few of the filenames? There are many add-ons which also save files when a flight is saved. To check you only have 5 actual flight files only count those with the FLT filetype (or FXML for P3D). If you are using add-ons which save extra files, FSUIPC can manage those too, but you need to tell it about them. Please look up the Autosave chapter in the "FSUIPC4 for Advanced Users" document. Note that if your Flight Sim crashes there may well be orphaned sets of saved files for which the index in FSUIPC's INI file hasn't been updated. If you do find FS crashing you will occasionally need to clean up old files yourself. Pete Pete

The Installation instructions which were inside the ZIP you downloaded, sitting right next to the Installer, did actually tell you where everything was and listed what you'd find there! Did you not read the Installation instructions? Pete

MOVED FROM SUBFORUMS TO SUPPORT FORUM SO IT CAN BE SEEN AND ANSWERED! First, let me ask. Have you read any of the FSUIPC User Guide, one of the documents installed for you in the FSUIPC Documents subfolder? If not please do read some, at least those sections relevant to what you want to do. Let me split your message up into its separate questions: Do you mean you press a button but nothing appears showing the joystick number and button number? If so it sounds like the joystick isn't installed correctly. Seems that Saitek installers are very prone to this. If FS itself can see the buttons and axes, then it may just be a problem with the registration of the device -- the most common problem with Saitek installs. To fix this please refer to the FAQ subforum above, look at the thread entitled "Fixing joystick connections not seen by FSUIPC". If FSX cannot see the device either you need to reinstall it from scratch, or visit the Saitek support forum. Naturally the other parts of that settings dialogue cannot really be used until a button or switch is identified, as there's nothing to which it can assign whatever actions you want to select. You are not SELECTING an aircraft here! To select an aircraft go to the appropriate FS menu! You are creating a Profile for the CURRENT AIRCRAFT -- i.e. the one you have loaded in FS and the one you would be assigning actions for. If you already have created any profiles they will be listed for you and you can thereby add the currently loaded aircraft to that profile. Or you can create a new one and give it a name. I really do suggest you at least browse through the User Guide. (It contains pictures as well! ;-)) Probably the same answers as above, then, without more information to go on. Just search tags. Some folks use them, most don't. No, sorry. This is a support forum. Answers are given in the forum, that's the point. Pete

But I don't see any other posts from you! In any case you can delete your own posts then post in the proper place yourself. If you have a question, post it in this, the Support Forum, with a suitable title. If the title states the subject clearly then others may be able to help too, or instead of myself when I'm away (which is often). Pete

THREAD MOVED FROM FAQ SUBFORUM so it can be answered.. It depends on when I see them, or in my absence, another moderator who just happens to visit. BUT if you post support questions in SubForums, not in the main Support Forum, they will usually be ignored for so long that they get really outdated and in the end, deleted. The FAQ subforum, where you posted, is like the other SubForums, a repository for information, not a place for interctive support threads. Pete

Looking at your settings you've made a bit of a hash calibrating Throttle 2. Compare the two entries: Throttle1=-16143,-512,512,16383/32 Throttle2=-8192,596,596,745/32 If the full range of values supplied by Throttle2 is only -8192 to +745, as you've calibrated here, then there's either something seriously wrong with that part of the unit, or you've got some driver installation or Windows calibration issues. For modern USB axes the normal range is -16384 to +16383, and whilst I always recommend that you leave a region at either extreme free, to allow for small variations such as humidity, temperative, voltage changes, your numbers are very bad. However, nothing here wouild explain "erratic and jumpy" if what you mean by that is that they go back and forth, or "jitter". If that is the case then you either have faulty hardware or a very dirty device. You have different calibrations in profile "be56" which you use with the Baron: Throttle1=-16143,-512,512,16383/32 Throttle2=-7745,-512,512,1340/40 Throttle=-16380,16380 There you have a conflict in any case, with the generic all-engine Throttle calibrated as well as two separate throttles. You should reset that. Here your Throttle 2 calibration is just as bad -- -7745 to +1340. Worse, you appear to have enabled the "Filter", which is a desperate measure indeeed, especially if applied to one throttle and not both as they will behave asymmetrically. I see you also have a profile called "g1000"., used with the Mooney. There you don't have throttle 2 assigned, but: Throttle=-16380,16380 Throttle1=-16143,-512,512,16146/32 again you have the generic throttle calibrated as well as the seperate throttle1. Reset that. Pete

So, it isn't SmartCars, and not FSUIPC ... time surely to visit PMDG's forum? Pete

I think you must be in the wrong place. Why not try a support forum for "SmartCars" (whatever that is), or PMDG? Pete

No, there's no difference whatsoever in FSUIPC's treatment of axes between FSX and P3D. Did you copy over your FSUIPC4.INI file, so you had the same settings? You provide no information I'm afraid. Are you assigning in FSUIPC or P3D? If in FSUIPC have you disabled controllers in P3D? Are you calibrating in FSUIPC? Is FSUIPC anything actually to do with it? And what IS the latest version which you have installed They have numbers. Folks often say "latest" and mean "the last one I noticed". The current one, the supported version, is 4.944a. The version of FSX or P3D is not relevant to FSUIPC's axis and calibration support. Pete

No. Plug-in support has only ever been available for registered users. Pete

Hmm. Very strange. I'm sure that if it were a general problem there would be a massive thread or multiple threads about it here. The only usual problem with using FSUIPC with PMDG aircraft is in the area of the Throttles, where calibration in FSUIPC can't be used because their aircraft take the throttle value directly, and FSUIPC has to bypass that in order to calibrate and feed in the modified vales at a different level. The throttles can still be assigned in FSUIPC, but to the normal FS controls ("Axis throttleN set"), and then not calibrated -- i.e ensure the calibration tab for them says "not processed". This is effectively the same as assigning them in FS itself, but doing it in FSUIPC allows you to turn off controllers in FS so that there are no conflicts for aircraft assignments in other profiles. Hope you find out what is wrong in your system! Pete