33 replies to this topic

[Agrikaan]

Yeah... Patch.

On my two older W7x64 PC's, the MechWarrior (from Steam) crashes to desktop.
On my new W10x64 PC, the MechWarrior (from Steam) crashes the PC.

Nice.

---

On a more general note that have driven me mad for two decades. A game should be able to start using the current monitor resolution. Now this MechWarrior game, using CryEngine, every single time, even if for just a microsecond, it manages to reset and/or move my windows, gadgets and other applications (music player, web browser) around. To where I certainly don't want them.

I am this close to implementing a policy to uninstall and refund every game that does this during startup, or even during the first installation. Lots of games does this, in 2016.

Somehow games, while requiring DX11, 2GB RAM, 100GB drive space and Win7 and such, still defaults to an 800x600 resolution, just in case my PC is an x486 from 1996. Yeah, that *could* happen.

Other games, some of them over 10 years old, don't. Like Assassins Creed 1 (just replayed it), it set itself to the monitor resolution as default. So if Ubisoft could do it in 2007, anyone can in 2016. It can't take even an average skilled programmer more than 2 hours to get this done.

So get it done. So I can start even one game of the otherwise great MechWarrior Online game, without being pissed.

Edited by Agrikaan, 22 January 2016 - 10:10 AM.

[Teefrs]

Fix your ****.....

[Liveish]

have to remove my profile every time if i want to play now. ( waiting on support)

[Christopher Hamilton]

tried removing shader cache, still crash. I enter login data and MWO ceases to exist.
I can play random matches with no issue, but had a total of 7 crashes on CW Emeralt Taiga Attack as attacking faction.
I did a total of 49 damage - as soon as something moved, some interaction took place or i entered center of facility -
it either crashed (sending a report) or stuttered and hung up everything (in one case forcing me to cold boot, in another still capable of task-manager-killing it - with very slow task manager.

i suspect two things:
- parser or config error in startup code
- some gfx or memory management bug that is triggered under load (the CW triggers it only during fights, instabrawl doesnt.)

[Fat Jack Murphy]

Same issue as Christopher here, havent tried CW drops after listening to his crashfails on TS.
Win 7 64 bit, DX9 client.
32 gb ECC memory, dual quadcore xeon, R9 390, current stable driver. filesystem checks, disk error summary clean. repair tool and render cache cleaning didnt help.
forcing 32 bit to be able to play at all, 64bit client crash on login confirmed.
32 bit client occasionally crashes with no appearant motivation.

please fix.

[ItchyTriggerFingers]

anyone had any luck with a fix ?

[AssaultPig]

forcing the 32bit client fixed it for me, at least for the time being

irritating though

[Tarl Cabot]

https://mwomercs.com...__fromsearch__1

Download and install both Microsoft Visual C++ 2010 Redistributable Packages, x86 AND 64x. Some players had to uninstall them then re-install them to successfully install them and to get MWO working.

https://www.microsof...s.aspx?id=17718
Also download and install dotNet4 for both x86/x64.

On windows update, make sure ya have selected recommended downloads also.

Edited by Tarl Cabot, 27 January 2016 - 07:27 PM.

[AssaultPig]

re-installing the c++ distros doesn't seem to have helped

can't install dotnet4 since I already have a higher version

[ItchyTriggerFingers]

After speaking to support for the last week, i get the feeling they are not sure how to fix it

Can you confirm the following

What OS ?
Video Card ?

Edited by ItchyScrot, 04 February 2016 - 12:48 AM.

[Túatha Dé Danann]

It ran fine until today. Now I get crashes every time I Alt+Tab.

Specs:
Win 10 64 bit
Newest drivers from AMD (16.1.1)
Asus Rampage IV Extreme BE
Intel Core I7 4930K @ 4.2 GHz
AMD Radeon HD 7970 (slightly overclocked, passed every stress test I threw at it)
Crucial MX-200 1TB SSD
32 GB RAM @2133 MHz

Error notification say:
Bad D3D call, driver at bad state, may be caused by stuff like:
- overclocking (nope, its stable)
- bad driver installation (nope, runs fine on every other game too)
- bad program code that may cause bad driver state (jep, thats it)

Why? Because the 32-bit version works, the 64 bit version of the client not.
Update:
It crashed under 32 bit too, but once I switched to DX 9, everything is fine - even 64-bit mode.

Edited by Túatha Dé Danann, 09 February 2016 - 08:58 AM.

[Teefrs]

for me i have found its something with dx9....but if i use dx11 its fubar also....dx9 crashes to desktop on startup.....if you have not deleted that bit from the profile....dx11 loads with the whole profile...but it leaves the screen resolution all wonky.

[Wonderdog]

I'm getting the same issue since recent patch (not sure which one).

Regular CTD with error report submission after a while. Intel 6700k + 980Ti - seems to get worse if I'm doing a lot of alt-tabbing to desktop while waiting for queues to proc.

#Wonderdog

[GZeorymer]

I have been getting these odd crashes as of late either, the client has NEVER been this unstable since...well...ever? I've been playing it since the beta days *points to founder tag*,and for some reason over the last few days...I can't even stay in a game because the first few seconds I'm in...it crashes...the details of what they are I'm gonna put in a link here, since I made a thread about this problem...

http://mwomercs.com/...deo-card-error/

On another note, here are my current specs;

Win7 64bit
3.40GHz Quad Core
8 Gigs of Ram
Geforce GTX 580

My computer stresses more trying to run Guild Wars 2 with nearly a hundred players in one screen on it's engine (My heat monitor will tell me my CPU works hard on it), yet something like MWO has NEVER pushed my CPU hard, yet I'm crashing. I managed to run the latest batch of crashes in full window mode and I copied two messages;

"Fatal Error:
Present returned status DXGI_ERROR_DEVICE_REMOVED this can happen for a number of reasons:
* The underlying hardware is unstable (check voltages, etc)
* The display driver encountered a bad state (ensure drivers are up to date with latest fixes)
* The game issued a bad D3D command causing the driver to enter a bad state (log an
issue stating the exact steps that resulted in this error occuring) For more information
please refer to the games knowledge base
Reason = D3D Device Hung"

The second message which is at my lower right hand tab reads;

"Display driver stopped responding and has recovered:
Display driver NVIDIA Windows Kernel Mode Driver, version 361.75 stopped responding and has successfully recovered"

Now, this seems to have been happening over the last few days; my drivers are up to date, I ran the repair tool on my launcher (it's not from steam). It says it has no errors or misplaced files but I let it clean the cache anyway. I'm still getting this exact same crash. What's more, it seems to have been happening more often when I pilot light mechs, not sure if it has to do with the game trying to render the mechs themselves and failing, or the environment as they move fast.

I'm reading that some people think the client's more stable when it's running in 32-bit mode, can anyone confirm if this is a work around?