57 replies to this topic

[C E Dwyer]

frame rate is stable has been around 60 on low settings

ping however has trebled from 97 to 294

isp virgin media (UK) 30meg down load,2 meg upload ( and I get that or higher)

10 meg ram
geforce gtx650ti
intel i5

did speed checks today from varying places west to east coast from north america to England UK

Worse by far was Vancouver less than 8mbps download spd 1mbps upload with a ping of 348

Halifax 28.7 download 1.8 upload ping 220

Edited by Cathy, 19 September 2013 - 05:22 AM.

[Peter von Danzig]

It seems that mostly people from germany, austria and finland having connectivity issues...

[Airu]

My ping took a hit, used to be around 60-70 (from Canada) now its at 169 most of the time

[Beijing]

Worked for the last 2-3 hours without a problem. Now the ping is back to ****** up.
And I can't even login anymore.

See the ping to the Internap Router in Toronto:

Spoiler

Pinging 70.42.24.196 with 32 bytes of data:
Reply from 70.42.24.196: bytes=32 time=174ms TTL=244
Reply from 70.42.24.196: bytes=32 time=161ms TTL=244
Reply from 70.42.24.196: bytes=32 time=158ms TTL=244
Reply from 70.42.24.196: bytes=32 time=717ms TTL=244
Reply from 70.42.24.196: bytes=32 time=194ms TTL=244
Reply from 70.42.24.196: bytes=32 time=160ms TTL=244
Reply from 70.42.24.196: bytes=32 time=159ms TTL=244
Request timed out.
Reply from 70.42.24.196: bytes=32 time=157ms TTL=244
Request timed out.
Request timed out.
Reply from 70.42.24.196: bytes=32 time=159ms TTL=244
Reply from 70.42.24.196: bytes=32 time=158ms TTL=244
Reply from 70.42.24.196: bytes=32 time=290ms TTL=244
Reply from 70.42.24.196: bytes=32 time=340ms TTL=244
Reply from 70.42.24.196: bytes=32 time=158ms TTL=244
Reply from 70.42.24.196: bytes=32 time=158ms TTL=244
Request timed out.
Reply from 70.42.24.196: bytes=32 time=168ms TTL=244
Reply from 70.42.24.196: bytes=32 time=160ms TTL=244
Reply from 70.42.24.196: bytes=32 time=158ms TTL=244
Request timed out.
Reply from 70.42.24.196: bytes=32 time=158ms TTL=244

Ping statistics for 70.42.24.196:
Packets: Sent = 23, Received = 18, Lost = 5 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 717ms, Average = 210ms

[Thor Dyrden]

Ping ok again today (Germany)... was 500+ yesterday - now back to normal (125-130)

[Beijing]

Right now it works again...

[Azar Javed]

Just a side note: It seems that the nVidia GeForce driver v320.18 WHQL is making serious problems since launch. Got down to 8-12fps with weird motion blurring all over the scene (disabling MB didn't do anything, nor did changing other options). Driver 320.49 WHQL and also the brand-new 327.23 WHQL that got released today have fixed this for me. Also, my pings didn't fluctuate a bit since launch, sitting at around 130ms from Austria, just like before.

8/8Mbit G.SHDSL full duplex line
2 x GTX 580 3GB
WinXP Pro x64 Edition SP2 (NT5.2)

Sad to see that even GeForce driver 327.23 did not bring an SLI profile for MWO though.

I mean, ~50fps are nice in 2560x1600, but when there's lots of smoke and explosions, it can drop to 20-30. SLI would maybe really help there.

Edited by Azar Javed, 19 September 2013 - 01:58 PM.

[Mighty Spike]

Always had a constant ping at 130. Now 140-150. And also a fps drop from25-30. now 11-20. Its now hard to play,huge lags in the game,aiming nearly impossible. Any Fix incoming? Nothing changed at settings and drivers.

Edited by Mighty Spike, 20 September 2013 - 07:48 AM.

[Autobot9000]

For me there are three main issues regarding performance:

1) Heat vision. This is sometimes unplayable. For some reason the FPS can drop dramatically when enabling heat vision. I can not give a fully reproducible description, but at some point I guessed one particular case of this happening was in Frozen City, when entering fog areas. This is not the only case of the issue though, just the one, where I repeatedly saw it happening.

