Thomas Richter

Hi, if it doesn't start what is it doing then, crashing? When you first installed FSUIPC4 and started FSX-SE did you confirm to trust the FSUIPC4 module? Thomas

Hi, press Yes/ Agree to run FSUIPC4.dll. Also please copy and paste the FULL content of the FSUIPC4 Install.log file, located in \Modules folder of FSX-SE (YourDrive:\Steam\SteamApps\common\FSX\Modules). Thomas

Hi 'penta_a', do you still a problem with your X-55 controller units and FSUIPC4.966c? If so and in case with your latest message and attached FSUIPC4.ini file you didn't have any Button or Axis assigned, could you please change your FSUIPC4.ini file for this both sections manually and run then again a test with an default aircraft instead. The JoyName section is your original and doesn't need to be changed, as long it is still the same. [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={32BD3B00-0998-11E6-8002-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={32BD3B00-0998-11E6-8006-444553540000} This both following sections should look like this, just copy and paste the sections by overwriting the existing ones. [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,4,0,0,0 -{ DIRECT: Throttle }- 1=1X,256,D,1,0,0,0 -{ DIRECT: Aileron }- [Buttons] PollInterval=25 ButtonRepeat=20,10 0=P1,0,K13,24 -{Key press: alt+Rtn}- This changed section have the X-Axis of your throttle unit assigned to FS Throttle (all engines) and the X-Axis of your Stick unit assigned to Ailerons. The assigned Button #0 is a Key Press: ALT + ENTER , so it will toggle windowed mode and full mode. We would like to see if the assignment will work instead of assigning something out of the menu. Thomas

Hi, please copy and paste the full content of your FSUIPC4.ini and FSUIPC4.log to your message. Also make sure you used the latest installer for FSUIPC4.966c. Thomas

Hi, there is no problem with calibration in FSUIPC. Please make sure you calibrate with the correct values. In FSUIPC calibration Tab the MIN value is and Set button is on the left and the max value Set button on the right. The value given by your controller or joystick you read in the window on the left. That means i.e. when you move your stick to the left you might read a positive value and you will have to press the Max value Set button on the RIGHT, moving the stick to the right might give a negative value (that's the Min) and you will have to press the Min Set button on the left. The Set buttons are logical placed (Minimum left and Maximum right) but the Min and Max value of controller have their values mostly not matching to the Set button positions. So make sure you check the value given if it is the minimum (negative, i.e. -16383) and press the corresponding Set button ... Thomas

Hi, please install latest FSUIPC4.966c, that will solve that problem. Install_FSUIPC4966c.zip Thomas

Hi, just in addition the INI file still says [General] UpdatedByVersion=4958 Did you install latest 4.966c ? Thomas

Hi (@ASadik), The version 4.966b works correct and you should use that in any case. You need to delete the existing controller entries under the [JoyName] section and then run FSX or P3D. If you have both installed you need to delete those entries in both/ any FSUIPC4.ini file ! I.e. here it looked like this and the identical devices have to be deleted (RED marked), or even all if you are not sure. FSUIPC4 will re-arrange the order and correct the Registry for that. [JoyNames] AutoAssignLetters=No 0=Logitech Extreme 3D 0.GUID={0667FA70-5979-11E4-8005-444553540000} 1=vJoy Device 1.GUID={04D9C8B0-994A-11E6-8002-444553540000} 2=Saitek Pro Flight Yoke (USB) 2.GUID={B4B9AF80-229C-11E7-8001-444553540000} 3=Saitek Pro Flight Yoke (USB) 3.GUID={B4B9AF80-229C-11E7-8001-444553540000} (It might be different arranged in your case) You will have to check if the previous Button and Axis definition still work, if not it is not an error of FSUIPC4 but the no longer matching of Controller (Joystick) letters that have been changed. Thomas

Hi, both throttle have now their correct unique GUID, so that will work correct in any case. Thomas

Hi, Works OK, I tried also your definition. But the only definition in your INI file is for A=Saitek Pro Flight X-55 Rhino Stick A.GUID={B15E4040-937C-11E5-8002-444553540000} with a profile only for [Profile.35] 1=F-22 Raptor - 525th Fighter Squadron and buttons for trim UP and DN [Buttons.35] 0=RA,8,C65615,0 -{ELEV_TRIM_UP}- 1=RA,6,C65607,0 -{ELEV_TRIM_DN}- Just delete those (Profile.32 and Buttons.35 sections) and define them new. In case the controllers might have been re-arranged they maybe swapped and the functions are no longer on the controller you expect. Thomas

Hi, delete the controller entries under [JoyNames] in FSUIPC4.ini file. On next start it will sort and recreate the GUID's correct. Thomas

Hi, make sure you deleted the devices they are identical first in [JoyNames] section, in your case the Pokey. Works for both, FSX and P3D Thomas

Hi, could you please attach the FSUIPC4.ini file and FSUIPC4.log file to your message of both FSX and P3D to see the possible difference. Thomas

Hi, please copy and paste the full content of the FSUIPC4.log file and the full content of your FSUIPC4.ini file to your message. Thomas

Hi, first thing would be to copy and paste the FULL Content of your FSUIPC4.log file into your message. Thomas

Hi, the trim changes correct also for PMDG B737NGX. The Trim wheels are not moving because it seems that PMDG doesn't read the actual trim value via SimConnect back but only the trim controls like Key input. I checked the Trim function here with B737NGX. For the other PMDG products it might be different. Thomas

Hi, that is not to FSUIPC itself related but an application that uses FSUIPC connection. In case PMDG uses SimConnect direct and not FSUIPC it will be one of the other app's you did run at the same time, maybe vPilot or Acars? Thomas

Hi, as always it is best to copy and paste minimum your FSUIPC4.log file (full content) and with settings problems as well the full content of your FSUIPC4.ini file, please. Thomas

Hi, as I already said: Thomas

Hi, you need to set the SimConnectStallTime= value to your needs of course because it will stay as it was saved last, max 20. Thomas

Hi, Latest is FSUIPC4965 Offset 0xBC0 range is 16383 (Trim Up) to -16383 (Trim DN), so you need to use instead offset sword decrement, x0BC0 50/-16383 and checked Control to repeat..... offset sword increment, x0BC0 50/16383 and checked Control to repeat..... That will show up in FSUIPC4.ini as (here) 1=R0,5,Cx43000BC0,xC1800032 -{offset sdword decrement, offset 0BC0 (Decr=50, Limit=-16383)}- 2=R0,3,Cx33000BC0,x3E800032 -{offset sdword increment, offset 0BC0 (Incr=50, Limit=16383)}- The -50 value you used to decrease would actually increase and because it is not signed value it gives the extreme high positive value. As the function already is defined as decrease there is no need to use a negative value BUT the max negative limit. Thomas

Hi, the only reason that this happens is that you actually are not using latest FSUIPC4, make sure you install latest version 4.965. Thomas

Hi, the FSUIPC Documents folder (subfolder of Modules) contains the file The 2016 List of FSX and P3D Controls.pdf where you will find the control VIEW IG VIEWGROUP SET 66848. That might be interesting for you. Thomas

Hi, there is no control for that in FSUIPC. You could send with a Button press the CTRL+K key press but you don't know of course the actual state, disabled or enabled. I have a problem that movement off the yoke disconnects the A/P... :( That is actual the correct function, depending on the system behind it you might have an option to disable this? Thomas

Hi, might be interesting respectively important. it seems that Windows 10 introduced an error I have never seen before, I don't remember this also not with Windows 10 before. Windows 10 Pro 64, Version 1607, Build 14393.969 If you have the Task Manager window open and active then Controllers freeze! As soon you de-activate it, select some other App or even the desktop then Controllers work normal again. I didn't see that effect happen with any other app but might be as well. Later: That is only true for P3Dv3 - HF4 ! FSX/ FSX-SE works OK. So more a problem of P3D than Windows maybe !? Thomas