122 replies to this topic

[Sjorpha]

I have updated drivers and a Geforce 750 GT 2GB, running the game on a windows boot on my Macbook pro. Game runs fine FPS wise on mixed medium-high settings, hovering between 40-65 fps, but I am still getting frequent screen freezes and CTDs, especially on The mining collective.

[SI The Joker]

Processor: i5 650 3.20GHZ
Memory: 8gb RAM
Motherboard: Asus P7P55D Pro
Graphics: 1 x GTX 670
Sound: Creative SB xfi

Prior to the patch, the game would freeze every once in a while and I could get around it by dumping out to Task Manager (CTRL ALT DEL) and then hitting ESCAPE key to take me back into the game.

Like others, after the patch I am now experiencing hard freezes in Mining Collective only. That does cause the game to hard-crash.

In general, I am still experiencing sub-par frame rates when I look at others' rigs here on the forums. I see these folks posting frame rates of 100+ with GTX cards that are lesser than mine and I barely pull 40 without a firefight going on... so I am definitely looking for any solution to get more frames out of this game.

Keep at it guys!

Edited by SI The Joker, 04 November 2014 - 05:34 AM.

[ImperialKnight]

Haven't had the freeze bug on Mining Collective since I updated the drivers. Fingers crossed.

i5-3570K. GTX970

[veedubfreak]

No freezes or crashes here. But I literally get 0 benefit from my 2nd card.

SLI 970 with i7 4770k @ 4.6ghz.
Win 8.1

[B0oN]

Will do .

[Alexander Garden]

Okay, so they rolled out 344.60 earlier today. Still trying to compile info on what kind of effect the new driver set may have.

[DjPush]

I am downloading the 344.60 driver now. With the .44 driver I would get flickering in the mech bay with SLI turned on and when I lanched the flicker parts of the mech bay would be on screen in the cockpit (like an overlapping image). I will try the new drivers and let you know if that has changed anything.

[DjPush]

This is what I was trying to get at in the last post. Fresh instal of drivers (downloaded from website and not through Geforce experience)
Driver: 344.60
FX 8320
GTX 770 4GB (SLI)
16 GB DDR3 @ 1600MHz


Tried to make a video of it using Shadowplay and the game crashed. Hope this helps you guys.

[Alexander Garden]

Okay, thanks Dj. We weren't too confident that this release would be bringing any SLI improvements (or fixes).
Communication with NVIDIA to iron out these problems is on-going.

That being said, feed me all the info you can about its influence on screen freezing.

[Alekzander Smirnoff]

I'm having the EXACT same issue as DjPush above, getting ghosting of the mech lab while playing and a horrible frame rate around 20/s with the 344.60, prior to this driver I was running the WHQL version 344.11. Did a clean install and I get the above issue.

AMD 955BE @ 3.2ghz
2x EVGA GTX 760SC in SLI
8GB DDR3 1600
Vista x64
DX11
Very High settings on everything except shadows and blur set to low.
Also just occurred to me, I've got it set in full window mode.


Going to try it in single gpu mode and see what it looks like then update this post.

After playing a match on HPG manifold, which I also want to point out it appeared AMS was shooting missiles down from the basement to missiles being fired from above with no line of sight from the ams to possibly even shoot at missiles. Single GPU mode I was getting between 25-70fps depending on what was going on. Going to see what happens when forcing the other SLI types does.

Forcing them yields the same results, horrible frame rate but no crashes.

Edited by Alekzander Smirnoff, 04 November 2014 - 04:43 PM.

[Bigbacon]

have you guys tried turnoing the graphics down especially post processing?

I used to pplay with all settings very high and AA on. I was having the same issue as you and turned off AA and dropped all settings to High and it went away.

also...where cna you get the new driver? I don't see it on nvidia's website the 344.60 nm...oddly if I pick 400 series it doesn't show but pick 900 and it does show the 400 series as compatible.

i still get a tiny bit of flicker in the mech bay but nothing else.

Edited by Bigbacon, 04 November 2014 - 04:07 PM.

[Goose]

Seems worse, to me: I even have this hesitation, now, when I torso-twist …

[SubXulu]

I am still getting screen freezes :|

[Asmodeus8888]

The release brought NO SLI Improvements

[Alekzander Smirnoff]

I've noticed with the two drivers past 344.11 that it microstutters a bit more in single GPU mode than it used to in that particular driver. I get little tiny freezes that last maybe 2-3 frames when whipping the torso around as well. As to SLI and testing it in various manners yesterday, I'm leaving it off until the next driver comes down the pipe.

[Alekzander Smirnoff]

Also of note, I don't know if this is unique to me but I have a logitech G510 keyboard with the little LCD display that I usually have EVGA precision dumping out information on my video cards. It appears the game isn't using the primary GPU nearly as much as the secondary. To the point that (with adaptive power management being the default now for nvidia cards unless forced off) GPU one will down clock almost 50% from maximum (boost clock) while the secondary sits at the base clock (not boost clock) level.

[Twilight Fenrir]

Well, I updated to the newest driver yesterday, and I'm still having issues...

I've got an Nvidia GTX 570, and really often when I go to leave match, the game crashes to desktop with no error message. it's just gone.

ALso, a more recent development, occasionally when I start the game, after putting in my password and logging in, it crashes my graphics card. This actually produces an error message, seen below. This also royally screws up Firefox.

[Alekzander Smirnoff]

That error looks like its not driver related, but directx api related. Might want to pop over to Here (microsoft's DX support/download page) and grab both the 9.0c and 11 versions and run them both. See if that helps, since the crash also affects, in your case, firefox, then it is probably crashing the DX API and not the nvidia driver since modern web browsers use direct draw and direct 2d as well (sometimes OpenGL as well which is included in the nvidia driver package).

[Giggity]

Give this a try.
Go into the NVIDIA controll panel/select manage 3D settings/click the program settings tab/ select MWO/scroll down to SLI rendering mode/ select force alternate frame rendering mode 1. It stopped the flickering and ghost mechlab for me and gave a slight boost in frame rate. Play with it might make you happy. Giggity

[WaddisznoHUN]

Giggity!

I try your suggest and you're right. My rig is a Core i7 965EE with 12 GB ram and a Nvidia Gtx 590 card in watercooling. In Dx11 after i try the forced alternate rendering mode the sli works normal, gone the ghost picture from mechlab, gone the flickering on the mech, and finally all two core utilising between 50-58 % per core. My fps in testing grounds constant 60 fps, i allways using vsync because i hate the microstutter.... tomorrow i try in 12 vs 12 match.....Thx for the useful tip.

Sincerelly

Waddiszno

Edited by Waddiszno, 07 November 2014 - 11:35 AM.