Jump to content
The simFlight Network Forums

Recommended Posts

Posted

@speedbird144 You have three devices recognised. but two now seem to have the same id:

Quote

      453 Device acquired for use:
      453    Joystick ID = 2 (Registry okay)
      453    2=Razer Orbweaver Chroma
      453    2.GUID={23EAF9D0-BB93-11EA-8016-444553540000}
      453 Device acquired for use:
      453    Joystick ID = 5 (Registry okay)
      453    5=BU0836X_1
      453    5.GUID={23D6FCA0-BB93-11EA-800B-444553540000}
      453 Device acquired for use:
      453    Joystick ID = 2 (Registry okay)
      453    2=Flight Control Rudder
      453    2.GUID={23EAF9D0-BB93-11EA-8016-444553540000}
 

Also one device seems to have an issue:
 

Quote

      109 Product= <not readable at this time: maybe device disconnected?>
      109    Vendor=1532, Product=0207 (Version 1.1)
      343    GUIDs returned for product: VID_1532&PID_0207:
      343       GUID= {23EC8070-BB93-11EA-8019-444553540000}
      343       Details: Btns=3, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      343       GUID= {23D10930-BB93-11EA-8007-444553540000}
      343       Details: Btns=1, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      343       GUID= {23EAF9D0-BB93-11EA-8016-444553540000}
      343       Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255

 

2 hours ago, speedbird144 said:

Everything was normal with previous free version

Something else must have changed on your system. There were only a few minor cosmetic changes between the beta and the released version. Have you had a windows or driver update maybe?

Can you attach your FSUIPC7.Joyscan.csv file as well as your FSUIPC7.ini. And try not to start a new log. Think I'll remove that feature!

@katoema Hmm, strange. Glad its now working!

 

Posted

Hello, I also have two axes (my rudders and throttle/prop/mixture) not being picked up.  I successfully set up my first profile last night and calibrated my throttle quadrant and it worked fine.  Tonight it's not being picked up by FSUIPC at all.

 

FSUIPC7.log FSUIPC7.ini

Posted
9 hours ago, John Dowson said:

@speedbird144 You have three devices recognised. but two now seem to have the same id:

Also one device seems to have an issue:
 

 

Something else must have changed on your system. There were only a few minor cosmetic changes between the beta and the released version. Have you had a windows or driver update maybe?

Can you attach your FSUIPC7.Joyscan.csv file as well as your FSUIPC7.ini. And try not to start a new log. Think I'll remove that feature!

@katoema Hmm, strange. Glad its now working!

 

Attached. 

FSUIPC7.ini FSUIPC7.JoyScan.csv

Posted
9 hours ago, John Dowson said:

@speedbird144 You have three devices recognised. but two now seem to have the same id:

Also one device seems to have an issue:
 

 

Something else must have changed on your system. There were only a few minor cosmetic changes between the beta and the released version. Have you had a windows or driver update maybe?

Can you attach your FSUIPC7.Joyscan.csv file as well as your FSUIPC7.ini. And try not to start a new log. Think I'll remove that feature!

@katoema Hmm, strange. Glad its now working!

 

I reconnected all controls and looks like everything is recognized in FSUIPC now. I noticed controls stopped working in P3D as well. I have a feeling when Asobo pushed update 5 (before the patch) and people started complaining their controls started to fail causing CTD, maybe be something went off in controls settings. So far so good. Will keep playing with it. 

Thanks for help. 

Ed 

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.