40 replies to this topic

[MadLibrarian]

I'm not entirely sure, but it is probably related to the extreme light bloom on this map in the well lit areas near spawns. It seems to cause FPS drops in everybody, with some people freezing. There's probably nothing we can do individually to really fix it, besides turning particles down to help a bit, but they surely know about it by now. I don't know how it got out of the testing phase like this, but if they can resolve it without ruining the map, they probably will. Just a matter of them being able to dedicate the resources.

So for the time being, I just look at the ground after spawning and run to a darker area. Trying to fight in the well lit areas is even more of a death sentence than you'd expect. Just need to embrace the darkness while we bide our time.

[That Dawg]

MadLibrarian, on 13 October 2014 - 08:29 AM, said:

just look at the ground after spawning and run to a darker area.

I made laff upon that.
thats the preferred tactic of the pug teams I've had

[ViridianKnight]

alt tab it is for me , somtimes even twice

also semm to be some wierd lighting in the brighter areas, cocpit and mech txturs "shimmering/flickering"

[Big Tin Man]

Yup, freezes on startup. Alt + tab for me here. i7-930, GTX 750, 12 GB ram, SSD

I also get a significant amount of rubberbanding on this map as well. Running my ember is tough.

[Chaosity]

It sounds like some of the visuals on this map are pressing the limits on your CPU/GPU setups. Everyone who has had this problem and posted their equipment they use has older or less than "pushing technology's edge" stuff. Not your fault. You shouldn't have to have cutting technology hardware to play, but my guess is that PGI people do, so they seldom see this. Personally... i7-4820K, GTX-770, and SSD. Good when I bought it ages ago but not cutting edge today, but good enough that I don't have this issue with this map.

PGI: dig out some old hardware for your QA guys to test this kind of crap, PLEASE.

Edited by Chaosity, 13 October 2014 - 05:22 PM.

[WOLF PACIFIER]

I really tired from this map bug. Mining collective is great map, very cool. But when my screen turns black in the middle of combat... This is really annoying.

I must kill game process -> launch game again -> skip intro movies -> log in -> wait for connection -> wait for map loading -> watch how my mech was smashed.

During this amount of time I could restart my PC 2 times and this is will be faster than actions which I listed above.

Devs should fix this bug. Seriously.
Support is absolutely silent about this for now.

Edited by Siberian tiger, 15 October 2014 - 12:14 PM.

[Alexander Garden]

Hey everyone,

As far as I've seen every player who is getting this particular freeze issue is running on an NVIDIA GPU. During this time we've been running through some support tickets to narrow down a resolution, and I apologize sincerely for not addressing the forum posts sooner.

If you are running GeForce Experience and have applied Optimized settings to MWO, please remove the Optimized status and revert the settings to default (un-optimized).

Next, please perform the following steps:

• Manually download the latest NVIDIA driver set using the Manual Driver Search system here: http://www.geforce.com/drivers. Do not install them yet.
  
• Un-install your current NVIDIA drivers through the Windows Uninstall process.
  
• Reboot.
  
• Manually install the latest driver set you previously downloaded. Do not install the drivers using GeForce Experience. Please continue on to the next step before completing the install.
  
• During the install, select the Custom (Advanced) install option, then on the next screen, check the 'Perform a clean installation' box.
  
• Complete the install and reboot.
  
• Test for the persistence or resolution of the freeze issue.

Please let me know in this thread if you continue to experience freezing after performing all of the above steps. Apologies again for the delay.

[WOLF PACIFIER]

Alexander Garden, on 15 October 2014 - 02:06 PM, said:

Hey everyone,

As far as I've seen every player who is getting this particular freeze issue is running on an NVIDIA GPU. During this time we've been running through some support tickets to narrow down a resolution, and I apologize sincerely for not addressing the forum posts sooner.

If you are running GeForce Experience and have applied Optimized settings to MWO, please remove the Optimized status and revert the settings to default (un-optimized).

Next, please perform the following steps:

• Manually download the latest NVIDIA driver set using the Manual Driver Search system here: http://www.geforce.com/drivers. Do not install them yet.
  
• Un-install your current NVIDIA drivers through the Windows Uninstall process.
  
• Reboot.
  
• Manually install the latest driver set you previously downloaded. Do not install the drivers using GeForce Experience. Please continue on to the next step before completing the install.
  
