Turning off the Xbox controller auto-configuration solved this issue, but did not solve my issue within Castle Crashers. Something interesting that I DID find (stay with me here), I was trying to map the controllers manually within steam's Big Picture in hopes that perhaps steam could act as a middleman that might tell Castle Crashers which controller is one and which is two, except big picture instead detected my controllers and mapped all of the inputs directly to one, so when I pressed up on one controller it would think both controllers were sending the up input, skipping boxes. I also tried a fresh install of the game and the same issue rose. Last night I did verify the game files, and it detected and retrieved on bad file, yet it still didn't work. This was the first thing I tried, because the wireless receiver randomly disconnects the second controller when two are connected, so I figured that new batteries may solve the issue, however I still experience the disconnects and so since then I've been running one wireless controller and one cabled controller (or both cabled if a game gets confused). My PC is still able to detect activity from the controllers in other games and I'm able to map them in other games.Ĥ. I've tried multiple, yet I still experience the issue. I've tried every combination possible in terms of connecting prior to and after launching the game (so, yes)ģ. I apologize to have come across such an anomaly! Your questions:Ģ. I have some other ideas but lets address these first. Have you tried different USB cables? Those cables can sometimes go bad.ĭo both controllers have fresh batteries in them when you connect wirelessly? When you connect the controllers via USB, do you connect them before starting Castle Crashers? Which version of Windows are you running? We have tried this several times here in our office and are not experiencing this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |