34 replies to this topic

[DustyLoft]

Well, after a couple of relatively lag-free nights of MWO, last night I was back to total laggage almost every round. I'm not sure why it varies from night to night. General internet traffic / latency? I'm always on at the same time though - 9:30pm GMT to midnight or 1am. ...I think I need to visit 'MWO Anonymous.'

The worst case of lag was when 5 or 6 Lights (Jenners and Locusts), of which I was one, were running in circles, in close proximity, in the sea in Crimson Strait. The game would be fluid for a few seconds, then the screen would freeze for a few seconds, then it would go fluid for a few more seconds, then freeze again, and so on. Eventually the Jenner we were all chasing just stood still (not powered down) and we killed it. Whether they were also experiencing lag and just decided to disconnect, I don't know.

I take Durant's point about scenery / buildings taking their toll on CPU/GPU. Maybe that is when the freezing occurred - when I circled round to face the city / coast. Seemed a bit more random than that though.

As Zeus says, this is the only game where this happens.

As NRP says, upgrading isn't necessarily the cure.

We have fibre optic cable in our area, and have had for 13 years. Should be nice and quick... in theory.

Well, I've got an hour spare. Lets see what tonight brings...

[SirDubba]

If you have fiber cable, then I don't think your connection is causing issues..

I've experienced drops in fps mostly at Tourmaline Desert when I'm at the side of the map looking towards the center. There are smoke- (and blurring heat-)effects of somekind and especially when there is a battle going at the center, my fps drops from capped 60 to ~40fps. Usually It stays above 50fps very nicely even during close combat.
This fps drop, which happens in some other maps as well, caustic valley being another I recall, didn't come with the latest patch. It has been present for some time now. I'm hoping some of the fixes they found to DX11 will apply to this, since I feel this is a lower priority issue.

Settings are at 'High', fullscreen*1080, Vsync Disabled, glow effects Enabled, AA Disabled.
And btw, my ping is very stable nowadays, usually 124-126ms. 130ms on rare occasions. Gets better! ^^

[zudukai]

I would like the team to look at the C2Q 8200 + Nvidia GTX460 combo, i used to get + ~ - 30~45fps now i get 20~30fps.

[MaverickCDN]

I was unable to play all weekend due to "Session was lost" errors occurring every time I tried to start the game. I was able to log in fine and the UI loads and shows my mc, c-bill and XP numbers after a short delay, but no mechs appear, and I after another short delay i get the "session was lost" message and am kicked back to the log-in screen.

I uninstalled and re-installed the game, updated all my drivers, and can play other online games just fine.

It looks like my connection was failing with 100% packet loss after the 11th hop (last succesful hop was border1.te9-1-bbnet2.tor001.pnap.net (70.42.24.196)) I am connecting from halifax Nova Scotia with Bell/Aliant fibreop and have never had connectivity issue before.


Any suggestions how to deal with this if it still a problem tonight?

Edited by MaverickCDN, 04 November 2013 - 06:39 AM.

[Durant Carlyle]

Sounds like the internet between you and Canada was having problems. That's not a MW:O problem.

[MaverickCDN]

I'm already in Canada, and MWO is the only thing I seem to be having a problem with.

[Durant Carlyle]

Sorry, didn't equate Nova Scotia with Canada. Been a while since my last Geography class.

You play anything else with a Canadian server in the same area a the server cluster for MW:O? If not, there's no comparison.

As I said, it's some router between you and the server cluster that's having a problem. Even if you were three hops from the cluster, if hop #2 was having problems, you still wouldn't be able to connect.

[JayVrb]

PRIMARY CONCERN: My FPS for my hardware (FPS should be higher)


How had the patch generally affected your performance?

• It's the same it's been for a few patches, which is poorer than expected considering my hardware

Whether there are specific points in the game when your performance changes.

• Definitely more towards the center of the map and where there is a huge brawl going on

What are your video settings, did you change them since last patch?

• Everything is maxed out. I notice a DECREASE in performance even when i LOWER my graphics settings. This confuses me.

Average FPS ingame and in the menus for previous patch and latest patch (Press F9 to see your FPS)

• Average hovers around 40fps, but often dips down to the 30's when it matters (e.g. brawls). In previous patches (months ago), it would stay consistently between 50 and 60.

System specs

Spoiler

Video: GTX 760 2GB
CPU: I5-2400 Sandy bridge 3.1GHz quad-core
Memory: 8GB DDR3 (Ripjaws X Series)
Motherboard: MSI P67A-G43f
Hard Disk: Samsung 840 Series 120GB SSD
OS: Windows 7 Professional 64bit
Resolution: 1366 x 768

Your advertised internet connection speed / Geographic location

• ~60mb down, ~10mb up; Memphis, Tennessee

