Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Good day all. 

After W10 latest update all my controls are messed up. I have a tiller assigned via FSUIPC and it used to worked fine till Windows pushed the update. I assigned and calibrate tiller again and it works during taxi and suddenly stops working. If I restart FSX it may or may not work at all. I thought may be it was a conflict with Saitek rudder pedals but I assigned and calibrated pedals in FSX, not in FSUIPC. But pedals not working as before in anyway. 

Thx

PS. Not sure what part of the log I have to include, it is too long. 

********* FSUIPC4, Version 4.966c (17th April 2017) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
fsx.exe version = 10.0.62615.0
Reading options from "E:\FSX\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 10
Module base=5AD70000
User Name="My name "
User Addr="myemail@gmail.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 25/05/2017 23:59:43
        0 FLT path = "C:\Users\Admin\Documents\Flight Simulator X - Steam Edition Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.62615.0
        0             api.dll: 10.0.62615.0
        0        controls.dll: 10.0.62615.0
       16      fs-traffic.dll: 10.0.62615.0
       16             G3D.dll: 10.0.62615.0
       16        language.dll: 10.0.62615.0
       16            sim1.dll: 10.0.62615.0
       16        visualfx.dll: 10.0.62615.0
       16         weather.dll: 10.0.62615.0
       16          window.dll: 10.0.62615.0
       16 ----------------------------------
       31 Trying to connect to SimConnect Steam ...
       31 FS path = "E:\FSX\steamapps\common\FSX\"
      110 ---------------------- Joystick Device Scan -----------------------
      235 Product= BU0836X_1
      235    Manufacturer= Leo Bodnar
      235    Serial Number= B52708
      235    Vendor=1DD2, Product=2201 (Version 1.36)
      235    Assigned joystick id 5 (Registry okay)
      250    GUID= {CE02BA90-7BF8-11E6-8001-444553540000}
      250 Product= Saitek Pro Flight Yoke
      250    Manufacturer= Saitek
      250    Vendor=06A3, Product=0BAC (Version 3.3)
      250    Assigned joystick id 0 (Registry okay)
      250    GUID= {C8053830-C09A-11E5-8003-444553540000}
      250 Product= USB Controller
      250    Manufacturer= Goodbetterbest Ltd
      250    Vendor=25F0, Product=83C1 (Version 3.19)
      250    Assigned joystick id 3 (Registry okay)
      250    GUID= {848199F0-C162-11E5-8001-444553540000}
      250 Product= Saitek Pro Flight Rudder Pedals
      250    Manufacturer= Saitek
      250    Vendor=06A3, Product=0763 (Version 1.0)
      250    Assigned joystick id 2 (Registry okay)
      250    GUID= {C802C730-C09A-11E5-8001-444553540000}
      281 Product= USBAXES-PLUS V2 
      281    Manufacturer= Opencockpits   
      281    Vendor=04D8, Product=0000 (Version 2.0)
      281    Assigned joystick id 1 (Registry okay)
      281    GUID= {37E9E100-17C5-11E7-8001-444553540000}
      281 Product= Button Box Interface
      281    Manufacturer= Leo Bodnar
      281    Serial Number= B56985
      281    Vendor=1DD2, Product=1150 (Version 2.4)
      281    Assigned joystick id 4 (Registry okay)
      281    GUID= {8EE7B440-C938-11E6-8001-444553540000}
      281 -------------------------------------------------------------------
      281 ---------- Making INI JoyNames Section ----------
      281    Joy#0: OEMName = "Pro Flight Yoke"
      281    Joy#0: GUID = {C8053830-C09A-11E5-8003-444553540000}
      281    Joy#2: OEMName = "Mad Catz Pro Flight Rudder Pedals"
      281    Joy#2: GUID = {C802C730-C09A-11E5-8001-444553540000}
      281    Joy#3: OEMName = "USB Controller"
      281    Joy#3: GUID = {848199F0-C162-11E5-8001-444553540000}
      281    Joy#4: OEMName = "Button Box Interface"
      281    Joy#4: GUID = {8EE7B440-C938-11E6-8001-444553540000}
      281    Joy#5: OEMName = "BU0836X_1"
      281    Joy#5: GUID = {CE02BA90-7BF8-11E6-8001-444553540000}
      297 -------------------------------------------------
      391 LogOptions=60000000 00000001
      391 -------------------------------------------------------------------
      391 ------ Setting the hooks and direct calls into the simulator ------
      391 --- CONTROLS timer memory location obtained ok
      391 --- SIM1 Frictions access gained
      391 --- FS Controls Table located ok
      391 --- Installed Mouse Macro hooks ok.
      391 --- Wind smoothing fix is fully installed
      391 --- SimConnect intercept for texts and menus option is off
      391 --- All links checked okay
      391 -------------------------------------------------------------------
      391 SimConnect_Open succeeded: waiting to check version okay
      391 Trying to use SimConnect Steam
      391 Opened separate AI Traffic client okay
     4469 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     4469 Initialising SimConnect data requests now
     4469 FSUIPC Menu entry added
     4485 E:\FSX\steamapps\common\FSX\flights\other\FLTSIM.FLT
     4485 E:\FSX\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air
     9110 Weather Mode now = Theme
    34156 E:\FSX\steamapps\common\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
    37078 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    37406 *** EVENT: Cntrl= 86637 (0x0001526d), Param= -16256 (0xffffc080)  <86637>
    37406 *** EVENT: Cntrl= 85637 (0x00014e85), Param= 0 (0x00000000)  <85637> 

