323 replies to this topic

[Sir Roland MXIII]

Paul Inouye, on 06 November 2013 - 12:04 PM, said:

1) No.

2)

3) We are adding the ability to bind MB1 to "fire selected weapon group" but it's requiring a bit of trickery on the control binding end of things. We have engineering working on it right now and as soon as that is fixed, the bind will be available to you all again. Sorry for the inconvenience but this was something we did after watching new players have a problem with the current implementation.

That's a hell of a word to use to describe us. Especially given the potential loss of profits for PGI that it fails to imply. Still. Thanks for not ejecting myself and others out of MechWarrior with this tomfoolery. Seriously Paul, next time DO NOT REMOVE AN OPTION, just make it non default and call it a day, FFS!

EDIT Last sentence needed something to make it a little less likely to be ignored.

Edited by miSs, 06 November 2013 - 12:30 PM.
nope.

[KHETTI]

You know paul, a simple heads-up previous to this happening could have saved a whole lot of grief.
As it stands i currently no longer have an install of MWO, and to be honest i'm not sure i want to go through installing it again.
Completely unessessary drama and inconvienience that could have been avoided with a single paragraph.

[NuclearPanda]

Sir Roland MXIII, on 06 November 2013 - 12:24 PM, said:

That's a hell of a word to use to describe us. Especially given the potential loss of profits for PGI that it fails to imply. Still. Thanks for not ejecting myself and others out of MechWarrior with this tomfoolery. Seriously Paul, next time DO NOT REMOVE AN OPTION, just make it non default and call it a day, FFS!

EDIT Last sentence needed something to make it a little less likely to be ignored.

Wow man, you should really chill out to be honest. Just saying. They're working on fixing it, there's no reason to freak out!

[Sir Roland MXIII]

KHETTI, on 06 November 2013 - 12:25 PM, said:

You know paul, a simple heads-up previous to this happening could have saved a whole lot of grief.
As it stands i currently no longer have an install of MWO, and to be honest i'm not sure i want to go through installing it again.
Completely unessessary drama and inconvienience that could have been avoided with a single paragraph.

Good lord, no frakking kidding. This has just been without a doubt the most idiotic thing I've ever seen them do.

[Bodach]

How is it that big an issue since you just removed it?

[moneyBURNER]

While I appreciate Paul's response, not only does the explanation not restore my faith, but it shakes my confidence completely because now there's no telling what they can break next, given how little they understand the implications of such minor but critical changes. How could they not forsee our reaction, or the inconsistency of design with other interface features?

I'm also wondering why they just couldn't change the default binding for M1 if it was such a problem for new players, and leave the original binding empty instead of removing it.

It's shocking.

[Roadbeer]

Which brings up my question about when it's going to be fixed.

This is literally a game breaker for a lot of people, people who are burning premium time waiting for it to be fixed.

Now back in "BETA" this wasn't a big deal, because you could expect things like this, and it could be argued that you rolled the dice spending money on something that was "Under development" and subject to change. But now that we're "LIVE", the developer does have some responsibilities for compensation when they pull off stunts like this.

Edited by Roadbeer, 06 November 2013 - 12:51 PM.

[fiStfiRE]

Rumor: NOV 2013 PGI Headquarter is surrounded by DEA Enforcements since the begin of they're glory 2013 Halloween Party, heavy smoke, fighting sound and lightning confuse DEA, so they stay back and call for heavy armored Support. PGI release the Patch without checking the code to save they're hard work. DEA cutoff all PGI Communication lines...

We don't need to know what they smoke or take on this Party, but for sure the next Party is much smaller, if PGI don't show any reaction to 200+ Posts from paying Players.

I still hope PGI say "it's a Bug, we don't want to remove fire selected Weapon Group completely". Nobody loose his face this way, all would be fine.

Battletech is always complicate for new Players. Rules are complex but well balanced and exactly this makes Battletech one of the most exiting Games. Any change to Rules can break the Game, we understand all Changes to balance this Game.

The remove of "fire selected Weapon Group" without any need, and no advance for any balanced Mechconfig in Universe is the most stupid "Rule" change in my over 20 Years of Battletech Tabletop, Mechwarrior, BT3025 History.

This fire mode is so basic for many Players, you cant remove it.

EDIT: I don't see Pauls post, We've got some hope!

Edited by fiStfiRE, 06 November 2013 - 01:15 PM.

[Kunae]

