125 réponses à ce sujet

[DarkAmaranth1966]

I still don't see how the KBM controls are THAT different form any other RPG /combat game. Yes the FUNCTIONALITY of those controls needs work, Hold for example) but the actual controls to issue the commands are fine.

 

What do you want? Mouse button for fire and wheel for walk and the game randomly chooses what ability to fire with? What is so bad about pressing letters, or using the mouse to move and, pressing numbers to activate abilities? It isn't like you can't remap them to whatever keys suit you.

[Damazig]

posted this on another section already but here it is.

 

All these months and still, walk ability for pc mouse and keyboard users only comes out now, and still all the other major keyboard and mouse UI problems remain... A shame Bioware turned away from the players and the platform that made them great, and to make it worse, lie about it saying and advertised it was thought and developed with the PC in mind. I didn't enjoy what Bioware did with Dragon Age 2, coming from the brilliant game that Origins was for me, I really disliked Mass Effect 3 ending, and then this... Dragon Age Inquisition, a game I was still able to really enjoy, but I'm done giving my money to this company that flat out lies about the game being made specifically with the PC in mind, and then we all saw what happened. 

 

And it takes them 2 months to get a patch so that PC mouse and keyboard players can have a feature that console and gamepad/controller already had this entire time... the ability to walk.

 

Oh the good old Bioware days, games and Doctors... sorely missed.

 

No more buying Bioware games from me.

[deathhawk2]

The problem with saying that in 2 months they have only did this much, you have to remember that they were off for a good portion of December, I could understand this reasoning if during those 2 months, one of them wasn't there Christmas break.

[Damazig]

The problem with saying that in 2 months they have only did this much, you have to remember that they were off for a good portion of December, I could understand this reasoning if during those 2 months, one of them wasn't there Christmas break.

So wait, a big product comes out, and lets cut them some slack on fixing it, cause it holidays, so everyone should have a 2 month break? I sure wish I worked in a company with those politics concerning time off!

 

In any case, the biggest point of my post wasn't even/just that.

[In Exile]

So wait, a big product comes out, and lets cut them some slack on fixing it, cause it holidays, so everyone should have a 2 month break? I sure wish I worked in a company with those politics concerning time off!

 

In any case, the biggest point of my post wasn't even/just that.

 

That you have a terrible work environment doesn't mean that Bioware should also have a similarly terrible environment. 

[Damazig]

Yeah yeah Bioware is supposed to have great working conditions, but no entire teams has a 2 month time off anywhere. The game wasn't thought out for PC, and it got patched too slow, still has tons of problems, and new ones at that(0 armor shields?). 

[In Exile]

Yeah yeah Bioware is supposed to have great working conditions, but no entire teams has a 2 month time off anywhere. The game wasn't thought out for PC, and it got patched too slow, still has tons of problems, and new ones at that(0 armor shields?). 

 

I don't know why you think a few weeks off during the holiday break translates into 2 months of off-time. Patches take a substantial amount of time to get out of the game, particularly for the hardware combinations Bioware has to deal with (old gen., new gen., PC). 

 

As to Patch 3, the armor issue on shields is a visual bug only. It doesn't affect newly crafted shields, and I've tested shields in combat and the damage mitigation is there. 

[JaegerBane]

The problem with saying that in 2 months they have only did this much, you have to remember that they were off for a good portion of December, I could understand this reasoning if during those 2 months, one of them wasn't there Christmas break.

I'd take your point if the patch fixed a single issue, or was broken itself - but there isn't any excuse for releasing a patch which breaks features in the base game. That goes for any software.

As to Patch 3, the armor issue on shields is a visual bug only. It doesn't affect newly crafted shields, and I've tested shields in combat and the damage mitigation is there.

[Jaron Oberyn]

I'd take your point if the patch fixed a single issue, or was broken itself - but there isn't any excuse for releasing a patch which breaks features in the base game. That goes for any software.

Maybe you haven't been in the announcements forum for the bast month and a half, but there was an angry mob demanding the patch come out asap, with little to no regard to the process involved in making a successful patch. So once again, as with the deployment of P2, Bioware succumbs to the masses who complain about waiting and we get a half baked patch. You can't have your cake and eat it to. People need to understand that fixing bugs isn't as simple as toggling a switch, the solution for a bug could introduce 1 or more other bugs as we have seen in P2 and now P3. This is a large part of why patches take so long, yet people want everything now - and then complain when Bioware does just that. No matter what they do, they just can't win with some people. Take a long time to ensure a successful patch, criticized by angry mob. Rush a quick patch to appease angry mob, criticized by said mob. 

[Biotic Flash Kick]

Maybe you haven't been in the announcements forum for the bast month and a half, but there was an angry mob demanding the patch come out asap, with little to no regard to the process involved in making a successful patch. So once again, as with the deployment of P2, Bioware succumbs to the masses who complain about waiting and we get a half baked patch. You can't have your cake and eat it to. People need to understand that fixing bugs isn't as simple as toggling a switch, the solution for a bug could introduce 1 or more other bugs as we have seen in P2 and now P3. This is a large part of why patches take so long, yet people want everything now - and then complain when Bioware does just that. No matter what they do, they just can't win with some people. Take a long time to ensure a successful patch, criticized by angry mob. Rush a quick patch to appease angry mob, criticized by said mob. 

