162 replies to this topic

[MaddMaxx]

Aethon, on 08 April 2013 - 11:43 AM, said:

How about allowing us to stop our premium time, since we keep getting matches with no HUD, no IFF indicators, no capture indicators, and no map? No map/capture indicators may sound minor, but it makes Conquest a pain.

Allowing us to stop our premium time until the HUD is fixed would be a nice gesture on PGI's part.

Not picking on you here but your request is "flawed" at a fundamental level. If for even one instant, the Dev could be assured that no one would abuse it, as in, unless it could be guaranteed that "everyone" who wanted it turned off, would in fact turn it back on when the "fix" was in, then it makes little sense to even ask for it.

Besides, not everyone is having enough of these issues to warrant "turning off" anything.

Edited by MaddMaxx, 08 April 2013 - 12:48 PM.

[Garth Erlam]

l4Dl, on 08 April 2013 - 11:49 AM, said:

Sorry to quote you Garth, but, If you want this perfect, send me a copy of the current source code (.h, .cpp) files for the HUD functions.
I'll also need the areas in the main code where you call these functions on loading/updating states etc.

I'd be willing to debug the issue for you, shouldnt take too long.
I take its a class function in C++?

If you want it perfect, .lua script isnt the way to go for performance/stability or future implementations.

Happy to help, and with no cost to PGi.

Oh, sure, I'll just 'send' you the codebase for the game.

Since we're making ridiculous claims, the Cicada should have 12 energy slots, also you need to pay money directly to my bank account so I can remove the code that'll cause you to crash on load. GIANT SMILEY FACE

[Team Leader]

Garth Erlam, on 08 April 2013 - 12:47 PM, said:

Oh, sure, I'll just 'send' you the codebase for the game.

Since we're making ridiculous claims, the Cicada should have 12 energy slots, also you need to pay money directly to my bank account so I can remove the code that'll cause you to crash on load. GIANT SMILEY FACE

Since we are making ridiculous claims, can we get viable MGs?

[OuttaAmmo NoWai]

You just gotta be patient. I'm a software engineer, man. I've seen some sh#t.

The development process is maddening, and that's ASSUMING you can work well with your team.

Try coding in Mainframe Assembler for 30 seconds and you immediately appreciate PGI for all they've done.

[MrPenguin]

Team Leader, on 08 April 2013 - 12:50 PM, said:

Since we are making ridiculous claims, can we get viable MGs?

[Gallowglas]

Alois Hammer, on 08 April 2013 - 12:46 PM, said:

Because developer whose biggest title so far was Duke Nukem Forever.

And big, wildly successful game companies like Blizzard NEVER have bugs that take a long time to hammer out and about which the player base becomes extremely impatient...right?

Oh, wait...

Edited by Gallowglas, 08 April 2013 - 01:11 PM.

[Franchi]

Gallowglas, on 08 April 2013 - 01:07 PM, said:

And big, wildly successful game companies like Blizzard NEVER have bugs that take a long time to hammer out and about which the player base becomes extremely impatient...right?

Oh, wait...

Yeah cause as a long time blizzard player I have totally had times where the game was unplayable for 4-5 days at a time.

OH WAIT..............

[Roadbeer]

Franchi, on 08 April 2013 - 01:14 PM, said:

Yeah cause as a long time blizzard player I have totally had times where the game was unplayable for 4-5 days at a time.

OH WAIT..............

YMMV
I'm currently having no problems at the moment.

Can you say with certainty that while you had a stable experience with a Blizzard title, that someone else didn't?

[Franchi]

Roadbeer, on 08 April 2013 - 01:17 PM, said:

YMMV
I'm currently having no problems at the moment.

Can you say with certainty that while you had a stable experience with a Blizzard title, that someone else didn't?

I had a stable experience with blizzard games and games from half a dozen other publishers, running a 5 year old PC with out of date drivers on a graphics card that could hardly be called a graphics card.

If you want to cause problems with blizzard games you generally have to work at it, and game breaking bugs in my EXP are patched within 3 days, typically less if it is affecting a large number of clients.Now I never did play D3, so maybe that was a bug fest, but we all knew it was going to be a POS before it released.

Now lets compare to the rig this game is having issues with, less than a year old custom PC with well over $1000 in hardware, so much in fact I stopped adding it up, most up to date drivers and in better than 75% of games I have one or more bugs, this PC has no trouble with ANY OTHER GAME, and runs them all at high or ultra with better FPS than it can run this game on low.


Sorry PGI its not my hardware, its your software, or should I say MALWARE.

Edited by Franchi, 08 April 2013 - 01:31 PM.

[Roadbeer]

Franchi, on 08 April 2013 - 01:25 PM, said:

{lots of words}

And how many programmers do you think work on your average Blizzard title? How much revenue do they have to draw from?

You are comparing a start up "mom & pop" to Wal*Mart. I remember the first few games that Blizzard put out, not exactly the text book definition of stability, even after launch, and there were MUCH, MUCH fewer available hardware configurations at the time.

[MrPenguin]

Franchi, on 08 April 2013 - 01:14 PM, said:

Yeah cause as a long time blizzard player I have totally had times where the game was unplayable for 4-5 days at a time.

OH WAIT..............

Hi, my name is diablo 3. I believe you've met me and my friend error 37?

[Franchi]

MrPenguin, on 08 April 2013 - 01:43 PM, said:

Hi, my name is diablo 3. I believe you've met me and my friend error 37?

Reading comprehension:1
You:0

Nope never met D3, knew it was going to be a POS long before launch.

