46 replies to this topic

[Victor Morson]

Carcass23, on 29 April 2013 - 03:52 PM, said:

I love the way you throw vague numbers out there; "Well over half a dozen units.", "Most of the people that have stepped back over this have done so out of frustration and disappointment,", "I made this thread more on the behalf of the other people having this issue, which I'd argue is the vast majority." the list goes on..

Sobbing because the devs aren't fixing bugs fast enough for you. I voted no because this suggestion isn't helpful or productive.

Rolling things back to a working state, reintroducing the two new 'mechs and going from there isn't productive?

And this goes well beyond "vague numbers." Even in PUGs the level of discos are insane, and the reason is the same that the 8 mans are jacked. Because you do not have a problem does not mean there isn't one, and this one is in particular severe.

If you have some issue, go onto the NGNG Teamspeak and talk to any unit connected, see what they say. I'll bet you right now not one of them says differently.

Hammerfinn, on 29 April 2013 - 05:30 PM, said:

OP: you are overstating and not thinking through the practical effects of your suggestion.

Yes I am. Rolling back an issue until it can be introduced in a stable state is the NORM. I don't know why people think it isn't around here.

PGI has done rollbacks before.

Edited by Victor Morson, 29 April 2013 - 05:46 PM.

[Tsunamisan]

How hard would it be really to fix the HUD PGI just needs to give the players a command s to redraw it if it fails to initialize the first time in the match. We already have a command to turn the HUD off so why not have one that resets it and reloads the default values so if you have no radar or no compass. no torso twist showing you could fix that simply enough.


I also think if PGI released smaller patches more frequently instead of huge ones they would be easier to troubleshoot as well. Nothing harder that trying to find a problem in a mound of new code.

Edited by Tsunamisan, 01 May 2013 - 09:49 PM.

[Hammerfinn]

How the heck is this piece not in K-town for improvement yet?

The amount of ignorance about development and coding, business structure and management is simply mind-boggling.

Mods, move this where it belongs, where it can become the thread it was meant to be!

[Renthrak]

Tsunamisan, on 01 May 2013 - 09:46 PM, said:

How hard would it be really to fix the HUD PGI just needs to give the players a command s to redraw it if it fails to initialize the first time in the match. We already have a command to turn the HUD off so why not have one that resets it and reloads the default values so if you have no radar or no compass. no torso twist showing you could fix that simply enough.

If it was that simple, it would already be fixed. If it's a choice between assuming the people making the game are so braindead that they didn't think of this already, or that the amateur suggestion wouldn't fix the problem, I'll go with the latter.

Tsunamisan, on 01 May 2013 - 09:46 PM, said:

I also think if PGI released smaller patches more frequently instead of huge ones they would be easier to troubleshoot as well. Nothing harder that trying to find a problem in a mound of new code.

They did exactly that during Closed Beta. It wasn't any better. In fact, having to finalize a patch every week seems to have been a distraction from fixing existing issues, since the program build would change so often. The extra week is useful for nailing down a problem without tossing in new issues half-way through.

Comparing Closed Beta stability to what we have now, there is a larger problem more often (crash, HUD bug, etc), but when there is NOT a major problem, the game is so much more playable. I'll take the trade-off, since it's not a permanent problem anyway. The game is nowhere near finished at this point. We're still in Beta, even if some people want to claim that a prototype is a production model because they say it is.

[Carl Wrede]

You people without crashes or freezebugs, i wonder if you know how lucky you are?

I myself have a CTD or freezebug around every 4th game or so. Sometimes several games in a row. It gets rather frustrating after a while especially when you play in a team with your friends and there is almost always one or several that crashes every game.

[Fooooo]

Tsunamisan, on 01 May 2013 - 09:46 PM, said:

How hard would it be really to fix the HUD PGI just needs to give the players a command s to redraw it if it fails to initialize the first time in the match. We already have a command to turn the HUD off so why not have one that resets it and reloads the default values so if you have no radar or no compass. no torso twist showing you could fix that simply enough.

That little bit right there.

There is a cvar called

gfx_reload_ui

However it seems to do nothing. Its most likely just a cvar for the editor, which doesnt work in game.......however it got me to thinking the same thing you are.

Why not create a quick reloader and bind it to a key ?

That way people who suffer a HUD failure can "reboot" the HUD. Much like reloading the shaders or terrain while in-game etc........ Although TBH it may not fix the issue for that match at all, as whatever caused the failure may still be there and just cause it to fail again when you reload it etc.....

It would be a nice stop-gap until they fix the issue.....if its possible that is.

Edited by Fooooo, 02 May 2013 - 03:46 AM.

[DaZur]

Hammerfinn, on 01 May 2013 - 10:05 PM, said:

The amount of ignorance about development and coding, business structure and management is simply mind-boggling.

What?!! C++ coding doesn't have an auto-correct like MS Word?

I've said it once and I'll say it again... The Internet is the only place in the world where every user is an expert and every industry professional is viewed as a knuckle-dragging mouth breather...