Well **** about giving the game extra time?

 

2 months of QA and polish would have done this game wonders.

Hell, if this game started out as single player campaign maybe it would even have been better 

it makes me wonder

 

is the single player story tacked on? or is it the multiplayer that is tacked on? 

[DarkAmaranth1966]

No, the whole team would not have had 2 months off, but the senior personnel that have to approve the release of patches could easily have had 4 weeks (possibly more) off so, even though the peons could do the work, it couldn't be approved for release until the senior personnel came back.

 

What they need is volunteer alpha and beta testers. Alpha should get the game they test free and, Beta a 40 or 50% discount (or gift card code for that amount) That would cost very little and, get the game onto different systems with different configurations, different internet connections and so on that may or may not be optimal for the game. They'd find a lot more bugs pre release that way and, the same testers can test patches too. It isn't a big deal to have the testers sign a DND (Do Not Disclose) agreement - I've done so for 2 games I test and all I get is either free DLC, a discount on expansions or, unique in game items that only testers get. (Like test a full DLC pack and get a weapon with slightly less than BiS stats for my main toon to use.) Suits me, I have fun testing, seeing the sometimes wacky bugs, trying out everything to find exploits and, chatting with the devs and, it gives me a greater appreciation and understanding of the game as well as letting me make suggestions when they have to make last minute in game changes. Bioware/EA needs players to test for them - better game that way and, little cost to them for us to do it.

[archav3n]

posted this on another section already but here it is.

 

All these months and still, walk ability for pc mouse and keyboard users only comes out now, and still all the other major keyboard and mouse UI problems remain... A shame Bioware turned away from the players and the platform that made them great, and to make it worse, lie about it saying and advertised it was thought and developed with the PC in mind. I didn't enjoy what Bioware did with Dragon Age 2, coming from the brilliant game that Origins was for me, I really disliked Mass Effect 3 ending, and then this... Dragon Age Inquisition, a game I was still able to really enjoy, but I'm done giving my money to this company that flat out lies about the game being made specifically with the PC in mind, and then we all saw what happened. 

 

And it takes them 2 months to get a patch so that PC mouse and keyboard players can have a feature that console and gamepad/controller already had this entire time... the ability to walk.

 

Oh the good old Bioware days, games and Doctors... sorely missed.

 

No more buying Bioware games from me.

 

I think Bioware staff are mostly console fans themselves and been playing on controllers from Day 1 to now. Otherwise they wouldn't have not notice the clunky controls on PC would they? I mean .. really? Right click 90% time to control the camera? Maneuvering obstacles during Tac-Cam? Indoor Tac-Cam? Irresponsive Dialogue Wheel when using the mouse?

[DarkAmaranth1966]

I assume they mostly use controllers on the PC even. Most techies (like the devs) are younger and learned to game with controllers. They probably don't have many that actually play the game on PC using KBM, and I doubt any that find controllers confusing and frustrating so refuse to use them. They didn't account for the PC players that bought the PC version because we hate controllers.

 

The controls are fine, it's the way those controls function that is a problem. I don't mind the mouse look requiring you to hold a button (I disable auto look in games if possible anyway as I dislike it.) WASD is standard, numbers for abilities and F keys for party select, standard stuff. So the actual controls are fine but, how the game responds to some of them needs attention.

[DragonAgeLegend]

Honestly the controls I want for DAI would be the same that was used on the last DA games. Left click to attack, Right click to move the camera, auto attack, a goddamn tooltip on the skills in the bar, and auto run to loot. What would make it better is if we could have more then 8 abilities on the bar but that could be slightly pushing it. We don't want a complete overhaul of the system.

Also in tac cam, I would prefer it if I press the A or D keys that the camera moves in that direction and does not rotate instead like it does at the moment.

[atlantico]

Truth be told, my keyboard mappings aren't far off the scheme I used for the mass effect games. That's what is presumably getting everyone into a nerdrage.... I haven't played DA:O for ages but IIRC it controlled like KOTOR.

Actually DA:I controls more like KotOR sans tac-cam. The nerdrage is mostly because DA:I is ... bland and kinda buggy with a poor mouse/keyboard interface. And a stupid UI. And a multitude of larger or smaller inane design decisions. Few weapon models. Few armor models. And so on and so fort, things that I'd categorize under "blandness".

 

But made for consoles isn't always terrible, as in the aforementioned KotOR, which was 100% made for consoles, and yet the keyboard and mouse interface worked very well. The UI of that game was not good. It was optimized for consoles, but not so badly that it felt completely out of place on PCs. On PCs it just looked and felt clunky, but not out of place. A lot of things on PCs look pretty clunky.

 

However, I mentioned that I wasn't disappointed with patch 3, and well, I'm not - but I am disappointed with the shield bug it introduced, where my crafted shields all have zero defense value out of the blue. 

 

A hotfix may be in order.

[Aurok]

The horse is a speck in the distance now anyway. The time to get the game to a reasonable standard on all platforms & control schemes was before it came out.