2) The game is obviously precalculating/initializing/loading material while progressing through a map (mechs, animations, special effects (shaders?), textures?). As I am not a developer I obviously can't tell what it is, but certainly on my computer it causes full-stalls of the FPS for some milliseconds. If that happens in a battle it's quite likely I am losing because of this. In other circumstances it still lowers the games appeal. I wouldn't mind, if I had to wait longer before a match or even before the game starts up. Just in games this is annoying.

3) The game stutters/stalls for noticable time, when moving the camera aburptly, e.g. by changing direction on a light mech at full speed or quickyl twisting the torso. This doesn't go away after that area has loaded, it seems just that the games performance is so low, that it can not handle this kind of fast paced gaming. It's one of the reasons why it's unattractive to me to play a light mech. I am aware, that a core 2 duo (wolfdale 8200)@2.66Ghz with an ATI 6850HD and 4GB RAM isn't a top end setup, but not absurdly terrible either.


Edit:
MWO is currently the only application on my computer managing to blue screen my Windows7 64 bit. I think MWO is crashing my ATI display driver obviously I have the most recent version installed). You guys probably need to sort out with ATI if there are issues in their driver or whether you are using a feature not supported in this particular way from ATI. The issue happens maybe every 100 games.

Edited by Autobot9000, 20 September 2013 - 09:30 AM.

[kainers]

So frustrating trying to play with there being so much shudder. My pings are a consistent 90's. Frame rate sucks at 15-20 but always has. Mech's are standing still just marching then jump to another location like magic. My Mech seems to just go in circles when this happens. I press R to target Mech's nothing happens till 10 seconds later. I try and fire anything and there is 5-10 seconds before anything launches. This started a couple days ago and hasn't gotten better, today it actually seems worse.

[Flapdrol]

My ping is far from stable, 120-200 or even higher during peak hours. If I play in the morning (europe) the ping is a steady 120 and hit detection seems fantastic, with fluctuating ping it's pretty bad sometimes.

I wonder if there's a tool or a way to keep an eye on things, see if the connection is overloaded on my end, pgi end or somewhere in between. My ping to local sites is generally a steady 20.

[9H3X6]

Last two patches have had a significant impact on my FPS. The user.cfg is not working. Overall the performance hit took me out of the 50-40s average battle FPS range and put me into the 40-30s for most maps. (60FPS standing still) However, both vision modes (frozen city + river city night) will produce unplayable 15-30. I have ton quite a bit to try to correct. Repair tool. Re-install. New ATI 13.9 driver. Empty user.cfg. It seems to give playable frame rate following reboot but after so many games the performance just drops. I've consistently thought I corrected the issue then low FPS returns.

Prior patches that broke user.cfg I played with all max settings + vync. Here's user.cfg I used for months without any FPS issues. Note I also used sweetfx during that time. Not using it anymore with the return of film grain.

Spoiler

;Field of View inside Cockpit (Default:75)
cl_fov = 85
cl_sensitivity = 0.1
r_ColorGrading = 0
r_DepthOfField = 0
r_GlowAnamorphicFlares = 1
r_HDRBloomMul = 0.6
r_HDRBlueShift = 0
r_HDRBrightLevel = 0.75
r_HDRBrightOffset = 5
r_HDRBrightThreshold = 6
r_HDREyeAdaptionCache = 0
r_HDRGrainAmount = 0
r_HDRLevel = 3
r_HDROffset = 10
r_HDRRendering = 1
r_MotionBlur = 0
r_MotionBlurMaxViewDist = 100
r_PostProcessHUD3DCache = 0
r_RainMaxViewDist_Deferred = 100
r_Sunshafts = 1
q_Renderer = 4
q_ShaderFX = 4
q_ShaderGeneral = 4
q_ShaderGlass = 4
q_ShaderHDR = 4
q_ShaderIce = 4
q_ShaderMetal = 4
q_ShaderPostProcess = 4
q_ShaderShadow = 4
q_ShaderSky = 4
q_ShaderTerrain = 4
q_ShaderVegetation = 4
e_Shadows = 1
e_GsmCache = 0
e_GsmLodsNum = 5
e_GsmRange = 3
e_ParticlesShadows = 1
e_ShadowsCastViewDistRatio = 1
e_ShadowsMaxTexRes = 1024
e_ShadowsOnAlphaBlend = 0
e_ShadowsResScale = 4.0
r_ShadowBlur = 2
r_ShadowJittering = 2.5
r_ShadowsPCFiltering = 1
r_ShadowsUseClipVolume = 1
r_FogShadows = 1

