uhh i just googled to see if anyone else was having a problem lately my 360 wireless controller has been shutting off automaticly everytime i cast fire ball or its cast on me the 1st 2 times i played thru the game it was fine but now EVERY TIME it just turns off
Controller Issue
Débuté par
Viral Strike
, déc. 16 2009 07:21
Retour en haut
#27
Posté 06 mai 2010 - 07:07
Lone hero
-
- Members
- 43 messages
so it appears this is a coding issue huh never happened till i got Wardens keep first playthrough to warriors runs up to a skeleton and hmm i think i'll circle him or i think i'll just stop or i think ill attack the enemy behind me
#28
Posté 31 juillet 2010 - 10:13
gwfran
-
- Members
- 4 messages
So is there any fix for this? My controllers (the original and a new one) both do this and this game is basically unplayable. If there's no fix for it, I guess I never buy BioWare again.
#29
Posté 31 juillet 2010 - 10:18
Sesshomaru47
-
- Members
- 1 455 messages
It is your controller, it's stuffed, busted, ready for the trash heap, a pile of junk if you will. Mine did the same thing, I swapped it over and now the problem is gone. So you can all stop blaming the game and start blaming mircosoft or whoever made your controller.
#30
Posté 31 juillet 2010 - 10:25
OBakaSama
-
- Members
- 3 112 messages
I'd agree it's the controller (mine does it too). It's strange that the sensitivity is more noticeable in DA (and my current game of ME2) because with other games I play the problem doesn't appear.
#31
Posté 01 août 2010 - 05:31
gwfran
-
- Members
- 4 messages
Well, I went out and bought a new controller and it does the exact same thing AND this is the only game that the problem exists on. As a software developer, I can say that this points to an issue in the software. It may be because of a flawed porting to the XBox console, but either way, this bug is BioWare's and they need to resolve it instead of just ignoring our emails. A bugfix where the zero-center of the control is expanded is all that's required, but apparently that's asking too much. I'd love to blame it on Microsoft (I hate Microsoft with a passion), but the evidence says otherwise.
#32
Posté 01 août 2010 - 05:48
gwfran
-
- Members
- 4 messages
Reading further - apparently BioWare has this issue with Mass Effect as well. The problem is that they didn't set the deadzone variable for Mass Effect or DA:O so the smallest drift in calibration of the controller will result in the issue. The fix for this would be to submit a bug fix that sets the variable - but apparently that's asking too much after I've (and others) have shelled out $100+ for this game. So my answer is still the same - they won't get any more of my money.
#33
Posté 01 août 2010 - 05:55
gwfran
-
- Members
- 4 messages
From the Microsoft Developer's Network:
Dead Zone
In order for users to have a consistent gameplay experience, your game must implement dead zone correctly. The dead zone is "movement" values reported by the controller even when the analog thumbsticks are untouched and centered. There is also a dead zone for the 2 analog triggers.
Note
Games that use XInput that do not filter dead zone at all will experience poor gameplay. Please note that some controllers are more sensitive than others, thus the dead zone may vary from unit to unit. It is recommended that you test your games with several Xbox 360 controllers on different systems.
Dead Zone
In order for users to have a consistent gameplay experience, your game must implement dead zone correctly. The dead zone is "movement" values reported by the controller even when the analog thumbsticks are untouched and centered. There is also a dead zone for the 2 analog triggers.
Note
Games that use XInput that do not filter dead zone at all will experience poor gameplay. Please note that some controllers are more sensitive than others, thus the dead zone may vary from unit to unit. It is recommended that you test your games with several Xbox 360 controllers on different systems.