[bzombo]

Please compose yourself and do not be rude. I am not acting like "it's easy", I'm merely expressing my disappointment that I have yet to see a patch to address the PC controls that they said they would address. We've been waiting a few months now which is even more worrisome. Most people are waiting for this to start a new play through, my self included.

Which means you've already played the game.  You can play again as it is now or wait. You want Bioware to change the pc controls from what they decided to do. For that, you'll wait as long as it takes. It's not super easy to create a patch as complex as changing the controls, let alone for only one platform that doesn't even drive most of the sales.

[Gaz83]

Yeah, I'm probably going to skip this when it hits consoles. Not only does it fail to solve major issues, but it's priorities are all out of whack. Getting rid of the dupe glitch is one of their key concerns? Really? I can only assume they plan on selling us crafting gear further down the line as DLC. After all, they never bothered patching it out of previous entries, and there are no leaderboards losing their integrities. If later patches add in essential fixes, I'll relent. Until then? I'll pass. Best set up a few new game saves then, for world state reasons. 

[Giantdeathrobot]

Oh for the love of Bhaal.

 

Just because you have gotten used to something doesn't mean that mechanic isn't inherently flawed. Let's take needing to hold the mouse button to move as an example. To use the universally-loathed metaphor of cars: imagine that you have to use both feet whenever you want to brake or accelerate. Is it possible to drive using both feet at the same time to brake or accelerate? Yes, of course. But should it be necessary? Is it inefficient and indicative of poor design? Will driving like that for extended periods tire you out more than is necessary? Absolutely.

 

It is because so many of you are so complacent with mediocrity and poor design that developers keep giving us exactly that. Bioware has clearly designed this game for consoles and is giving you, the PC gamer, the middle finger. Despite that, you just smile and go merrily on your way. It would be like going to a Starbucks and watching the barrista spit into your cup, then taking it and gulping down with a smile on your face. Open your eyes and get a clue. People like me are tired of giving them to you.

 

Uh, you can move with WASD? 

[Captain Wiseass]

[sarcasm]Sure, if you want to be a plebe.[/sarcasm]

 

Really, the things some people will go Dowager Countess over never cease to amaze me.

[JaegerBane]

Maybe you haven't been in the announcements forum for the bast month and a half, but there was an angry mob demanding the patch come out asap, with little to no regard to the process involved in making a successful patch. So once again, as with the deployment of P2, Bioware succumbs to the masses who complain about waiting and we get a half baked patch. You can't have your cake and eat it to. People need to understand that fixing bugs isn't as simple as toggling a switch, the solution for a bug could introduce 1 or more other bugs as we have seen in P2 and now P3. This is a large part of why patches take so long, yet people want everything now - and then complain when Bioware does just that. No matter what they do, they just can't win with some people. Take a long time to ensure a successful patch, criticized by angry mob. Rush a quick patch to appease angry mob, criticized by said mob.

I've dipped in and out but typically don't spend too much time on there, it can get a bit toxic at times.

However, while I'm sure the majority of whiners haven't got the slightest idea what kind of effort was required to get a patch out of the door, in most software that has any design whatsoever, it's relatively easy to make sure a patch does not directly break currently functional features in the software. It can have unintended side effects and the fixes it makes can fall over, but actually hitting elements of the software that have nothing to do with the patch implies there were some dangling elements going on there.

I agree they've probably rushed it because of the whiners, and patching something that is broken can be downright infuriating, but they do have a certain responsibility to thoroughly test what they roll - it's only going to create more work for them if they don't.

[unclee]

ITT: every PC player on the BSN is a veteran game developer that knows exactly what goes into finding, fixing, testing and release patches/bug fixes.

 

Whose to say they didn't try fixing/changing some of the things people are disappointed with but found that they caused additional issues with the game? Would you have rather they addressed your disappointment at the expense of new bugs/glitches? People here seem to want to have their cake and eat it too.

 

I shouldn't be shocked though. Had they "fixed" some of the things that one group say need to be fixed, they'd have just pissed off another group of users because they didn't address THEIR needs. They can't win either way.

 

I'm sure most people will think I'm blindly defending Bioware, but I'm not. They released a game that crashed often and it's taken multiple patches to start to get right. They should rightly be taken to town on that one. What I'm not going to do is get upset because they're prioritizing bug fixes over feature requests (which any software developer worth their salt would do). For those looking for fixes to actual bugs (like the 0 armor one), then you've got legitimate complaints. Those looking for feature requests? You'll need to wait in line until after bug fixes (won't stop people from complaining though).

[Shryke]

So why doesn't Bioware come out and say as much? Indie developers communicate about things like this all the time. "We can't implement this feature very easily because it breaks this feature. But we'll keep working on it...", etc. Bioware has been absolutely terrible at communicating to its community. Tell us you are not easily able to implement click-to-open-container or some other oft-requested feature and we will make every effort to understand.

[pdusen]

Tell us you are not easily able to implement click-to-open-container or some other oft-requested feature and we will make every effort to understand.

 

Based on what I've seen on the BSN, I find that very, very unlikely.

[Shryke]

Well we'll never know, will we?