AsaiaCZ / javascript-joystick

Automatically exported from code.google.com/p/javascript-joystick
0 stars 0 forks source link

Plugging in new controller renders previous controllers unrecognizable. #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Plug in a second HID compliant usb controller and previously used 
controllers are no longer recognised by the plugin
2.
3.

What is the expected output? What do you see instead?
Expected plugin to reference the current active controller but this seems to 
refer to the most recently used controller.

What version of the product are you using? On what operating system?
Joystick plugin ver 0.6.3 / Windows 7 Home Premium Sp1 

Please provide any additional information below.

Found while using GE Flight simulator.  Have contacted Xavier, the simulator 
author, and he notes that this is not due to the way he references the plugin.

Here's what I experienced in GE Flight:

I have originally used x-box 360 controller for GE Flight - recognized fine 
(as a generic HID compliant device) and working very well.   
I also have Thrustmaster T-Flight Hotas X flight stick - also recognized 
without problems (also handled by as a generic HID compliant device) and 
working well.

The problem is if I unplug the T-Flight and plug the X-box 360 controller back 
in, it is no longer recognized, but the T-Flight is.

It seems as though previously used controllers are no 
longer recognized where latest used controller takes precedence.  Possibly 
referencing last used and not current active controller? 

I have another hid compliant controller so to test this I : 
- Cleared Browser cache/cookies 
- Shut down browser 
- Unplugged X-Box 360 controller 
- Unplugged T-Flight stick 
- Plugged in my Razer Nostromo Gaming Keypad 
- Loaded up the browser and tested response of controllers.

Result: 
-The Nostromo pad was recognized and usable.
-The X-Box 360 is no longer recognized. 
-The T-Flight stick is no longer recognized. 

In each of these tests only 1 controller was plugged in at a time to rule out 
conflicts & which one was the currently active one. 
Tested in Firefox 12.0 & SR Ware Iron 18.0.1050.0 (Chrome clone)  with the same 
result.   
Google Earth Plugin ver 6.2.2.6613 
Joystick plugin ver 0.6.3 
Windows 7 Home Premium Sp1 

Thanks

Original issue reported on code.google.com by send...@gmail.com on 18 May 2012 at 2:29

GoogleCodeExporter commented 8 years ago
when uaing gefs and google the large cities like boston/los angelas render 
serfaces  like on the moon with bumpy runways !! Why???? 

Original comment by olbo...@gmail.com on 26 Mar 2013 at 6:45

GoogleCodeExporter commented 8 years ago
Update:  Selecting a controller as 'The preferred controller for older games' 
in windows controller properties - allows the device to be recognized again.

Original comment by send...@gmail.com on 26 Mar 2013 at 10:48

Attachments:

GoogleCodeExporter commented 8 years ago
The plug-in uses the (very) old Windows method of accessing controllers so this 
makes sense (it was originally written for Win98/2k).

Original comment by cwoffen...@gmail.com on 27 Mar 2013 at 9:08

GoogleCodeExporter commented 8 years ago

Original comment by cwoffen...@gmail.com on 8 Dec 2014 at 12:12