23 replies to this topic

[Grendel408]

I've determined it's an issue with DX11 and both the 32bit and 64bit client modes. Before I used to have CTD's with an error explaining a D3D or DX error and the GPU driver crashed and recovered, ultimately crashing your game on top of it. Now... I don't get the error, just in-game (mechlab and matches) where the game freezes for 5-10 seconds (crucial time while in the middle of battle btw) and recovers while warping me somewhere forward of my original position depending on the speed of throttle. VERY VERY annoying... and has cost me a handful of matches where I likely would have survived had that not happened.

PC specs above recommended, GPU drivers updates, PC drivers (all updated), clean install, even went so far into my registry to inspect things. GPU Manufacturers claim it's not their card, stress tests prove it's not the GPU. It's MWO that is not optimized very well at all causing these issues. Problem became more prevalent after installing Win10x64. Prior to Win10 I would get a CTD and error message. I don't file tickets anymore because when MWO crashes I get that little report thingy popping up and sending data to PGI (I hope). That and the normal response to filing a support ticket is too long to stay current with so I just keep grinding... occasionally restarting my PC as needed.

Might as well mention this too... running Teamspeak and using VOIP in MWO has issues... if I run MWO without TS, in-game VOIP works fine...

There are a good handful issues PGI must resolve if they wish to continue to bringing out more content, take a break in adding content (Mechs) and take time to "spring clean" the game is greatly needed. We need a thorough quality check on MWO.

[Lunatic_Asylum]

I think that I might have a hint to a solution (but not a solution).

The problem is "DXGI_Device_Removed" that does not actually show up, and the game resumes playing, creating microfreezes. It does appear on both DX9 and DX11 and in other games, actually. Back in 2014, NVidia drivers worked well.

Something is happening between NVidia and games (this bug was in other game in 2012 as well, but was fixed in 2014 and botched up in 2015 again). I am sure that someone mentioned that Radeon has similar problems.

If you are an NVidia user, try to install the 344.11 drivers.

Depending on the DX9/DX11 selection, graphic details, and games, the bug may occur more often or rarely. Usually, switching to DX9 and the lowest details possible created only 1 such occurence per hour. It gets to 1 per minute sometimes at DX11 with maximum settings.

I have been into that problem since 2012.
I narrowed it down a bit.
- some NVidia drivers from 2014 solve this problem;
- this is not overheating or overclocking;
- this is not a graphics card (however, some cards crash less often);
- this is not a particular game (however, some games never have this error).

I tried a lot of PC configurations and could always reproduce the bug on NVidia and Intel computers on various Windows 7 x64.
Reproduced on:
i3 with ASUS GTX460 768MB 8GB RAM W7 Ultimate x64
i5-3570 with ASUS GTS450 1GB RAM W7 Home x64
i7-930 with MSI GTX680 2GB RAM W7 Ultimate x64

I sent the message to the support.

Edited by Lunatic_Asylum, 14 December 2015 - 08:52 PM.

[mr bear]

http://mwomercs.com/...-stop-freezing/

Cross posted. Not quite sure if solution mentioned will work.. but seems to be the same problem we are all experiencing..

[Lunatic_Asylum]

mr bear, on 14 December 2015 - 11:05 PM, said:

http://mwomercs.com/...-stop-freezing/ Cross posted. Not quite sure if solution mentioned will work.. but seems to be the same problem we are all experiencing..

I am running Avira and Spybot, and my freezes are of a different nature, unfortunately (DXGI_error minicrashes without any output on the screen: the game just lags for a second).

Edited by Lunatic_Asylum, 14 December 2015 - 11:24 PM.