Had the same feelings about it pre-launch that I have now about MWO post launch, to bad my spidy senses didn't start tingling in time for this one.

Edited by Franchi, 08 April 2013 - 01:47 PM.

[Hekalite]

Dishevel, on 08 April 2013 - 09:07 AM, said:

My premium time is running. I do not want to hear "Its beta". In a real beta they roll back and fix ****.

this is not beta anymore. Once they can not roll back changes due to the money they make with the changes they can no longer hide behind beta,

Quoted just in case you thought I didn't read your post.

It's beta. Get over it. If you have premium time running it's because you made a conscious choice to buy it knowing full well the game was in beta. It will be considered "out of beta" when they remove the beta from their logo.

As for the bugs themselves, read the command chair post on the subject.

[MrPenguin]

[Roadbeer]

Franchi, on 08 April 2013 - 01:45 PM, said:

Nope never met D3, knew it was going to be a POS long before launch.

And yet you use Blizzard as your reference for stability. Little disingenuous don't you think?

Franchi, on 08 April 2013 - 01:45 PM, said:

Had the same feelings about it pre-launch that I have now about MWO post launch, to bad my spidy senses didn't start tingling in time for this one.

Post launch? Oh, you're one of those "Not Beta" guys, aren't you?

[Side Step]

Blizzard who releases their game "when they're finished" take their time in ironing out bugs. You cannot have bug fixes both fast and good. You only get one, or the other.

As an answer to topic title: This is why we have to wait. So we don't get half assed fixes that only demand more fixing down the line.


I'm fine with waiting until they get it right, and I really hope they take their time with UI 2 so it will become a good platform with very few bugs that they can build upon on their way to release.

If UI 2 comes out and the bugs are still there, then there's reason for concern...

Edited by Side Step, 08 April 2013 - 01:58 PM.

[Franchi]

Roadbeer, on 08 April 2013 - 01:51 PM, said:

And yet you use Blizzard as your reference for stability. Little disingenuous don't you think?



Post launch? Oh, you're one of those "Not Beta" guys, aren't you?

Got anything other than opening day errors as the game gets flooded with millions of players? Hell I bet PGI would KILL to have that kind of problem.

I said it was going to be a POS, as in boring bland game play and an absurd RL money auction house that I would not enjoy.

We can argue about "It's a Beta" but there are no more wipes and the game is available to play for anyone and the game is running SALES every weekend, its a soft launch but a definitive launch.

Edited by Franchi, 08 April 2013 - 02:05 PM.

[l4Dl]

Garth Erlam, on 08 April 2013 - 12:47 PM, said:

Oh, sure, I'll just 'send' you the codebase for the game.

Garth,

I offer you my help, which i believe can resolve the hud bugs within a few days (on my own). Free of change to PGi.

As most of the .lua scripts are contained in the scripts.pak file, and, open to everyone who installed the game, i so no reason why giving me the requested "current" code will be an issue?

Garth Erlam, on 08 April 2013 - 12:47 PM, said:

Since we're making ridiculous claims,

If you believe .lua script performs faster and more efficiently than C++, please do fill me in.
Maybe i've been programming games in C++ all this time, when, i should of been making .lua scripts with references to Nanosuit?

Garth Erlam, on 08 April 2013 - 12:47 PM, said:

the Cicada should have 12 energy slots, also you need to pay money directly to my bank account so I can remove the code that'll cause you to crash on load.

I fail to see how making childish jokes regarding mech configs will fix the current HUD bugs in the game, or, is this your way of showing me how much the "current unstable build" is not a concern for you?

Edited by l4Dl, 08 April 2013 - 02:05 PM.

[Mild Monkey]

Garth Erlam, on 08 April 2013 - 09:11 AM, said:

Actually, that doesn't happen.

I appreciate you're angry, but understand that, 'I'm having HUD problems' isn't a light-switch fix. There's no magical button, or line of code, that will 'fix' it. If we could fix it quickly, why wouldn't we? What possible scenario would have us cackling in glee as our game had an error?

As soon as we can, we will hotfix or patch the issue out.

Because apparently you are EVVVIL. That office of yours is a den, admit it already. Maybe even a pit, who knows. Or a dungeon, if you are into it. There you sit all day, brooding... "Ah, my immoral allies, what part of our source of income are we going to screw up royally today? Lord Deviant, any ideas? Mylord Counselor of Unimportant issues, do you think we could code some strange psychedelic shapes into the game?"

This is how you are pictured by this particular part of the community.
Guys, I have said so before and I will say it again: There are so freaking MANY different aspects to a game, including the businessy part of it... myriads of issues appear on an hourly basis and they all need to be taken care of YESTERDAY OR ELSE. These guys have to prioritize all the time, cut them some slack. Yes, there are a lot of bugs, goobers and even boogers in the game but is it unplayable? Hells to the nah!

You are picturing the devs (and dev is short for devil, amirite?) as greedy Scroodge McDuck figures counting money and ordering their next golden toilet bowl with sable fur trimmed seat while stroking their handsewn wallets made from baby dolphin foreskins?

Edited by Mild Monkey, 08 April 2013 - 02:08 PM.

[Kain]

We have to wait, because they are probably developing through Agile™ with a 2 week iteration process,

Nevertheless I have to wait until i just can play the game again, because the current version is bugged for , due to this:
http://mwomercs.com/...e-your-drivers/

And the only thing I can do is, filing a support ticket and wait, until they have fixed this bug..
That is just the way it is..., of course PGI choices/patches/bugs/development could be criticized, but alas we are not making this game...

Edited by Kain, 08 April 2013 - 02:10 PM.