I expect that UI 2.0 will be launched without a paper-doll, in the mechlab.

[Jakob Knight]

Translation: While watching players who are playing their first game without the benefit of a Game Manual to explain to them how to do things, we noticed they were having some problems with weapon groupings. Thus, without stopping to think things through about the full ramifications, we decided to simplify the game to keep those new players from feeling bad. In the future, we intend to code the option to map this function back in, but it isn't a priority at the moment as we don't know how to do that yet.

Sounds like business as usual for PGI. Maybe someday they might actually be able to learn that thinking things through before doing them is a good idea (3PV anyone?).

Edit: And people say this is giving back their confidence in the Devs? If anything, it should make them wonder what else they will do away with whenever they see a new player having problems.

Edited by Jakob Knight, 06 November 2013 - 01:14 PM.

[Nation Uprise]

Paul Inouye, on 06 November 2013 - 12:04 PM, said:

We are adding the ability to bind MB1 to "fire selected weapon group" but it's requiring a bit of trickery on the control binding end of things. We have engineering working on it right now and as soon as that is fixed, the bind will be available to you all again. Sorry for the inconvenience but this was something we did after watching new players have a problem with the current implementation.

I don't understand. How was it working incorrectly before? It was as simple and straight forward as anything could be. You want to shoot the currently selected weapon group, you press that button. You want to shoot every other weapon group without selecting a specific one, you press the appropriate button. So whats wrong here? Based on the explanation for removal, I would think renaming the fuction or moving the fuction would be an easier thing to do instead of removing and rebuilding code that seems to have worked from the beginning.

[Roadbeer]

Nation Uprise, on 06 November 2013 - 01:13 PM, said:

I don't understand. How was it working incorrectly before? It was as simple and straight forward as anything could be. You want to shoot the currently selected weapon group, you press that button. You want to shoot every other weapon group without selecting a specific one, you press the appropriate button. So whats wrong here? Based on the explanation for removal, I would think renaming the fuction or moving the fuction would be an easier thing to do instead of removing and rebuilding code that seems to have worked from the beginning.

[DavrosDalek]

Paul,

Your new players are not your only concern here.

[XphR]

Do we need to start requesting other features we currently use also stay available with incoming new users not knowing they are available or how to use them?

Despite multiple slaps to the face, a laughable path of pro(re)gression and a lack of PR controll I continue to inject funding in "good faith" to a degree that is becoming more and more difficult to defend..

You guys could really benefit from reeling in the lines and taking inventory of the nets.

[fiStfiRE]

Paul Inouye, on 06 November 2013 - 12:04 PM, said:

3) We are adding the ability to bind MB1 to "fire selected weapon group" but it's requiring a bit of trickery on the control binding end of things. We have engineering working on it right now and as soon as that is fixed, the bind will be available to you all again. Sorry for the inconvenience but this was something we did after watching new players have a problem with the current implementation.

Why don't allow to bind "fire selected weapon group" to MB2 if this is more easy to code? ATM I only can play Boats without binding.

[Grave Dancer]

Bodach, on 06 November 2013 - 12:39 PM, said:

How is it that big an issue since you just removed it?

Because apparently their release process doesnt include this little thing we in the industry like to call "Roll-back". If it did, the sensible thing to do would be to roll back that code until a PROPER fix to the new player issue could be implemented (in other words... remapping the default bind for mb1 without completely removing the option to bind to what it used to be bound to).

[ShadowSpirit]

Paul Inouye, on 06 November 2013 - 12:04 PM, said:

1) No.

2)

3) We are adding the ability to bind MB1 to "fire selected weapon group" but it's requiring a bit of trickery on the control binding end of things. We have engineering working on it right now and as soon as that is fixed, the bind will be available to you all again. Sorry for the inconvenience but this was something we did after watching new players have a problem with the current implementation.

New players having problems? Sorry but new players ... always have problems with new games. It's called "read the manual", "read the forums", or "watch the tutorial video."

You are throwing the baby out with the bath water again.

[caseysrevenge]

Yeh paul we are not mindreaders you know.

[ShadowSpirit]

NuclearPanda, on 06 November 2013 - 12:27 PM, said:

Wow man, you should really chill out to be honest. Just saying. They're working on fixing it, there's no reason to freak out!

That attitude is precisely why this game is mediocre .... at best.

[Roadbeer]

I suggest everyone who is burning premium time while this is being resolved send in support requests for reimbursements on premium time for the period that they are unable to play.