Jump to content
The simFlight Network Forums

Deleted FSX-SE controls keeping reinstalling [MOVED FROM FAQ SUBFORUM]

Recommended Posts


I have installed FSX-SE on a new HDD. I have P3DV4 on a separate HDD on the same PC.  I have been using FSUIPC for years and like the many options and controls it provides.

This is my set up: CH Eclipse yoke, GoFlight GF-TQ6 quadrant, Saitek rudder pedals. These have all been calibrated, and appear stable in W10 calibration. 

When I delete the FSX-SE axes and button controls for my three game controllers I can sometimes set the controls in FSUIPC normally.

In flight though, either the yoke or the rudder, not usually the throttle controls, fail to obey instructions.

Checking back to the FSX-SE default controls, I find that many of these have reinstalled - button and axis commands. I've rebooted and restarted FSX-SE each time deleting the defaullt commands till I am blue in the face. But the problem persists.

The log file is below and I've attached the JoyScan.csv.

I'd be grateful for advice. 


********* FSUIPC4, Version 4.974b (14th March 2018) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0)
fsx.exe version = 10.0.62615.0
Reading options from "F:\FSX_Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 10
Module base=52C60000
User Name="John Fee"
User Addr="gooneybird@yankeedodge.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       15 System time = 04/04/2020 08:42:19
       15 FLT UNC path = "\\RUDOLF\Users\howar\Documents\Flight Simulator X Files\"
       15 ------ Module Version Check ------
       15        acontain.dll: 10.0.62615.0
       15             api.dll: 10.0.62615.0
       15        controls.dll: 10.0.62615.0
       15      fs-traffic.dll: 10.0.62615.0
       15             G3D.dll: 10.0.62615.0
       15        language.dll: 10.0.62615.0
       15            sim1.dll: 10.0.62615.0
       15        visualfx.dll: 10.0.62615.0
       15         weather.dll: 10.0.62615.0
       15          window.dll: 10.0.62615.0
       15 ----------------------------------
       46 Trying to connect to SimConnect Steam ...
       62 FS UNC path = "F:\FSX_Steam\steamapps\common\FSX\"
      125 ---------------------- Joystick Device Scan -----------------------
      140 Product= Saitek Pro Flight Rudder Pedals
      140    Manufacturer= Saitek
      140    Vendor=06A3, Product=0763 (Version 1.1)
      140    GUIDs returned for product: VID_06A3&PID_0763:
      140       GUID= {DAA2C6C0-EC02-11E7-8008-444553540000}
      140       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      140 Product= CH ECLIPSE YOKE
      140    Manufacturer= S
      140    Vendor=068E, Product=0051 (Version 0.0)
      140    GUIDs returned for product: VID_068E&PID_0051:
      140       GUID= {DAA25190-EC02-11E7-8006-444553540000}
      140       Details: Btns=26, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R460,U1023,V1023,X1006,Y1023,Z1023
      156 Product= GF-TQ6 Throttle System
      171    Manufacturer= GoFlight
      171    Vendor=09F3, Product=0200 (Version 1.0)
      171    GUIDs returned for product: VID_09F3&PID_0200:
      171       GUID= {DAA29FB0-EC02-11E7-8007-444553540000}
      171       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R219,U219,V222,X225,Y228,Z228
      171 -------------------------------------------------------------------
      171 Device acquired for use:
      171    Joystick ID = 2 (Registry okay)
      171    2=Saitek Pro Flight Rudder Pedals
      171    2.GUID={DAA2C6C0-EC02-11E7-8008-444553540000}
      171 Device acquired for use:
      171    Joystick ID = 1 (Registry okay)
      171    1=CH ECLIPSE YOKE
      171    1.GUID={DAA25190-EC02-11E7-8006-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 0 (Registry okay)
      187    0=GF-TQ6 Throttle System
      187    0.GUID={DAA29FB0-EC02-11E7-8007-444553540000}
      187 -------------------------------------------------------------------
      203 LogOptions=00000000 00000001
      203 -------------------------------------------------------------------
      203 ------ Setting the hooks and direct calls into the simulator ------
      203 --- CONTROLS timer memory location obtained ok
      203 --- SIM1 Frictions access gained
      203 --- FS Controls Table located ok
      203 --- Installed Mouse Macro hooks ok.
      203 --- Wind smoothing fix is fully installed
      203 --- SimConnect intercept for texts and menus option is off
      203 --- All links checked okay
      203 -------------------------------------------------------------------
      203 SimConnect_Open succeeded: waiting to check version okay
      203 Trying to use SimConnect Steam
      203 Opened separate AI Traffic client okay
     1015 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     1015 Initialising SimConnect data requests now
     1015 FSUIPC Menu entry added
     1015 F:\FSX_Steam\steamapps\common\FSX\flights\other\FLTSIM.FLT
     1015 F:\FSX_Steam\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air
     6109 Weather Mode now = Theme
    19312 User Aircraft ID 1 supplied, now being used
    19312 Aircraft loaded: running normally now ...
    39578 System time = 04/04/2020 08:42:59, Simulator time = 08:42:25 (16:42Z)
    39593 Aircraft="Aircreation582SL red"
    45234 Starting everything now ...
    46406 Advanced Weather Interface Enabled
   228375 Sim stopped: average frame rate for last 185 secs = 219.4 fps
   228375    Max AI traffic was 28 aircraft (Deleted 0)
   231109 === Closing session: waiting for DLLStop to be called ...
   233765 === DLLStop called ...
   233765 === Closing external processes we started ...
   234781 === About to kill any Lua plug-ins still running ...
   234937 === Closing global Lua thread
   235953 === About to kill my timers ...
   236156 === Restoring window procs ...
   236156 === Unloading libraries ...
   236156 === stopping other threads ...
   236156 === ... Memory checking ...
   236156 === ... Button scanning ...
   236265 === ... Axis scanning ...
   236375 === Releasing joystick devices ...
   236375 === Freeing macro memory
   236375 === Removing any offset overrides
   236375 === Closing all WideFS threads
   239359 === Clearing any displays left
   239359 === NOTE: not calling SimConnect_Close ...
   239359 === AI slots deleted!
   239359 === Freeing button memory ...
   239359 === Closing my Windows ...
   239359 === Freeing FS libraries ...
   240375 === Closing devices ...
   240375 === Closing the Log ... Bye Bye! ...
   240375 System time = 04/04/2020 08:46:19, Simulator time = 08:45:30 (16:45Z)
   240375 *** FSUIPC log file being closed
Minimum frame rate was 128.0 fps, Maximum was 349.6 fps
Minimum available memory recorded was 2720Mb
Average frame rate for running time of 185 secs = 219.1 fps
Maximum AI traffic for session was 28 aircraft
Memory managed: 96 Allocs, 95 Freed
********* FSUIPC Log file closed ***********



Edited by Pete Dowson
Link to comment
Share on other sites

20 minutes ago, John Fee said:

When I delete the FSX-SE axes and button controls for my three game controllers I can sometimes set the controls in FSUIPC normally.



If you mean delete their assignments in FSX-SE, then there's no need to do that in any case. Instead, if you intend to assign only in FSUIPC, then you should disable each of the controllers explicitly.

This is because, even if you delete all the assignments, FSX will made new assignments automatically if at any time it thinks the devices are newly connected and therefore waiting for defaults.



  • Thanks 1
Link to comment
Share on other sites

Thanks, Pete,  I was doing my homework in the FAQ section.

Disabling all the controllers in FSX-SE seems to have done the job. Although the yoke and rudder now respond correctly, the yoke movement in the VC is jerky, and similarly the elevators and ailerons in spot view. I was flying the default Cessna Skylane. It doesn't look good and in the past it has always meant problems.

Anyways, so far so good. Thanks again.



Link to comment
Share on other sites

38 minutes ago, John Fee said:

Although the yoke and rudder now respond correctly, the yoke movement in the VC is jerky, and similarly the elevators and ailerons in spot view.

Assuming you'd calibrated properly, and the controls are definitely disabled in FSX,  I suspect that the time available for FSUIPC to read, calibrate, and post on the values for the controls is just not available.  Also, FSUIPC limits its polling frequency to avoid impacting performance. The rate is set by the "PollInterval" parameter in the [Axes] section.  Now see this from your log above:

Average frame rate for running time of 185 secs = 219.1 fps

That's an obscene frame rate!  FSUIPC would need to poll 2-3 times more frequent to keep up. It also means FS is less able to spend time on other things than generating your views. You will probably find that mundane things like scenery texture loading lags behind if you ever go faster that the Skylane takes you.

Consider limiting the frame rate of your sim using the built-in limiter and / or Vsync options in FSX. You don't need more than 60 fps, and many folks are happy with 30 fps. I run my P3D installation at 25 fps.



  • Like 1
Link to comment
Share on other sites

Obscene frame rate indeed!  It was a new install so I hadn't got round to checking that. Now, set to a more leisurely 28 fps.

Applied Kosta's tweaks, extensive tests today with default scenery and aircraft and all is well, no more twitching control surfaces.

Thanks again. You never fail! 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.