s_MPEGDecoders = 32
s_Obstruction = 1
s_ObstructionAccuracy = 1
s_ObstructionUpdate = 0.1
s_SoundMoodsDSP = 1
s_VariationLimiter = 1
e_WaterOceanFFT = 1
e_WaterTessellationAmount = 10
e_WaterTessellationAmountX = 85
e_WaterTessellationAmountY = 85
e_WaterTessellationSwathWidth = 10
r_WaterCaustics = 1
r_WaterReflections = 1
r_WaterReflectionsQuality = 5
r_WaterReflectionsMinVisiblePixelsUpdate = 0.05
r_WaterTessellationHW = 1
r_WaterUpdateDistance = 0.2
r_WaterUpdateFactor = 0.05
e_DynamicLightsMaxEntityLights = 32
e_GI = 1
e_GIAmount = 0.6
e_GINumCascades = 1
e_GIMaxDistance = 100
e_SkyType = 1
e_SkyUpdateRate = 1
e_TerrainAo = 1
e_TerrainNormalMap = 1
e_VegetationUseTerrainColor = 1
r_DetailDistance = 8
r_DetailTextures = 1
r_ssdo = 1
r_SSDOAmount = 0.8
r_SSDOAmbientAmount = 1.1
r_SSAO = 0
r_SSAOQuality = 3
r_SSAODownscale = 0
r_refraction = 1
r_SSReflections = 3
r_Beams = 3
r_BeamsDistFactor = 0.01
r_BeamsMaxSlices = 300
e_Clouds = 1
r_CloudsUpdateAlways = 1
r_Reflections = 1
e_GsmRangeStep = 4
sys_spec_Quality=4
e_GsmCastFromTerrain = 1

i_lighteffects = 1
g_ragdollMinTime = 15
g_ragdollUnseenTime = 3
g_ragdollDistance = 40
e_ObjQuality = 4
e_DecalsAllowGameDecals = 1
e_DecalsLifeTimeScale = 2
e_DecalsOverlapping = 1
e_Dissolve = 2
e_LodRatio = 40
e_Lods = 1
e_LodMin = 0
e_MaxViewDistSpecLerp = 1
e_OcclusionCullingViewDistRatio = 1
e_ProcVegetation = 1
e_streamCgf = 0
e_VegetationBending = 1
e_VegetationMinSize = 0
e_VegetationSpritesDistanceCustomRatioMin = 1
e_VegetationSpritesDistanceRatio = 1.5
e_ViewDistMin = 10
e_ViewDistRatio = 100
e_ViewDistRatioCustom = 100
e_ViewDistRatioDetail = 100
e_ViewDistRatioLights = 100
e_ViewDistRatioVegetation = 100
e_TerrainDetailMaterialsViewDistXY = 2048
e_TerrainDetailMaterialsViewDistZ = 128
e_TerrainOcclusionCullingMaxDist = 200
ca_AttachmentCullingRation = 300
ca_DrawFaceAttachments = 1
ca_useDecals = 1
es_DebrisLifetimeScale = 1
i_rejecteffects = 1
e_Tessellation = 1
e_DecalsForceDeferred = 1
r_DrawNearZRange = 0.08
e_ParticlesQuality = 4
e_ParticlesLights = 1
e_ParticlesMaxScreenFill = 160
e_ParticlesMinDrawPixels = 1
e_ParticlesMotionBlur = 1
e_ParticlesObjectCollisions = 2
r_UseParticlesHalfRes = 0
r_UseSoftParticles = 2
g_breakage_particles_limit = 160
g_joint_breaking = 1
g_tree_cut_reuse_dist = 0
e_CullVegActivation = 50
e_FoliageWindActivationDist = 25
e_PhysFoliage = 2
e_PhysOceanCell = 0.5
p_gravity_z = -36.3
p_joint_damage_accum = 2
p_joint_damage_accum_threshold = 0.2
p_max_MC_iters = 6000
p_max_object_splashes = 3
p_max_substeps_large_group = 5
p_num_bodies_large_group = 100
p_splash_dist0 = 7
p_splash_dist1 = 30
p_splash_force0 = 10
p_splash_force1 = 100
p_splash_vel0 = 4.5
p_splash_vel1 = 10
v_vehicle_quality = 4
es_MaxPhysDist = 200
es_MaxPhysDistInvisible = 25
r_DynTexAtlasCloudsMaxSize = 128
r_DynTexAtlasSpritesMaxSize = 128
r_DynTexMaxSize = 80
r_EnvCMResolution = 2
r_EnvTexResolution = 3
r_EnvTexUpdateInterval = 0.001
r_ImposterRatio = 1
r_TexSkyResolution = 0
r_TexAtlasSize = 2048
r_TexMinAnisotropy = 8
r_TexBumpResolution = 0
r_TexResolution = 0
r_TexturesStreaming = 0
r_VegetationSpritesTexRes = 256