The rest my panel settings...

 

Thanks for looking.

Posted
3 hours ago, speedbird144 said:

After W10 latest update all my controls are messed up.

Anyone with multiple controls should use JoyLetters so that FSUIPC can retain the same assignments over changes like unplugging devices and updates to Windows.

3 hours ago, speedbird144 said:

I assigned and calibrate tiller again and it works during taxi and suddenly stops working.

Well, I know nothing except hardware malfunction which could make things "suddenly" stop working. If you aren't using it for a while and it stops then that's different -- probably power saving on the USB hubs. Check the power management settings in the Windows Device Manager.

3 hours ago, speedbird144 said:

If I restart FSX it may or may not work at all. I thought may be it was a conflict with Saitek rudder pedals but I assigned and calibrated pedals in FSX, not in FSUIPC.

It sounds like you are mixing assignments in FSX and FSUIPC. DO NOT DO THIS. Assign all in FSX or all in FSUIPC (and disable controllers in FSX), otherwise you will have conflicts.

3 hours ago, speedbird144 said:

PS. Not sure what part of the log I have to include, it is too long. 

And why, exactly, is it "too long"? Why have you enabled additional logging?

Anyway, please see the Download Links subforum above and give 4.966n a try. That will make a .csv type file which you can attach here.

Pete

 

Posted

Thanks for the reply, Pete.

I checked the tiller, FSX and Windows 10 do recognize it. I can assign the tiller to any axes withing FSX and it works. However FSUIPC does not recognizes it anymore. 

"It sounds like you are mixing assignments in FSX and FSUIPC. DO NOT DO THIS. Assign all in FSX or all in FSUIPC (and disable controllers in FSX), otherwise you will have conflicts."

I remember from our older discussions that PMDG does not like if you assign controls via FSUIPC, and I was suggested to assign controls within FSX, and I did. The rudder pedals works fine now. I did some steps Saitek suggested. 

"Download Links subforum above and give 4.966n a try. That will make a .csv type file which you can attach here."

Downloaded 4.966n. 

So everything was working great till Windows pushed the update. Rudder pedals were assigned in FSX and the tiller in FSUIPC. 

Thx 

FSUIPC4.JoyScan.csv

Posted
3 hours ago, speedbird144 said:

So everything was working great till Windows pushed the update.

Strange. 

Which device is the "tiller"? The CSV shows 6 good and usable devices, but with 4.966c there are only 5 selected, as shown in the log. i.e.

      281    Joy#0: OEMName = "Pro Flight Yoke"
      281    Joy#0: GUID = {C8053830-C09A-11E5-8003-444553540000}
      281    Joy#2: OEMName = "Mad Catz Pro Flight Rudder Pedals"
      281    Joy#2: GUID = {C802C730-C09A-11E5-8001-444553540000}
      281    Joy#3: OEMName = "USB Controller"
      281    Joy#3: GUID = {848199F0-C162-11E5-8001-444553540000}
      281    Joy#4: OEMName = "Button Box Interface"
      281    Joy#4: GUID = {8EE7B440-C938-11E6-8001-444553540000}
      281    Joy#5: OEMName = "BU0836X_1"
      281    Joy#5: GUID = {CE02BA90-7BF8-11E6-8001-444553540000}


Is it listed? All of those above are unambiguous, with correct GUIDs shown by DirectInput and in the Registry.

The missing one is "USBAXES_PLUS V2", which should appear as Joy#6 according to the csv results, but in the log it is listed as:

      281 Product= USBAXES-PLUS V2 
      281    Manufacturer= Opencockpits   
      281    Vendor=04D8, Product=0000 (Version 2.0)
      281    Assigned joystick id 1 (Registry okay)
      281    GUID= {37E9E100-17C5-11E7-8001-444553540000}

      
