Well I am using wireless and have no problems now.
Win XP SP 2 XBC wired ALtest Xbox drivers from MS.
All working fine I can now interact with multiple itemes by select Up on Dpad. Then Up down On Dpad to select item then A to activate and it works fine for me
yea it doesn't work for me either, something going on here. I have one of the wired controllers (sorry not spending 40 dollars just to use a wireless controller when the wired one works just fine).
Sometimes I can get a selection to trigger by choosing it, then pressing right on the d-pad, then swinging the d-pad toward up in one continuous motion.
Well that last patch for fixing the interaction bug didn't go well, did it? Seems like most are reporting this interaction /bug is still there. I went in game last night and approached a bunch of crates that prompted me with no less than six menu buttons that all said "Pick up crates". I was able to navigate up and down and shockingly pick up each crate with the "A" button and throw it with "DPad_Up". I was not able to do that before.
But when I walked up to multiple quest givers, or if there are multiple reward items on the floor, I still cannot pick each interaction with the "A" button.
Okay so what to do...
I know that the "A" button is also scripted for the "+up" command but it it should have been preceded with the command to activate an interface button. Looking at the command list, I thought that the command line for the "A" button might not have been properly scripted.
There are no less than 5 commands that activate your cursor on an item if you're using a mouse.
So what if we bind the A button with the above to see if it the interface bug can be worked out through scripting. The line would probably look like... (don't forget to add $$+up at the end otherwise you won't be able to fly up).
\bind Ab +<one of the activation commands above>$$+up
I will report later if my suggestion works (yes, I am still at work...) If any of you want to try it and see if you can make it work that would be great.
EDIT: There may be a variable switch at the end of the activation command line. If there is 1 will be On and 0 will be Off.
Still broke for me, but my main issue is it will no longer display the reticle of the target in front of me unless it's an enviromental object. which is very annoying I am much more interested in threats than objects.
Comments
This is great for all of us controller users!
Thank you!
Is this sarcasm? I just tried it and it is still broken...
Win XP SP 2 XBC wired ALtest Xbox drivers from MS.
All working fine I can now interact with multiple itemes by select Up on Dpad. Then Up down On Dpad to select item then A to activate and it works fine for me
I take back my thank you
But when I walked up to multiple quest givers, or if there are multiple reward items on the floor, I still cannot pick each interaction with the "A" button.
Okay so what to do...
I know that the "A" button is also scripted for the "+up" command but it it should have been preceded with the command to activate an interface button. Looking at the command list, I thought that the command line for the "A" button might not have been properly scripted.
There are no less than 5 commands that activate your cursor on an item if you're using a mouse.
InteractCursor
CursorExecute
EntityExecute
GenButtonClick
GenListActivate
So what if we bind the A button with the above to see if it the interface bug can be worked out through scripting. The line would probably look like... (don't forget to add $$+up at the end otherwise you won't be able to fly up).
\bind Ab +<one of the activation commands above>$$+up
I will report later if my suggestion works (yes, I am still at work...) If any of you want to try it and see if you can make it work that would be great.
EDIT: There may be a variable switch at the end of the activation command line. If there is 1 will be On and 0 will be Off.