e_CoverageBufferReproj = 0

Following Sept. patches I've tested with all max + vync as well as all max except post processesing @ low, shadows @ med, vsync off, aa off. Same FPS result regardless of the all maxed or adjusted settings.

Unaware of any signifiant changes to the system since the Sept. patches.
System
i7 920 @ 3.6Ghz
6GB 1600MHz (triple channel)
ATI 7870 (tested with Catalyst 13.2, 13.4, 13.9)
Xfi-Music
2x WD 150GB V-raptors RAID0
Win7 64bit

Ping is same as before. California giving 90-120ms.

Really haven't taken the time to learn all the cry engine tweaks. Obtained the user.cfg from other community members. If something significant didn't change with the engine in the Sept. patch I'm speculating the FPS drop is related to something being ignored in the user.cfg I used for months.

Thanks!

Edited by 9H3X6, 21 September 2013 - 08:01 PM.

[Pirate2Ninja]

Ping is about the same, I've been tweaking settings so it's been hard to determine average fps but it is better if not the same, no detectable performance loss. But Match making has been taking two to four times longer

[Ryvucz]

Been getting quite a few random disconnects, and from the looks of it, so do others.

Session Lost

[Ripper X]

Ryvucz, on 22 September 2013 - 07:43 PM, said:

Been getting quite a few random disconnects, and from the looks of it, so do others.

Session Lost

Yep this has been happening for the past several minutes

Edited by Ripper X, 22 September 2013 - 07:49 PM.

[Chavette]

Still happening.

[ShinVector]

9H3X6, on 21 September 2013 - 07:52 PM, said:

Last two patches have had a significant impact on my FPS. The user.cfg is not working. Overall the performance hit took me out of the 50-40s average battle FPS range and put me into the 40-30s for most maps. (60FPS standing still) However, both vision modes (frozen city + river city night) will produce unplayable 15-30. I have ton quite a bit to try to correct. Repair tool. Re-install. New ATI 13.9 driver. Empty user.cfg. It seems to give playable frame rate following reboot but after so many games the performance just drops. I've consistently thought I corrected the issue then low FPS returns.

Prior patches that broke user.cfg I played with all max settings + vync. Here's user.cfg I used for months without any FPS issues. Note I also used sweetfx during that time. Not using it anymore with the return of film grain.

Spoiler

