Jump to content

Screen Freeze(But Game Still Works)


13 replies to this topic

#1 iiDeadSeriousii

    Member

  • Pip
  • 13 posts
  • LocationProvidence, RI

Posted 20 December 2014 - 09:09 AM

I'm having a problem where a few seconds after logging in and being in the Mechlab (or any screen after log in) the image just freezes on the screen. I can move the mouse around, the music still plays, and I confirmed that I can even start a game. I click on Play Now and managed to blindly click the start game feature. The game even starts all the way up and I can hear all the game action going on, but yet I'm still sitting there staring at my mech in the main screen.

This happens every single time without fail and only started happening after the latest update. Should I go ahead and just uninstall the game and try again? Has anybody else encountered something like this?

#2 iiDeadSeriousii

    Member

  • Pip
  • 13 posts
  • LocationProvidence, RI

Posted 20 December 2014 - 12:24 PM

Just completely uninstalled the game and it happened again. After about 20 seconds I was going through the settings trying to restore everything back to how I had it and the mouse kept moving, sound kept playing, I was able to click options on/off but the screen was just frozen.

#3 9erRed

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • 1,566 posts
  • LocationCanada

Posted 20 December 2014 - 04:42 PM

Greetings,

Check for an update to 'flash player' and any windows updates.
- After the last patch and the ability for 64bit starts windows may need to update some items.

Read the patch notes and Client updates for the links to 'required' elements that must be updated or at least checked for most resent versions.
- See here: http://mwomercs.com/...bit-mwo-client/
- And here: http://mwomercs.com/game/patch-notes

As a note, if you 'tab out' of MWO mechlab and back in is it still locked/frozen?
- Is there actually a 'warning window' in the background that is requesting a response? And locking the window till it's responded to.

9erRed

Edited by 9erRed, 20 December 2014 - 04:43 PM.


#4 iiDeadSeriousii

    Member

  • Pip
  • 13 posts
  • LocationProvidence, RI

Posted 24 December 2014 - 01:55 PM

9erRed I've tried switching between the 32-bit and 64-bit client and neither seemed to make a difference. I've also made sure my DirectX and C++ Dist. were updated. I had newer versions in both cases from the link you shared with me.

There is no error message in the background. I've run the game windowed and fullscreened and Alt+Tabbed out just to see and nothing is there. It's as if the game is still running entirely other than the image on the screen is frozen. Sound is still playing and the mouse is still visibly moving.

It's very discouraging especially since CW launched and I haven't been able to get this working.

#5 9erRed

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • 1,566 posts
  • LocationCanada

Posted 24 December 2014 - 07:32 PM

Greetings,

Reference the Dx codex.
- download the file not run from site, then select run as admin for the file. there are items that are from the Dx9c install that will not get installed if your current version just stops it with the reply you saw.

- Also check your Video card drivers and what the latest download is. For Nvidia they just released a new driver 23Dec.
- Also check the Nvidia control panel for it's options reference MWO, if Nvidia.

As you stated, the game is still running but you can't see it, a driver issue for display most likely.

Good luck, and merry X-Mas,
9erRed

Edited by 9erRed, 25 December 2014 - 09:55 PM.


#6 badaa

    Member

  • PipPipPipPipPipPipPip
  • 735 posts

Posted 24 December 2014 - 08:37 PM

i get the same thing just alt - tab that should fix it

#7 Keira RAVEN McKenna

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 878 posts
  • LocationAuckland ...but summer has gone and the tears now flow

Posted 24 December 2014 - 10:03 PM

I hit the task manager as soon as mine does it then straight back to the game and it resumes.

#8 Stealth Fox

    Member

  • PipPipPipPipPipPipPip
  • Big Brother
  • Big Brother
  • 736 posts
  • LocationOff in the Desert

Posted 24 December 2014 - 11:10 PM

I feel you on this one dude, Mine will happen mid game sometimes, just gotta kill throttle. tell my team on comms to cover my dumb arse and alt tab out and back in. Solves it every time so far, but as for entirely mitigating the issue? I can't say.

#9 Keira RAVEN McKenna

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 878 posts
  • LocationAuckland ...but summer has gone and the tears now flow

Posted 25 December 2014 - 02:07 AM

View PostSeph MacLeod, on 24 December 2014 - 11:10 PM, said:

I feel you on this one dude, Mine will happen mid game sometimes, just gotta kill throttle. tell my team on comms to cover my dumb arse and alt tab out and back in. Solves it every time so far, but as for entirely mitigating the issue? I can't say.

it literally takes seconds...

#10 iiDeadSeriousii

    Member

  • Pip
  • 13 posts
  • LocationProvidence, RI

Posted 25 December 2014 - 10:14 AM