Edited by Vrbas, 04 November 2013 - 11:46 AM.

[Durant Carlyle]

The reason why your performance gets lower when you reduce graphics settings is that at higher settings the GPU takes over a lot of the graphics capability. When you lower settings, there is less for the GPU to do and more for the CPU to do. MW:O already uses a lot of CPU (it's very CPU-dependent), so adding to the pile by lowering settings makes your performance go down.

Don't know why your overall performance is so low though.

[DustyLoft]

Well, last night was a mixed bag...

Spawning next to somebody with a ping of 832 (which stayed like that) wasn't great. It was like walking through treacle until I got some distance between us.

I also had some great rounds. Got 5 kills in one round, then later got a score of 104 (758 damage) in another round. Perfectly playable.

To be honest, although I only get a max of around 40 fps, I'm happy if it doesn't drop below a still fluid 25fps. It tends to drop to about that with multiple Mechs on screen, but is still fluid and playable. It is just the intermittent screen freezes that mess me up.

Well, here goes another hour or so...

[MetalMagpie]

I have my graphical settings on medium (with particle effects on low) and get no performance problems on any map apart from Crimson Straits.

On Crimson Straits I experience sudden sharp FPS drops that appear to be triggered by me looking in a direction where there are lots of objects (one of the worse places is in C3 looking under the raised area at all the pillars). This has got me killed a few times.

I've experimented running around Crimson Straits on testing grounds and saw drops to 25FPS while I was standing static in C3 looking at the pillars, and drops down to 19FPS whilst running in the water towards shore. The more individual objects I have in view, the lower the drops seem to be. The best I get on that map in Testing Grounds is about 41FPS (standing in the water looking out at the mountain with no buildings in view). Screenshots here.

My system specs are:
Processor: Intel Core2 Quad 2.4GHz
RAM: 4GB
Graphics card: ATI Radeon HD 4800 series (with 2GB memory)
OS: Windows 7

[Marvyn Dodgers]

Maverick - Truly a blind shot in the dark here, but have you tried running the repair tool post install to see if something is getting corrupted? Shouldn't impact your hop from Nova Scotia, but one never knows.

http://mwomercs.com/...public-release/

If no luck there, have you submitted a support ticket with a DXDiag and Omicron log attached?

Good luck with resolution.

[9H3X6]

Ongoing FPS reduction since Sept patches when user.cfg and 3rd party film grain fix was broken. (Or fixed from PGI perspective)

Although FPS is lower since August, it is acceptable in normal view. Both heat vision and night vision have massive drop of frame rate making it unplayable. I am constantly turning heat vision off in frozen city blizzards cause I cannot aim at 15 FPS...once heat vision off back to 30-55 FPS.

A recommendation. Please put a film grain option into the game. I just don't understand why the static...having FPS issues while rendering a feature which I feel makes the game look worse. As if MWO was rendering on my 46" TV via bunny ears. I've even hit the TV...no change in the static. Perhaps not as noticeable for one playing on a 27" @ 1920x1080...very noticeable on a 46" with the same resolution.

Running all maxed but post processing on low. V-sync off.

Spoiler

i7 920 @ 3.6Ghz
6GB 1600Mhz DDR3 triple channel
ATI 7870
X-fi music
Win7 64bit

Edited by 9H3X6, 04 November 2013 - 11:38 PM.

[FrogToad]

Not having any real gamebreaking issues myself, I noticed a lot of multiple disconnects during the previous two nights (8 PM to 11 PM GMT).

In one game 6 other players disconnected. 2 right at the start of the round, not unusual, but another 4 during the first 3 minutes.

First I thought that could be intentional disconnects, but in following rounds a lot mor multiple disconnects happened. Sometimes only 2 but more often 3-4.

Just thought I'd mention it here.

[MaverickCDN]

MaverickCDN, on 04 November 2013 - 06:34 AM, said:

I was unable to play all weekend due to "Session was lost" errors occurring every time I tried to start the game. I was able to log in fine and the UI loads and shows my mc, c-bill and XP numbers after a short delay, but no mechs appear, and I after another short delay i get the "session was lost" message and am kicked back to the log-in screen.

I uninstalled and re-installed the game, updated all my drivers, and can play other online games just fine.

It looks like my connection was failing with 100% packet loss after the 11th hop (last succesful hop was border1.te9-1-bbnet2.tor001.pnap.net (70.42.24.196)) I am connecting from halifax Nova Scotia with Bell/Aliant fibreop and have never had connectivity issue before.


Any suggestions how to deal with this if it still a problem tonight?

As of last night connection was back to normal (no dicconnects steady ping at around 30). Whatever had failed over the weekend, someone must have come in on Monday and fixed it up