;Field of View inside Cockpit (Default:75)
cl_fov = 85
cl_sensitivity = 0.1
r_ColorGrading = 0
r_DepthOfField = 0
r_GlowAnamorphicFlares = 1
r_HDRBloomMul = 0.6
r_HDRBlueShift = 0
r_HDRBrightLevel = 0.75
r_HDRBrightOffset = 5
r_HDRBrightThreshold = 6
r_HDREyeAdaptionCache = 0
r_HDRGrainAmount = 0
r_HDRLevel = 3
r_HDROffset = 10
r_HDRRendering = 1
r_MotionBlur = 0
r_MotionBlurMaxViewDist = 100
r_PostProcessHUD3DCache = 0
r_RainMaxViewDist_Deferred = 100
r_Sunshafts = 1
q_Renderer = 4
q_ShaderFX = 4
q_ShaderGeneral = 4
q_ShaderGlass = 4
q_ShaderHDR = 4
q_ShaderIce = 4
q_ShaderMetal = 4
q_ShaderPostProcess = 4
q_ShaderShadow = 4
q_ShaderSky = 4
q_ShaderTerrain = 4
q_ShaderVegetation = 4
e_Shadows = 1
e_GsmCache = 0
e_GsmLodsNum = 5
e_GsmRange = 3
e_ParticlesShadows = 1
e_ShadowsCastViewDistRatio = 1
e_ShadowsMaxTexRes = 1024
e_ShadowsOnAlphaBlend = 0
e_ShadowsResScale = 4.0
r_ShadowBlur = 2
r_ShadowJittering = 2.5
r_ShadowsPCFiltering = 1
r_ShadowsUseClipVolume = 1
r_FogShadows = 1

s_MPEGDecoders = 32
s_Obstruction = 1
s_ObstructionAccuracy = 1
s_ObstructionUpdate = 0.1
s_SoundMoodsDSP = 1
s_VariationLimiter = 1
e_WaterOceanFFT = 1
e_WaterTessellationAmount = 10
e_WaterTessellationAmountX = 85
e_WaterTessellationAmountY = 85
e_WaterTessellationSwathWidth = 10
r_WaterCaustics = 1
r_WaterReflections = 1
r_WaterReflectionsQuality = 5
r_WaterReflectionsMinVisiblePixelsUpdate = 0.05
r_WaterTessellationHW = 1
r_WaterUpdateDistance = 0.2
r_WaterUpdateFactor = 0.05
e_DynamicLightsMaxEntityLights = 32
e_GI = 1
e_GIAmount = 0.6
e_GINumCascades = 1
e_GIMaxDistance = 100
e_SkyType = 1
e_SkyUpdateRate = 1
e_TerrainAo = 1
e_TerrainNormalMap = 1
e_VegetationUseTerrainColor = 1
r_DetailDistance = 8
r_DetailTextures = 1
r_ssdo = 1
r_SSDOAmount = 0.8
r_SSDOAmbientAmount = 1.1
r_SSAO = 0
r_SSAOQuality = 3
r_SSAODownscale = 0
r_refraction = 1
r_SSReflections = 3
r_Beams = 3
r_BeamsDistFactor = 0.01
r_BeamsMaxSlices = 300
e_Clouds = 1
r_CloudsUpdateAlways = 1
r_Reflections = 1
e_GsmRangeStep = 4
sys_spec_Quality=4
e_GsmCastFromTerrain = 1

