

Pgi, Why Are Your Patches Always So Buggy?
#1
Posted 02 April 2013 - 08:36 PM
When the game first became open beta it was at least two steps forward one step back. Heck I still think LRM's were the more balanced BEFORE the first accidental OP'ing of LRM bug. Now you finally brought them back almost to that point to have them become OP'ed again due to a glaring bug and my friend and I could easily predict you will nerf them to hell and back and after two weeks you still haven't fixed them, while at the same time adding Air Strikes, and Artillery Strikes that don't work.
Not to mention the server issues, the patch before last my friend and I were having hud issues 1 out of 3 matches with more crashes than ever before, and it's even worse this patch. How is it that you can't spend a single patch not focused on adding buggy content and fixing the bugs you already have in the game.
People disconnect due to errors in your game yet you told us flat out NO, that you won't add in a re-connect feature that even other similar games, ex. WOT have. Then why isn't this a greater priority? Yes we'd like new content but I can already imagine the first phase of community warfare coming in and that not working.
Please make your game more stable, don't add more content to your house of cards while at the very same time the very foundation of the game seems to crumble and get worse and worse. I want your game to succeed so I can have fun and enjoy it, but as much as it pains me to say this, but it feels to me you are doing anything you can to try to make this game fail but not solving your basics.
Direct x 11 isn't in, collisions aren't in, game crashes, servers getting worse at patch day. There is a poll out there stating how people are afraid of your patches due to the issues they bring. Please fix your game and stop trying our patience.
#2
Posted 02 April 2013 - 08:46 PM
#3
Posted 02 April 2013 - 09:08 PM
It's yet another ball dropped over another fact of PGI and their handling of the Battletech franchise just over the past week...
#5
Posted 02 April 2013 - 10:05 PM
Ter Ushaka, on 02 April 2013 - 09:40 PM, said:
You sir, are like a school holiday. No class.
@OP - it's scary how each patch just brings my level of enjoyment down. I can't wait for 'Beta' to be over which from all indication will be sometime this year. Have them launch Mechwarrior Online only to have casual players the world over complain about how buggy it is and drop it for something better.
That way, someone else; hopefully a company with tons more resouces and know how, can take over the Mechwarrior IP and franchise. I mean I applaude that they're doing but methinks they've bitten more off than they can chew.
#6
Posted 02 April 2013 - 10:17 PM
For a beta patch intended to get the game closer to a 1.0 state, this patch was 100% unacceptable, there is no way around it.
#7
Posted 02 April 2013 - 10:19 PM
Gotta remember the engine itself was updated during closed beta, and it messed up a lot of their work.
I know no one likes to hear it or read it, but... give it time. =P
#8
Posted 02 April 2013 - 10:22 PM
Add in variables like different computer hardware configurations, it's almost impossible for them to catch everything.
Additionally, patches may go up with bugs that are intentionally left to be fixed later. I agree it sucks, but the more detailed and thorough people can be about bug feedback, the better chance of getting it fixed.
Edited by tuokaerf, 02 April 2013 - 10:26 PM.
#9
Posted 02 April 2013 - 10:24 PM
Ryvucz, on 02 April 2013 - 10:19 PM, said:
Gotta remember the engine itself was updated during closed beta, and it messed up a lot of their work.
I know no one likes to hear it or read it, but... give it time. =P
I will say I like your reply better than the person who told me to shut up because I am not a computer game programmer. I state I am not an expert and make an observation. I appreciate you putting this knowledge forward though if you can, can you tell me where you obtained this info?
#10
Posted 02 April 2013 - 10:24 PM
It's not that these would be rare bugs that happen once in a while.
I played 2 matches after patch and experienced 3 bugs in that time before I quit to wait for hotfix.
I guess I'll no longer wait for patchday but for the hotfix-for-the-patch-day in the future.
#11
Posted 02 April 2013 - 10:27 PM
#12
Posted 02 April 2013 - 10:29 PM
Valdez Raptor, on 02 April 2013 - 10:24 PM, said:
I will say I like your reply better than the person who told me to shut up because I am not a computer game programmer. I state I am not an expert and make an observation. I appreciate you putting this knowledge forward though if you can, can you tell me where you obtained this info?
They had mentioned the upgrade to the engine in the closed beta forums, no idea where this would be at now though.
But I imagine that it is possible to look up information on the engine itself, pretty sure the creators of the game engine would boast new changes to the engine for marketing purposes.
Cryengine 3 is the name of the engine. I'd look it up myself but it's bedtime, and I'm just making "closing posts" before I go to sleep.
=D
#13
Posted 02 April 2013 - 10:34 PM
#14
Posted 02 April 2013 - 10:36 PM

I've notice on this patch that i have been getting artificial tearing in the terrain textures quite often, where before that was rarely occurring. Also seem to be having more CTD from the patch. Happen twice in 25 ish matches.... Again tho the problems normally go away once the patches have been tested by the community and PGI gets to tweak stuff around.
#15
Posted 02 April 2013 - 10:36 PM
Texas Merc, on 02 April 2013 - 10:27 PM, said:
There was the update that messed up their work horribly during closed beta, I remember that well.
Things were running smooth, no jerking/ruberbanding, then all of a sudden "New CRYengine update, now with more CRY!'
And the thing crapped itself and they had to do more passes over the maps. Remember that "4 FPS" bug? Yeah, the update did that.
Give 'em a little bit of a break.
#16
Posted 02 April 2013 - 10:39 PM
Ryvucz, on 02 April 2013 - 10:36 PM, said:
There was the update that messed up their work horribly during closed beta, I remember that well.
Things were running smooth, no jerking/ruberbanding, then all of a sudden New CRYengine update, now with more CRY!'
And the thing crapped itself and they had to do more passes over the maps. Remember that 4 FPS bug? Yeah, the update did that.
Give 'em a little bit of a break.
Yay someone else understands too.
P.S. : Dat Signature
Edited by Nightshade1, 02 April 2013 - 10:41 PM.
#17
Posted 02 April 2013 - 10:43 PM
#18
Posted 02 April 2013 - 10:43 PM
#19
Posted 02 April 2013 - 10:44 PM
Ryvucz, on 02 April 2013 - 10:36 PM, said:
There was the update that messed up their work horribly during closed beta, I remember that well.
Things were running smooth, no jerking/ruberbanding, then all of a sudden "New CRYengine update, now with more CRY!'
And the thing crapped itself and they had to do more passes over the maps. Remember that "4 FPS" bug? Yeah, the update did that.
Give 'em a little bit of a break.
Oh dear god I remember that patch. Trying to shoot a jenner was kinda ridiculous after that. Remember how bad the ruberbanding was with collisions??? Blew off a chunk of my teammates armor half the time trying to shoot the enemy getting up O_o
#20
Posted 02 April 2013 - 10:46 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users