• During the install, select the Custom (Advanced) install option, then on the next screen, check the 'Perform a clean installation' box.
  
• Complete the install and reboot.
  
• Test for the persistence or resolution of the freeze issue.

Please let me know in this thread if you continue to experience freezing after performing all of the above steps. Apologies again for the delay.

This is not fix the problem at all. I exactly followed your instructions. Step by step. I've played this map today 2 times. 1 crash.
I assume you should dig solution on the game side. These game crashes occur on this particular map. If you can't fix it now may be then you will temporarily exclude map from the list or something? (Because Nvidia users are dominating above amount of AMD users(or start a massive testing on test servers)) This bug is ruin enjoying from the game.

EDIT: I've played this map 6 times today. 3 times I got crash to desktop. 50% chance.

Edited by Siberian tiger, 16 October 2014 - 09:17 AM.

[Lily from animove]

That Dawg, on 12 October 2014 - 07:23 PM, said:

Its getting worse. What started out as jitters, hangs, lag, turned into this, and the effect is lasting longer. The ONLY map that does it-
The odd defects 4-5 days ago were tiny. now they obliterate the screen





I'm almost beginning to think it happens in the same area of the map, always at the beginning of the match.

can you try to recreate that in the testing grounds?
Maybe your GPU reaches some limits, what GPU do you have?. The last screen looks very much like the GPU having issues to build up the environment fast enough.
otherwise,stop origami during battles xD

Alexander Garden, on 15 October 2014 - 02:06 PM, said:

Hey everyone,

As far as I've seen every player who is getting this particular freeze issue is running on an NVIDIA GPU. During this time we've been running through some support tickets to narrow down a resolution, and I apologize sincerely for not addressing the forum posts sooner.

If you are running GeForce Experience and have applied Optimized settings to MWO, please remove the Optimized status and revert the settings to default (un-optimized).

Next, please perform the following steps:

• Manually download the latest NVIDIA driver set using the Manual Driver Search system here: http://www.geforce.com/drivers. Do not install them yet.
  
• Un-install your current NVIDIA drivers through the Windows Uninstall process.
  
• Reboot.
  
• Manually install the latest driver set you previously downloaded. Do not install the drivers using GeForce Experience. Please continue on to the next step before completing the install.
  
• During the install, select the Custom (Advanced) install option, then on the next screen, check the 'Perform a clean installation' box.
  
• Complete the install and reboot.
  
• Test for the persistence or resolution of the freeze issue.

Please let me know in this thread if you continue to experience freezing after performing all of the above steps. Apologies again for the delay.

Well this is honestly not a good solution. If it even works. I have more or less to solve any IT related issues within my family circle. And some people are not very familiar to stuff like described above. They just start their PC and are able to do basic stuff.

I hope you can fix this soon.

[Alexander Garden]

