Matricom Controller Suddenly Not Working

[ASittingDuck]

I have a matricom wireless controller for PC that has worked for Portal for almost a year now. All of sudden now it will not work when its emulating an Xbox controller and when I have it in its "default" mode, I can only move, I cannot change my vector of line of sight. Any Ideas how to fix this?

[A Wild Alechlo]

im getting the same issue but with a xbox 360 controller

[mediocreatbest]

SAME. It's so frustrating.

[Rei Scarlette]

This happened for me as soon as the recent 19.8 mb patch was dropped. No idea what they did there but now all of my various controllers can no longer look around with the right stick in Portal 2, and I'm also unable to access the controller area of the settings menu. The only controller I don't have access to, to see if it still works, is a Steam Controller, and I kinda don't want one. I'd talk about why, but that's going out of the scope of this topic so I'll keep to the main subject here.

Anyways, I do have some sort of solution for you! My solution (using ds4windows, but I'm sure you can do the same with most similar controller input programs) was to remap the right stick's up/left/right/down input to use mouse up/left/right/down instead. Looking around felt a bit janky, at first, but I got it to feel natural pretty quickly after tweaking my settings in ds4windows a bit.

Funny how they'd put a small patch into such an old game that promptly ends up breaking controller support, while seemingly doing little else. I still have no idea what the patch was actually intended to do. Anyways, I hope my suggested fix here will work for you as well.

[Rabbit]

I have the same issue tjoo... why did this just start?! It was working so well

[ASittingDuck]

Well I am glad that I am no the only one having this issue. I bet the reason was related to VR support. But that's just a guess. Now to figure out how to contact Valve directly about this.

[ASittingDuck]

Originally posted by ASittingDuck:

Well I am glad that I am no the only one having this issue. I bet the reason was related to VR support. But that's just a guess. Now to figure out how to contact Valve directly about this.

I just submitted a ticket to Valve directly. I hope they will actually respond but from what I have heard aboutt Steam/Valve support, I'm none too hopeful.

[ASittingDuck]

Originally posted by Reimilia Scarlet:

This happened for me as soon as the recent 19.8 mb patch was dropped. No idea what they did there but now all of my various controllers can no longer look around with the right stick in Portal 2, and I'm also unable to access the controller area of the settings menu. The only controller I don't have access to, to see if it still works, is a Steam Controller, and I kinda don't want one. I'd talk about why, but that's going out of the scope of this topic so I'll keep to the main subject here.

Anyways, I do have some sort of solution for you! My solution (using ds4windows, but I'm sure you can do the same with most similar controller input programs) was to remap the right stick's up/left/right/down input to use mouse up/left/right/down instead. Looking around felt a bit janky, at first, but I got it to feel natural pretty quickly after tweaking my settings in ds4windows a bit.

Funny how they'd put a small patch into such an old game that promptly ends up breaking controller support, while seemingly doing little else. I still have no idea what the patch was actually intended to do. Anyways, I hope my suggested fix here will work for you as well.

Thanks for the heads up, I will try that if things don't get addressed with the technical support ticket that I submitted within a week. I mean I code as well and know that this can be one of those things they weren't expecting so they wouldn't have tested it, especially on an old game. I will bet this had to do with VR control since they recently did that survey on "Rig" information and a lot the information that was collected seemed to be about VR capabilities. It would also kinda fit the bill how a VR change MIGHT make "looking around" impossible.

[Rei Scarlette]

Originally posted by ASittingDuck:

Thanks for the heads up, I will try that if things don't get addressed with the technical support ticket that I submitted within a week. I mean I code as well and know that this can be one of those things they weren't expecting so they wouldn't have tested it, especially on an old game. I will bet this had to do with VR control since they recently did that survey on "Rig" information and a lot the information that was collected seemed to be about VR capabilities. It would also kinda fit the bill how a VR change MIGHT make "looking around" impossible.

Oh, that is quite possible, now that you mention it. I hadn't thought about that, but it's a pretty likely reason why it might have happened. Thanks for that, because I was sitting here completely puzzled as to why the controls might have been affected, and VR stuff never even crossed my mind at the time.

[Crow T. Robot]

It's glitched to a Steam controller setup. The A,B,X button prompts on the main menu are the Steam controller ones and the button layout (you can access the controller menu for a split second when you first plug a controller in) shows a Steam controller rather than 360 one. That's why the right analog stick, which a steam controller doesn't have, doesn't work.

It looks like the update of Steam to handle controller config and that small game update (probably to allow Steam to take over controller config more easily) are conflicting with each other causing the game to default to a Steam controller. It's also why we can't access the in game controller options menu (except for a brief second before Steam notices a freshly plugged in controller) because it's now handled by Steam instead of the game itself.

[ASittingDuck]

Looks like they are now aware after some strong arm twisting from me (I work in tech support so the regular "its a 3rd party device" BS they TRIED to give me. . . well lets just say I know what to type to get them to get them work. They replicated the results on their side after that and say they are soon going to issue some fixes via the beta client and gave me a link for me to use. I will let you know if this helps before saying anything else.

[ASittingDuck]

Updating to the Beta Client solved the issue guys. The bug fix actually worked.