

Performance & Connectivity Feedback
#101
Posted 03 April 2013 - 03:49 AM
Otherwise, the last match I dropped into started with me rubber-banding all over creation before finally timing out and the process aborted (crash to desktop).
So that was interesting. Not sure I want to re-launch the client in the immediate future.
#102
Posted 03 April 2013 - 04:03 AM
- No issues with graphics (It actually 'felt' better) - no kaleidoscopic bug, no missing textures, no stuttering, no fps drops
- No issues with lagspikes and such (but I've seen people clearly experiencing them)
- 4-5 times (mostly on Alpine, not sure if map related) I've got crash to mechlab immediately after the match finished. No scoreboard, no exp&C-bill rewards, mech stayed locked for 5-10 minutes after the match.
(i5 3470, GF 650ti, 8gb ram, win 7 64x)
#103
Posted 03 April 2013 - 04:18 AM
1. 5 vs 8 - 8 Players ingame but only 5 Mechs
2. crash to mechlab
3. game chrash - had to be killed by taskmanager
Heatvision is fine but be serious PGI. In my company some guys get fired when they deliver again and again such a failure.
Please try to implement a kind of Quality control.
My system:
Number of Physical Processors 1
Number of Cores per Processor 4
Number of Logical Processors 4
CPU #1 Intel Core i5 3550
CPU Name Intel® Core i5-3550 CPU @ 3.30GHz
CPU Code Name Ivy Bridge
Vendor GenuineIntel
Number of Bits 64
Original Clock 3300 MHz
Video Adapter Radeon HD 6870
Video Processor AMD Radeon Graphics Processor (0x6738)
Memory Type DDR3
Installed Memory 8192 MBytes
Available Memory 8146 MBytes
Channels Dual
Maximum Capacity 32768 MBytes
Memory Slots 4
Win7 64bit
Se you after a hotfix.
#104
Posted 03 April 2013 - 04:55 AM
CPU: Intel i975 extreme @ 3.5 ghz
RAM: 12 gigs DDR3 2300
Drives: 2xOCZ Vertex 2's in RAID0
GPU: SLI - 2xEVGA GTX 680 FTW +
Drivers: 314.22
Release: 03/25/2013
So far no shader crash that has been plaguing me for weeks. checking the teams summary screen for alive/dead makes that entire window strobe and go grainy.
Edited by BrokenNachtmahr, 03 April 2013 - 05:05 AM.
#105
Posted 03 April 2013 - 04:56 AM
System:
i3 2100 @3.1GHz
4Gb DDR3 ram
GeForce gt430 2Gb
Win 7 32bit
#106
Posted 03 April 2013 - 05:05 AM
#107
Posted 03 April 2013 - 05:23 AM
- How had the patch generally affected your performance?
- Whether there are specific points in the game when your performance changes.
- What are your video settings, did you change them since last patch?
- Your advertised internet connection speed / Geographic location
#108
Posted 03 April 2013 - 05:37 AM
http://mwomercs.com/...ch/page__st__20
Anony Mouse, on 03 April 2013 - 05:30 AM, said:
#109
Posted 03 April 2013 - 05:57 AM
The beginnings of the matches take significantly longer, too.
Bad work.

#110
Posted 03 April 2013 - 06:12 AM
¿GPU Drivers are up to date? 314,22, check.
¿Direct X is up to date? check
¿The connection works as intended? Speedtest says check. Let's get on it.
Played 6 hours "in a row" since the patch.
Not a single match w/o some kind of bug in my team.
-Graphic corruption issues,
-Textures not loading issues,
-massive lag (even had two weapons fired at once with different mouse buttons, and one went out a second later, and the other three seconds after the first one),
-Black screens,
-Unability to launch the game if Mumble is on,
-This:

-The usual minimap not working, or not as intended issues,
-The usual hangouts when trying to get into the drop,
-The usual "Ready button unclicked when launch is clicked",
-No hud at all, or disappearence of it in the middle of the combat,
-No player personal onscreen indicators (own or enemy) when zoomed,
-Some warping,
-Some rubberbanding,
-'Mech stays ingame when the game is finished,
-Occasional freezing for some seconds...
This is not a failed patch issue. this game is a mess, because the old bugs are still on, and with every new patch the list keeps growing.
PLUS over all this, the comment from Mr. Ekman saying: "The lone wolf play style is what players currently have in the game today; the NPC factions will be free-to-play; the Merc Corps, on the other hand, will be monetized. "We're looking at possibly charging a one-time setup fee," Ekman said. "This is just to make sure there's not a flood of one-player corps." finished grinding my gears.Thanks, but no thanks.
Edited by Caballo, 03 April 2013 - 06:40 AM.
#111
Posted 03 April 2013 - 07:17 AM
Taking forever to access the Mechlab.
Drop Menu not appearing.
Black screen when game is entered.
Random disconnects and crashes.
Losing patience severely. PGI declared officially incompetent.
#112
Posted 03 April 2013 - 07:20 AM
#113
Posted 03 April 2013 - 07:40 AM
BulzEye, on 03 April 2013 - 07:20 AM, said:
Agreed on all points ... game was quite playable before this patch, barely had any problems. The rubber banding introduced in this patch is probably the most annoying... you go to shoot and can't tell which of the "popping" mechs to target.
Netcode wasn't mentioned in the patch notes but obviously something was touched, and has resulted in very negative side effects.
#114
Posted 03 April 2013 - 08:11 AM
I've played maybe 10 matches since the patch, and every match has had 2-3 disconnects - either players that disconnect, or players that never really make it into the match (their player name shows up, but a mech never does)
#115
Posted 03 April 2013 - 08:53 AM
#116
Posted 03 April 2013 - 09:03 AM
#117
Posted 03 April 2013 - 09:09 AM
since the patch I have had much more disconnects and complete breakdowns.
#118
Posted 03 April 2013 - 09:10 AM
Like 3-4 PER TEAM. No error no explanation, just CTD. I haven't have this many crashes EVER in this game.
#119
Posted 03 April 2013 - 09:12 AM
- performance fine yesterday, today it's unplayable.
- terrible lag/rubber banding going on. Ping otherwise looks ok.
- 1280x1024, very high, no blur, fullscreen
- Average 45 - 60 fps
- AMD PhenomII x4 965 BE@3.6GHz, 4GB RAM, AMD Radeon 7850 (13.1 Cats), Win7x64
- Cable 3/1Mb, ~80 ping, Texas
#120
Posted 03 April 2013 - 09:17 AM
Unbelievable.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users