If running a clean install with the instructions outlined above doesn't do the trick, another potential fix confirmed to work for some players is to roll-back your driver set to 340.52.
(And I can't stress enough the importance of running a manual, Custom, clean install with each install of a particular driver set; GeForce Experience and automatic installs seem to be increasing the frequency of these problems).

I do understand that these workarounds are not ideal fixes (nor are they seemingly guaranteed), and I do apologize sincerely for the frustration, but while we continue to work on a proper back-end fix these are the best options currently available.

Please be assured that we're continuing to work on a final resolution for this.

[Deathlike]

Ironically, I'm not suffering from this, running a GTX650 (1GB) with the latest WHQL drivers (344.11) on Win7 64-bit.

I run everything on low (still running a Core 2 Quad Q9650) except textures (medium) and shaders (very high), object detail (very high) with VSync off and Glow Textures off (don't want to saturate video memory unnecessarily).

For NVidia's settings, I run the following relevant ones:
Ambient Occulsion: Off
Anisotropic Filtering: App Controlled
AA - Gamma Correction: On
AA - Mode: Off
CUDA - GPUs: All
Max pre-rendered frames: App Controlled (Use 3D App Settings)
Multi-Display/Mixed GPU Acceleration: Multiple Display Performance (switch it to single if you run one monitor only)
Power Management Mode: Prefer Max Performance
Shader Cache: On
Texture Filtering - Anisotropic sample optimization: Off
Texture Filtering - Negative LOD Bias: Allow
Texture Filtering - Quality: Quality
Texture Filtering - Trilinear optimization: Off
Threaded Optimization: Auto
Triple Buffering: Off
Vertical Sync: Use 3D App Settings (Adaptive works nicely w/o issue, including the half adaptive option)
Virtual Reality prerendered Frames: Use 3D App Settings

This may be helpful, but doesn't guarantee anything. It may be a good idea to clear out MWO's shader cache if you haven't done it in a while.

[WOLF PACIFIER]

I also suspect Windows 8.1 incompatibility or bad AMD CPU's coding.

Deathlike, on 16 October 2014 - 12:18 PM, said:

Ironically, I'm not suffering from this, running a GTX650 (1GB) with the latest WHQL drivers (344.11) on Win7 64-bit.

I run everything on low (still running a Core 2 Quad Q9650) except textures (medium) and shaders (very high), object detail (very high) with VSync off and Glow Textures off (don't want to saturate video memory unnecessarily).

For NVidia's settings, I run the following relevant ones:
Ambient Occulsion: Off
Anisotropic Filtering: App Controlled
AA - Gamma Correction: On
AA - Mode: Off
CUDA - GPUs: All
Max pre-rendered frames: App Controlled (Use 3D App Settings)
Multi-Display/Mixed GPU Acceleration: Multiple Display Performance (switch it to single if you run one monitor only)
Power Management Mode: Prefer Max Performance
Shader Cache: On
Texture Filtering - Anisotropic sample optimization: Off
Texture Filtering - Negative LOD Bias: Allow
Texture Filtering - Quality: Quality
Texture Filtering - Trilinear optimization: Off
Threaded Optimization: Auto
Triple Buffering: Off
Vertical Sync: Use 3D App Settings (Adaptive works nicely w/o issue, including the half adaptive option)
Virtual Reality prerendered Frames: Use 3D App Settings

This may be helpful, but doesn't guarantee anything. It may be a good idea to clear out MWO's shader cache if you haven't done it in a while.

This is not a settings issue. Other maps works well.

Edited by Siberian tiger, 16 October 2014 - 12:56 PM.

[LordLosh]

STILL having issues with this map. I would say 85% chance I will crash to desktop when playing this map. Getting old. I run max settings on all other maps and have never had a problem. Really hope the new map is better than this one.

[KodiakGW]

Siviiliuhri, on 28 September 2014 - 01:49 AM, said:

I have the same problem but atleast for me this works as a workaround: When things lock up I atl-tab out to desktop and go ctrl-alt-del and open task manager...before doing anything else the MWO unlocks in the background and works normaly . I have no idea why this works but I have 100% success with it so hopefully it helps you too...

Confirmed. Works for me 100% of time when it freezes. But, If I don't do it too quickly, CDT.

[Mechwarrior Buddah]

Anyone else fallen through the map there?

[L e x]

KodiakGW, on 13 November 2014 - 08:46 PM, said:

Confirmed. Works for me 100% of time when it freezes. But, If I don't do it too quickly, CDT.

Exactly the same for me. Alt-Tab out and then back in fixes it, but only if I do it within about 5 seconds. Any longer and the game just cfrashes to desktop.

This REALLY only happens on Mining Collective for some reason.

[That Dawg]

Alexander Garden, on 15 October 2014 - 02:06 PM, said:

Please let me know in this thread if you continue to experience freezing after performing all of the above steps. Apologies again for the delay.

God I HATE it when you guys act like you care. And stuff.

I checked back in the thread FTHOI and spotted the note about nvidia, got the latest drivers, will do the un-opt thing and feed back later.
whoot

[That Dawg]

Nothing yet, removed the profile entirely from the Nvid control panel
Feels like a performance hit, but seems offline runs smooth and fps into the 80's
online not so much.
Have not had Mining since the change...figures, LOL, every other map last week, now, Caustic and Alpine!

If you do remove the profile, remember to delete the c:/mwo/user/shader cache
to load the new values.

[KursedVixen]

this map still crashes games... just crashed on mine the other day.

this map is constatly voted for just for this reason to crash people and make them Angry PGI really needs to remove this map.

Edited by KursedVixen, 05 March 2016 - 09:47 PM.

[Benjamin357]

The legacy mining collective issue had to do with DirectX versions, downgrading to 9 would fix it back then. I have not seen that personally in quite a while; running gtx550ti, with the 362 driver version and DX11 on Windows 7.