Used the repair tool and it said there was nothing wrong but clicked the "Fix" button anyways and it got it working again. There was a "ghosting" effect of the main screen (i.e. my mech in the mechbay being superimposed over whatever was on screen at the time) that would flash every time I stood still in game. It's almost as if when the game isn't rendering anything new video-wise it refers back to that "first" image it sees when the game logs in. Does that make sense?

Like 9erRed said it's gotta be something with the drivers (I'm always on the latest Nvidia beta drivers) not behaving right with the game. Or a combination of the game, my drivers, and my rig setup. Idk but it's working in some capacity even though it's not ideal.

Btw Alt+Tabbing does not work for me. It would just bring me back to the same state I was in.

#11 9erRed

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • 1,566 posts
  • LocationCanada

Posted 25 December 2014 - 09:57 PM

Greetings,

Check your task bar options, just to see if it's set to combine tabs or keep them separate.
- The game should drop the mech-lab screen to the taskbar during the in-game match, or just remove it till again requested.
- This does not appear to be happening with you and it stays open as a secondary window, which could be at a different screen resolution.
- There are a couple of images that are presented when in-game, some are always there but in transparent mode till called, the terrain, the mech cockpit, the mini map, the large map window. Others get called to overlay the main window, the 'tab' window for Pilots and info and the 'esc' key for options.
- From your last post it appears that the Mech-lab window is 'not being removed' during gameplay.
(look a your options for the game display size to see what the resolution is set for, and if this is the same as the mech-lab size.)
~ at one time PGI locked the Game to a specific size and the players options zoomed or shrank that default size, this has changed with the 64bit exe. There is still a scaling issue with multi monitors or more than one, not resolved yet.

The computer may be attempting to hold the game resolution and conflicting with the mech-lab screen size resolution, causing the flashing.

Just some ideas, no solutions that define the exact cause but overlapping windows of different resolutions always cause problems. Some of the older Mech games had this problem (displaying smaller video windows) as would flash or crash when it happened.

9erRed

Edited by 9erRed, 25 December 2014 - 10:00 PM.


#12 Darzok

    Member

  • PipPipPipPipPipPip
  • The Scythe
  • The Scythe
  • 255 posts

Posted 27 December 2014 - 04:30 AM

Its an on going bug that has not been fixed since the Beta as you can see if you scroll back enough on the forums.

The dev's know about the bug there was a post around Oct if i recall saying we are looking in to it but NOTHING since then and it seems to be spreading again and effecting more and more people like it did back in the beta.

Edited by Darzok, 27 December 2014 - 04:36 AM.


#13 Beaching Betty

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 710 posts
  • Location-

Posted 29 December 2014 - 02:00 AM

Mind telling us your system spec?

I used to have this problem too, not on this game but other games too! It always freeze without warning and it annoys me but then, I found a permanent fix FOR ME, I don't know if it will work for you.

If you have a Nvidia GPU, you can try downloading NVIDIA INSPECTOR, its an overclocking tool BUT we wont be using it to overclock but to downlock the memory of our GPU. So what I did was I open it up, and then I decrease the memory clock offset (not the core clock) of my GPU to -250 and it works now, no more crash, no more sudden freeze, the game runs smoothly :) If you dont have Nvidia, you can just use MSI AFTERBURNER and do the same, decrease the memory clock to -250.. though yours does not have to be precisely -250, you can try from -100, if it crash, change it to -150 until you find a perfect one.

EDIT: Oh you have Nvidia, great haha. and if you try my option and it works or not, do lt me know.

Edited by Pisang Panas, 29 December 2014 - 02:02 AM.


#14 Darzok

    Member

  • PipPipPipPipPipPip
  • The Scythe
  • The Scythe
  • 255 posts

Posted 31 December 2014 - 02:41 PM

View PostPisang Panas, on 29 December 2014 - 02:00 AM, said:

Mind telling us your system spec?

I used to have this problem too, not on this game but other games too! It always freeze without warning and it annoys me but then, I found a permanent fix FOR ME, I don't know if it will work for you.

If you have a Nvidia GPU, you can try downloading NVIDIA INSPECTOR, its an overclocking tool BUT we wont be using it to overclock but to downlock the memory of our GPU. So what I did was I open it up, and then I decrease the memory clock offset (not the core clock) of my GPU to -250 and it works now, no more crash, no more sudden freeze, the game runs smoothly :) If you dont have Nvidia, you can just use MSI AFTERBURNER and do the same, decrease the memory clock to -250.. though yours does not have to be precisely -250, you can try from -100, if it crash, change it to -150 until you find a perfect one.

EDIT: Oh you have Nvidia, great haha. and if you try my option and it works or not, do lt me know.


I am not willing to mess around and maybe damage the GFX card just to fix a problem the Dev's should of fixed ALONG TIME AGO this has been going on for months for some people since BETA.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users