• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

Why don't more PC versions of multiplatform games support gamepads/controllers?

All the more reason that its lack of support in other areas is missing. I honestly don't get it.

I dont know, ill recheck campaign again, but i dont know why anyone would punish themselves through campaign again.....controller support is definitely there for MP, it works perfectly albeit very hard to actually get kills.
 
Because two different control schemes with two different HUDs are more expensive to develop/integrate ingame.

Full gamepad support is a NICE and important feautre, but is an EXTRA feature. Everyone who plays on PC have keyboard and mouse, but not all PC gamers have a gamepad.
In fact most PC gamers prefer to have a decent keyboard&mouse control with a proper HUD/UI even if this means not gamepad support at all.




Common mistake. Why you assume this? Keyboard and mouse are the default input controllers on PC gaming.

Not everyone wants to play sitting at a desk every single time. When the work has already been done on the console, i don't see what the excuse is. The time constraints reasoning sounds pathetic.
 
If it makes sense a game probably should support the controller. This topic is weird though, it implies that the majority of multiplat games don't support the controller when the percentage that don't is probably like 5% (after the 360 controller became standard of course).
 
Can you elaborate on this? I only spent a few hours with the open beta, but from what I recall, there were only 7 skills mappable at any given time. Xbox pad obviously has 8 readily available buttons + many secondaries (dpad, clicks, start/back). Actually, I got a sense the game had been specifically designed around controller constraints, cause it seemed so obvious that you could easily map movement to the left stick and your various abilities to the buttons/triggers/bumpers. [conspiracytheory]I suspect they know their incredibly vocal PC nerd base would go batshit if they announced console versions or launched with controller support. We all know forums would blow up about how they've neutered and limited to the game for consoles and controllers. I think they're being very smart side step that negative press by not really committing to console releases (even though we know they're coming) and approaching controller support as an (maybe) after market bonus.[/conspiracytheory]

Using ranged attacks would be difficult. I'm not saying it's impossible, just that it would require some heavy reworking, more than just replacing button prompts and calling it a day.
 
Using ranged attacks would be difficult. I'm not saying it's impossible, just that it would require some heavy reworking, more than just replacing button prompts and calling it a day.

Maybe, but ranged combat seemed like it was mostly line of sight (random by nature of moving hordes) and aoe based, not really dependent on sniping individual mobs. I can't really see it being a problem, just basic directional auto targeting like a million games before it. How did Torchlight on consoles handle it by the way?
 
I obviously played all of them with XPadder, but it's still puzzling.

How was your experience with xpadder? I've always worried that it's too janky to work in games that require aiming because games that do support gamepads often include some kind of aiming assist to make it work right but that obviously won't happen with xpadder.
 
MW3 was especially disappointing since Black Ops had it.

I personally would rather use a 360 controller with my PC games, love being able to lay in my bed and get some quality PC gaming in

Every IW COD didn't have it. You can rest assured it's supported for Blops2.
BF3 supported it for the campaing, I can see why it wasn't there for multi. New MoH will probably be the same.
Anyway, besides some competitive multi FPSs, Torchlight 1, Mass Effect series and unfortunately Amnesia (which isn't a multiplat anyway) almost every console port has pad support now.
Torchlight 2 will, and hopefully Diablo3 will get it later when the game's out on consoles.
 
People keep saying this. As of about two weeks ago (the last time I tried) it was not supported in the campaign, unless there is some hidden option to use the controller in those QTEs.

I'm not so sure why anyone is so hung up about pad support for QTEs in one of the worst FPS campaigns ever created.
 
I would guess they probably just don't feel like it's worth the effort, assuming most people just use KB+M.

That would be my guess, at least.

Was Bioware ever asked in an interview about it?
 
I'm not so sure why anyone is so hung up about pad support for QTEs in one of the worst FPS campaigns ever created.
I'm just honestly curious as it has kept me from buying a few games that I had assumed would support the controller. Didn't DICE do all the necessary work to get 100% controller support for the campaign/menus and multiplayer in the console version? What kept them from providing that same support to the PC version? Is the controller-support code just not that portable between console and PC builds?

Just reading the responses in this thread it seems that nobody has a good idea why. In some cases one could argue that the UI changes would take a non-trivial amount of work, and somebody else thought that it wouldn't be wise to advertise console support and risk a PC gamer backlash. I'm not convinced although the UI changes has some merit, provided the PC version does indeed have a different UI from the console version.
 
I would guess they probably just don't feel like it's worth the effort, assuming most people just use KB+M.

That would be my guess, at least.

Was Bioware ever asked in an interview about it?

Yes. Apparently there UI team was stretched too thin to include it.
 
I'm just honestly curious as it has kept me from buying a few games that I had assumed would support the controller. Didn't DICE do all the necessary work to get 100% controller support for the campaign/menus and multiplayer in the console version? What kept them from providing that same support to the PC version?

Just reading the responses in this thread it seems that nobody has a good idea why. In some cases one could argue that the UI changes would take a non-trivial amount of work, and somebody else thought that it wouldn't be wise to advertise console support and risk a PC gamer backlash. I'm not convinced although the UI changes has some merit, provided the PC version does indeed have a different UI from the console version.

Honestly they probably just don't it's that big of a deal. I played the campaign with a pad too and while the QTE stuff was annoying, I have a mini keyboard with a trackball I could just pick up and use when they popped up. Maybe DICE feels any PC gamer playing this with a pad is nearby some sort of kb/m device and it's not just worth the effort of implementing the pad support. Or maybe they just aren't updating the campaign at all anymore since it's not the meat and potatoes of the game.

Strange omission either way, I suppose.
 
Bioware's reasoning for not including native gamepad support was shameful. Development realities and UI team stretched too thin are ridiculous excuses when you consider their resources.

I'd like to hear DICE and IW's excuses. At this point, these games have become glaring exceptions when it comes to gamepad support.
 
Better to have no controller support in a shooter than to have mouse controls in a console port trying to emulate an analog stick. If you're gonna play on pc, just learn how to play it the right way please.
 
It also was a very shitty version of the game.
Just saying...

Anyway, I'm all for optional gamepad for multiplatform games OR for games where the gamepad fits nicely.
I'm not a zealot. I generally prefer M&K when I think it's the best, but I'm all for a controller in games where it fits (Darksiders, Batman, Dead Rising 2 and so on).
On the other hand I couldn't care less to have pad support in first person shooters, Diablo-like, RTS, and so on.
I find baffling to read people asking for pad support on a multiplayer FPS. It's like asking to be brutalized.

I came to post pretty much this.
 
Hah. I can only blame myself but I think a lot of people here are missing the question.

The question is: Why don't some PC games have the SAME level of support for the controller that their console versions have?
 
Hah. I can only blame myself but I think a lot of people here are missing the question.

The question is: Why don't some PC games have the SAME level of support for the controller that their console versions have?

Because the rest of your computer is controlled via keyboard and mouse, not a controller. therefore, you are expected to not only have them, but know how to use them on a pc. The same cannot be said for a controller.
 
Hah. I can only blame myself but I think a lot of people here are missing the question.

The question is: Why don't some PC games have the SAME level of support for the controller that their console versions have?

Every single console game has to have complete controller support. On PC, Keyboard and Mouse are the primary input devices and controllers are secondary. Gamepad support has come a long long long way but, there are and, will likely always be, some exceptions because gamepad support is not considered a necessity.

Also, some genres (Diablo style RPGs, point and click adventure games and RPGs, MMOs, RTSes and other strategy games) are going to require much more work to come up with a usable control scheme on gamepads and it's often not worth implementing.
 
I don't know if this has been mentioned already, but some games the lack of gamepad support makes NO sense. Mass Effect 2 on the PC pretty much has all the required coding and assets to allow gamepad support, they just decided to not allow it. A simple change to a config file in the game enables most of the same functionality of the xbox 360 version though. It even has the Xbox controller button images in the game. Seriously, WTF bioware?
 
Because the rest of your computer is controlled via keyboard and mouse, not a controller. therefore, you are expected to not only have them, but know how to use them on a pc. The same cannot be said for a controller.
They already did the work to give the game controller support (PS3 and 360 versions) didn't they?

What is that kept them from just plugging that into the PC version as well? Hell, BF3's PC version supports it for everything but QTEs.

I don't know if this has been mentioned already, but some games the lack of gamepad support makes NO sense. Mass Effect 2 on the PC pretty much has all the required coding and assets to allow gamepad support, they just decided to not allow it. A simple change to a config file in the game enables most of the same functionality of the xbox 360 version though. It even has the Xbox controller button images in the game. Seriously, WTF bioware?
This is exactly what I'm asking about ;P
 
People keep saying this. As of about two weeks ago (the last time I tried) it was not supported in the campaign, unless there is some hidden option to use the controller in those QTEs.

Because it's true. I've played it that way. Although on-screen prompts (qte, pick up weapons..) keep showing up as kb controls.
I didn't have to change anything iirc, just had my wireless 360 pad turned on ( 360 pad is the only one supported afaik) before launching the game. If you want I can have a look at the options if I've changed anything, didn't touch the ini and such anyway.
 
Because it's true. I've played it that way. Although in-screen prompts keep showing up as kb controls.
I didn't have to change anything iirc, just had my wireless 360 pad turned on ( 360 pad is the only one supported afaik) before launching the game. If you want I can have a look at the options if I've changed anything, didn't touch the ini and such anyway.
So you were able to use the controller in the QTEs? I know the prompts are all keyboard/mouse based, which is the case with a lot of games, but unlike those other games I could use the equivalent controller button or trigger. That's never worked for me in BF3.
 
Oh man, I don't even want to contemplate playing Diablo or Torchlight with a gamepad. I dunno how you guys do it but it would infuriate me I reckon.
 
Oh man, I don't even want to contemplate playing Diablo or Torchlight with a gamepad. I dunno how you guys do it but it would infuriate me I reckon.
Torchlight is great with a pad. Have you ever tried it? You might be surprised at just how well it works.
 
Apparently its more work than whoever it is who's porting the game will commit to. they probably give it to the pc guys at the last possible second and say good luck, do what you can before launch. they might have denied them access to controller support assets as well, thinking they weren't relevant. I don't think anyone else will speak for them.
 
So you were able to use the controller in the QTEs? I know the prompts are all keyboard/mouse based, which is the case with a lot of games, but unlike those other games I could use the equivalent controller button or trigger. That's never worked for me in BF3.

Just tried it out. The controller still doesn't work during QTE's.
 
Just tried it out. The controller still doesn't work during QTE's.
Thanks. I couldn't test while I'm here at work, but its good to have this settled.

And to be honest, the last time I tried was a few days ago but I couldn't start up the campaign because Origin was down for maintenance. Modern gaming, I tell ya.
 
They already did the work to give the game controller support (PS3 and 360 versions) didn't they?

What is that kept them from just plugging that into the PC version as well? Hell, BF3's PC version supports it for everything but QTEs.


This is exactly what I'm asking about ;P
Probably different API's.
 
How was your experience with xpadder? I've always worried that it's too janky to work in games that require aiming because games that do support gamepads often include some kind of aiming assist to make it work right but that obviously won't happen with xpadder.
There's no aim assist in most FPS games, but if you're an experienced gamer, you'll still blast through these types of games, it shouldn't really be a problem even on harder difficulties. But I'm the kind of guy who usually disables them in console games if they allow that, so ymmv.

That said, you can tweak every aspect of your analogues and triggers, from deadzones to sensitivity - much more thoroughly and precise than any in-game sliders I've seen - so if you're unhappy with the default setup, there's always ways to make it work to your liking.


edit: now that I think of it, I can't remember which game it was, but I think one of the two FPS we're talking about also had some snap-on aim assist in the PC version. I remember making a note of that.
 
So you were able to use the controller in the QTEs? I know the prompts are all keyboard/mouse based, which is the case with a lot of games, but unlike those other games I could use the equivalent controller button or trigger. That's never worked for me in BF3.

Nope, I meant to say that you have to stick to the kb prompts. It's annoying. Other than that, the pad works (sp), I was referring to the "pad it's not supported in the compaign" point of your post.
 
Better to have no controller support in a shooter than to have mouse controls in a console port trying to emulate an analog stick. If you're gonna play on pc, just learn how to play it the right way please.

"The PC has a world of options, modifications, and tweaks, but you can't use any input method you want, that's just silly"
 
Torchlight is great with a pad. Have you ever tried it? You might be surprised at just how well it works.

How in the hell do you target specific things across the screen for ranged attacks? Does it give you a cursor or something?

I can see a gamepad working for melee classes, but no clue how you can have the proper accuracy to play a ranged class.
 
I am maybe the only one here but I think ME3 controls better with M/KW.

If a game involves any sort of aiming, I will be using KB/M every time. If I try to play them with a controller I spend more time fighting with the sticks trying to aim than actually enjoying myself.
 
How in the hell do you target specific things across the screen for ranged attacks? Does it give you a cursor or something?

I can see a gamepad working for melee classes, but no clue how you can have the proper accuracy to play a ranged class.
You aim where you're pointing, and there is soft auto-targeting. The only thing missing from the console version was the ability to swap between armor sets as far as I know.

Nope, I meant to say that you have to stick to the kb prompts. It's annoying. Other than that, the pad works (sp), I was referring to the "pad it's not supported in the compaign" point of your post.
As somebody who PC games from my couch, switching from controller to keyboard/mouse just for QTEs just isn't going to happen for me so I don't consider the campaign as "controller supported". Now I know zoku88 above suggested that there are probably different APIs to code against for controllers on the PC, but in the case of BF3 that still doesn't answer the question, since the controller works for everything but QTEs. I'm honestly flabbergasted that Dice didn't rectify such a small problem in their latest mega-patch.
 
If a game involves any sort of aiming, I will be using KB/M every time. If I try to play them with a controller I spend more time fighting with the sticks trying to aim than actually enjoying myself.

I think almost all games control better with M/KW with the possible exception of CAPCOM games for some reason.
 
I ended up gettin used to playing with a trackball for mouse and using a wireless keyboard. Then I attached a USB extension cable to the trackball. So now I still PC game on my couch in front of the 65" monitor.

Still would like controller support for PC games. I personally think the PS1 version of Magic Carpet is superior to the GOG mouse/keyboard version for example.

How hard could it be?
 
Count me in on being disappointed that BF3 didn't have proper controller support. I just wanted to chill on my couch and play it with all the setting maxed proper. I thought it was something I wasn't doing right when I came to the very first QTE. I'm still boggled by the lack of controller support for any of the Mass Effect series. I guess it's a good thing as I would have probably double dipped if it did. It seems like such a wasted opportunity to not include support for something YOU HAVE ALREADY INCLUDED SUPPORT FOR. I mean it's not like the resources haven't already been allocated to doing it, what's to stop it from being included? I would never trade M/Kb for Online multiplayer, but for single player? why not? I vastly appreciate when devs give me the choice to use a controller. Though on the same page I hate when proper M/Kb support is gimped because it's a console port too. I think DE:HR did a great job, best of both.
 
Top Bottom