Jump to content
The simFlight Network Forums

Controls Not Recognized


regis9

Recommended Posts

There is something strange going on with your devices - there seems to be a mix-up/registry problems between your TQ6+ and a vjoy device.
First you have this:

Quote

  503547    WARNING: Joystick ID 4 is duplicated in Registry

You  have the same joystick id (4) assigned yo your RUDDO+ and one of your x-box controllers (do you have 2?)

Then the mix-up between the TQ6+ and a vjoy device - from your log

Quote

    19891 Product= vJoy - Virtual Joystick
    19891    Manufacturer= Shaul Eizikovich
    19891    Serial Number= 2.1.9
    19891    Vendor=1234, Product=BEAD (Version 2.25)
    19891    GUIDs returned for product: VID_1234&PID_BEAD:
    19891       GUID= {F3E64CD0-A97E-11E8-8002-444553540000}
    19891       Details: Btns=128, POVs=(0, 18000, 27000, 9000), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
    19891 Product= VirtualFly - TQ6+  
    19891    Manufacturer=                             
    19891    Vendor=16D0, Product=0DA2 (Version 0.2)
    19891    GUIDs returned for product: VID_16D0&PID_0DA2:
    19891       GUID= {A283F420-D018-11E9-8002-444553540000}
    19891       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U4096,V4096,X4096,Y4096,Z4096
...

    19891 Device acquired for use:
    19891    Joystick ID = 2 (Registry okay)
    19891    2=VirtualFly - TQ6+
    19891    2.GUID={F3E64CD0-A97E-11E8-8002-444553540000}
 

So the TQ6+ has been acquired but with the GUID of a vjoy device.

And your axes  assignments are to device 'C', which is:

Quote

2=VirtualFly - TQ6+
2.GUID={F3E64CD0-A97E-11E8-8002-444553540000}
A=vJoy Device
A.GUID={F3E64CD0-A97E-11E8-8002-444553540000}
...
C=VirtualFly - TQ6+
C.GUID={A283F420-D018-11E9-8002-444553540000}

So it seems your registry is in a bit of a mess and there seems to be a problem with a vjoy device.

There are a few things to try:
   - revise your vjoy set-up
   - disconnect your TQ6+ and Ruddo+, remove any drivers and reboot, then re-connect to see if the issue get resolved
   - if that doesn't work, you will need to clean your registry. If you can show me your FSUIPC7.Joyscan.csv file I can help you with this.

John

Link to comment
Share on other sites

Thanks John, I couldn't find any specific VirtualFly devices drivers.  I had a look at the vJoy config and it only shows one device connected which I would expect is my Brunner Yoke (the reason I have vJoy installed).

I'm thinking this means I'll need to go the registry route?

For what it's worth I had a similar issue in FSUIPC6 with duplicate TQ6 entries in my FSUIPC.ini after I tried to set the axes up in P3D.  I deleted the extra entry but took what I assume is the device number from the new entry and changed it in the old entry and that seem to solve my issues there.  Here's an except from FSUIPC6 of my axes configuration.  3X and 3Y are where I inserted the number 3 from the new entry that was created:

[Axes.Airbus2 HOTAS]
RangeRepeatRate=10
0=0X,256,F,65764,0,0,0    -{ TO SIM: AXIS_RUDDER_SET }-
1=0Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-
2=0U,256,F,66387,0,0,0    -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
3=0V,256,F,66388,0,0,0    -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
4=3X,256,F,66420,0,0,0    -{ TO SIM: AXIS_THROTTLE1_SET }-
5=3Y,256,F,66423,0,0,0    -{ TO SIM: AXIS_THROTTLE2_SET }-
6=3R,256,F,66382,0,0,0    -{ TO SIM: AXIS_SPOILER_SET }-
7=4X,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
8=4Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-
9=5X,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
10=5Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-

This all seemed to start recently when I was playing another game that required me to unplug my TQ6 and my Warthog HOTAS throttles because their inputs conflicted with the game controls.  Wen I plugged them back in the issues started.

Thanks,

Dave

FSUIPC7.JoyScan.csv

Link to comment
Share on other sites

10 hours ago, regis9 said:

I deleted the extra entry but took what I assume is the device number from the new entry and changed it in the old entry and that seem to solve my issues there. 

Yes, we can try this first, although your ini/logs are quite confusing. As you only have assignments to your 'C' controller (TQ6), can you first try just removing al the entries in your [JoyNames] section  and replacing with

Quote

C=VirtualFly - TQ6+
C.GUID={A283F420-D018-11E9-8002-444553540000}
2=VirtualFly - TQ6+
2.GUID={A283F420-D018-11E9-8002-444553540000}

Start FSUIPC7 and see how it goes. Any issues, send back your new/updated .log and .ini, and I'll take a look at your Joyscan.csv file.

Link to comment
Share on other sites

Looks like I spoke too soon, after a successful flight earlier today, tonight my controls are not working again.  I'm really not sure what's going on here, it seems like something is making up additional controllers that don't exist, for example it's showing four X-Box controllers when I only have one?  Two TQ-6's when I only have one?  

I tried starting from fresh with a new FSUIPC7.ini file which is attached here and shows the extraneous controllers.

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

Link to comment
Share on other sites

11 hours ago, regis9 said:

for example it's showing four X-Box controllers when I only have one

It is showing 2 xbox controllers, not 4 - the other 2 entries are the joy letter assignments.

The problem is with your registry, with duplicate entries for the xbox one controller. I'll take a look later today and provide you with a script to run to remove the duplicate entries.

Link to comment
Share on other sites

Looking at your registry entries, it seems that both the xbox controller and your CLSE NG Yoke have duplicate entries.
Can you:
  - disconnect the CLSE NG Yoke and cbox controller
  - remove any software or additional drivers that you have installed for the yoke.
  - reboot (leaving devices still disconnected).
  - start regedit, and make a back-up of your registry
  - create a ,reg file (e.g. removeDevs.reg) wth the following content:
 

Quote

Windows Registry Editor Version 5.00

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_02FF]

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_045E&PID_02FF]

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_25BB&PID_008B]

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_25BB&PID_008B]

 

   - run the regedit file (i.e. double click it in windows explorer

You can then connect your devices again and install any software or drivers needed for the Yoke. Delete your current FSUIPC7.ini file and restart FSUIPC7.
Then lets see what devices are reported in your FSUIPC7.log, .ini and .Joyscan.csv files.

Link to comment
Share on other sites

Thanks John, a few questions to make sure I'm doing what I should be:

- When you say make a back up of my registry, do you mean by using the export inside regedit and then exporting all?

- How do I create a new reg file?  Is that done inside regedit?  I see the ability to create a new key?  Or do I just create a text file, put that content in it, the rename it to a .reg file?

Thanks,

Dave

Link to comment
Share on other sites

7 hours ago, regis9 said:

When you say make a back up of my registry, do you mean by using the export inside regedit and then exporting all?

Yes.

7 hours ago, regis9 said:

How do I create a new reg file?  Is that done inside regedit?  I see the ability to create a new key?  Or do I just create a text file, put that content in it, the rename it to a .reg file?

The latter - create the text file, addthe content and rename it with a .reg extension.

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.