So I'm puzzled.  I need to see a detailed log relating to 4.966n please. ut before starting the sim, add these lines to the [General]section of the INI:

Debug=Please
LogExtras=x200000

Can you run my HidScanner please and show me the Log it makes.  (Useful additional programs thread in Download Links subforum).

It would be a good idea too, please, to show me your FSUIPC4.INI file.

Pete

 

 

Posted

Yes, USBAXES_PLUS V2 is the tiller (sorry, I missed to mention that). 

34150626633_7e9da7223b_z.jpg

So PMDG NGX was working today, 777 though had some issues. The tiller did not work originally when I loaded 777 but when I accessed to FSUIPC and selected Axis Assignment window the tiller popped up and started working. I am puzzled too, Pete. 

HidScanner.log

FSUIPC4.ini

Posted
2 hours ago, speedbird144 said:

Yes, USBAXES_PLUS V2 is the tiller (sorry, I missed to mention that). 

And your picture shows it as Joy# 7! As in my previous reply, the log shows it as device #1. So something changed between your last submission and this. In fact several things, judging by your INI:

[JoyNames]
AutoAssignLetters=No
3=USB Controller
3.GUID={848199F0-C162-11E5-8001-444553540000}
4=Button Box Interface
4.GUID={8EE7B440-C938-11E6-8001-444553540000}
5=BU0836X_1
5.GUID={CE02BA90-7BF8-11E6-8001-444553540000}
1=Pro Flight Yoke
1.GUID={56E55BC0-41B4-11E7-8001-444553540000}
6=Mad Catz Pro Flight Rudder Pedals
6.GUID={56E55BC0-41B4-11E7-8002-444553540000}
7=USBAXES-PLUS V2        
7.GUID={37E9E100-17C5-11E7-8001-444553540000}

So, the Yoke has moved from 0 to 1, the Pedals from 2 to 6, and the tiller to 7! Have you beed unplugging them and reconnecting them? I can't think of any other reason for them to jump around like this.

I see you aren't using JoyLetters, which means all your assignments t devices which move about are going to get scrambled. If I were you I'f mmediately start using letters. See the chapter on this in the User Guide.

Otherwise, you look set now? You'll need to change the numbers back manually in the list in the INI and duplicate the lines with appropriate letters. Here, I've done an example for you:

0=Pro Flight Yoke
0.GUID={56E55BC0-41B4-11E7-8001-444553540000}

2=Mad Catz Pro Flight Rudder Pedals
2.GUID={56E55BC0-41B4-11E7-8002-444553540000}

3=USB Controller
3.GUID={848199F0-C162-11E5-8001-444553540000}
4=Button Box Interface
4.GUID={8EE7B440-C938-11E6-8001-444553540000}
5=BU0836X_1
5.GUID={CE02BA90-7BF8-11E6-8001-444553540000}
7=USBAXES-PLUS V2        
7.GUID={37E9E100-17C5-11E7-8001-444553540000}

Y=Pro Flight Yoke
Y.GUID={56E55BC0-41B4-11E7-8001-444553540000}

R=Mad Catz Pro Flight Rudder Pedals
R.GUID={56E55BC0-41B4-11E7-8002-444553540000}

C=USB Controller
C.GUID={848199F0-C162-11E5-8001-444553540000}
B=Button Box Interface
B.GUID={8EE7B440-C938-11E6-8001-444553540000}
A=BU0836X_1
A.GUID={CE02BA90-7BF8-11E6-8001-444553540000}
T=USBAXES-PLUS V2        
T.GUID={37E9E100-17C5-11E7-8001-444553540000}

The ones I don't know I've lettered A, B, C. Change them it you wish.

I note now that you have weird axis assignments:

0=0X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
1=0Z,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
2=1X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
3=1Y,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
4=2Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
5=2R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
6=5X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
7=7X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-


Delete all the Tiller lines which are wrong.  And use the letters, so:

Check this. Not sure where your Spoilers and Throttle are. On the Yoke?

Only right brake, no left?

No aileron or elevator?

1=YZ,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
2=RY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
3=RR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
4=TX,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-


Or maybe you are better off starting from scratch -- delete the assignments and start again?

I notice you have no default generic assignments at all, only profiles. You are much betteroff doing all your standard assignments with no profile selected, with a default aircraft. THEN make the profiles which only then need to contain those things which are different.  Much easdier, shorter, and easier to maintain. For buttons, profiles ones override general ones. For axes you can opt to "base" the profile on the general ones, so they get copied first, THEN make your changes.

Pete

 

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.