i_lighteffects = 1
g_ragdollMinTime = 15
g_ragdollUnseenTime = 3
g_ragdollDistance = 40
e_ObjQuality = 4
e_DecalsAllowGameDecals = 1
e_DecalsLifeTimeScale = 2
e_DecalsOverlapping = 1
e_Dissolve = 2
e_LodRatio = 40
e_Lods = 1
e_LodMin = 0
e_MaxViewDistSpecLerp = 1
e_OcclusionCullingViewDistRatio = 1
e_ProcVegetation = 1
e_streamCgf = 0
e_VegetationBending = 1
e_VegetationMinSize = 0
e_VegetationSpritesDistanceCustomRatioMin = 1
e_VegetationSpritesDistanceRatio = 1.5
e_ViewDistMin = 10
e_ViewDistRatio = 100
e_ViewDistRatioCustom = 100
e_ViewDistRatioDetail = 100
e_ViewDistRatioLights = 100
e_ViewDistRatioVegetation = 100
e_TerrainDetailMaterialsViewDistXY = 2048
e_TerrainDetailMaterialsViewDistZ = 128
e_TerrainOcclusionCullingMaxDist = 200
ca_AttachmentCullingRation = 300
ca_DrawFaceAttachments = 1
ca_useDecals = 1
es_DebrisLifetimeScale = 1
i_rejecteffects = 1
e_Tessellation = 1
e_DecalsForceDeferred = 1
r_DrawNearZRange = 0.08
e_ParticlesQuality = 4
e_ParticlesLights = 1
e_ParticlesMaxScreenFill = 160
e_ParticlesMinDrawPixels = 1
e_ParticlesMotionBlur = 1
e_ParticlesObjectCollisions = 2
r_UseParticlesHalfRes = 0
r_UseSoftParticles = 2
g_breakage_particles_limit = 160
g_joint_breaking = 1
g_tree_cut_reuse_dist = 0
e_CullVegActivation = 50
e_FoliageWindActivationDist = 25
e_PhysFoliage = 2
e_PhysOceanCell = 0.5
p_gravity_z = -36.3
p_joint_damage_accum = 2
p_joint_damage_accum_threshold = 0.2
p_max_MC_iters = 6000
p_max_object_splashes = 3
p_max_substeps_large_group = 5
p_num_bodies_large_group = 100
p_splash_dist0 = 7
p_splash_dist1 = 30
p_splash_force0 = 10
p_splash_force1 = 100
p_splash_vel0 = 4.5
p_splash_vel1 = 10
v_vehicle_quality = 4
es_MaxPhysDist = 200
es_MaxPhysDistInvisible = 25
r_DynTexAtlasCloudsMaxSize = 128
r_DynTexAtlasSpritesMaxSize = 128
r_DynTexMaxSize = 80
r_EnvCMResolution = 2
r_EnvTexResolution = 3
r_EnvTexUpdateInterval = 0.001
r_ImposterRatio = 1
r_TexSkyResolution = 0
r_TexAtlasSize = 2048
r_TexMinAnisotropy = 8
r_TexBumpResolution = 0
r_TexResolution = 0
r_TexturesStreaming = 0
r_VegetationSpritesTexRes = 256

e_CoverageBufferReproj = 0

Following Sept. patches I've tested with all max + vync as well as all max except post processesing @ low, shadows @ med, vsync off, aa off. Same FPS result regardless of the all maxed or adjusted settings.

Unaware of any signifiant changes to the system since the Sept. patches.
System
i7 920 @ 3.6Ghz
6GB 1600MHz (triple channel)
ATI 7870 (tested with Catalyst 13.2, 13.4, 13.9)
Xfi-Music
2x WD 150GB V-raptors RAID0
Win7 64bit

Ping is same as before. California giving 90-120ms.

Really haven't taken the time to learn all the cry engine tweaks. Obtained the user.cfg from other community members. If something significant didn't change with the engine in the Sept. patch I'm speculating the FPS drop is related to something being ignored in the user.cfg I used for months.

Thanks!

I have the same CPU.. You might want to try playing with HT turn off and see whether your min fps improves.

[EyeDie I]

ping is usually in the 20s,used to get 50+fps on medium settings, now 36+fps on low with occasional freezes game gets less playable with every patch.

[Expired]

Ping before Patch: 120-150
Ping after Patch: 350-500
Ping after Patch after using Repair Tool: 200-400

Locking on Mechs takes ages, zooming takes ages, damage hardly registered

Frames are still the same: Around 45, having all Options on Maximum.

Phenom Black Edition II X4 955 @ 3.20GHz
12GB Ram
Radeon HD 6950
Win 7 64


Fix it please!

Edited by Expired, 23 September 2013 - 11:41 AM.

[Foster Bondroff]

With the latest patch ping really got bumpy.

Usually i had a ping of steady 120-140ms. After last patch ping varies between 140-450ms. This is very annyoning. Also some mini lags appeared where it seems as if the server loses me for about 1-2 seconds and than puts me back in.

I also wonder why so many functions seem to be server authoritative. I understand that some vital functions like weapons and movement tracking must be server authoritative, but why zoom function is?

I think a lot of functions could only be client sided. Would put much less stress on the servers and should lead to a much smoother gameplay.