29 replies to this topic

[80sGlamRockSensation David Bowie]

I'm convinced its an issue with the map itself and not entirely just a texture issue.

Similar to that giant light box hovering over the Tunnel in Forest Colony causing a shitstorm of bad frames, there is something inherently broken with this map being added early to the game with a much less experienced map team.

[Cest7]

Seems that when this bug happens to me, it happens after every SECOND drop on frozen city after deleting shaders.

[Shamous13]

Cest7, on 13 February 2014 - 12:04 AM, said:

Seems that when this bug happens to me, it happens after every SECOND drop on frozen city after deleting shaders.

you could try this don't know if it will work for you but it has worked for most people.

Albert Meyburgh, on 06 February 2014 - 02:40 PM, said:

vsync makes the shaders rebuild so it's probably related to a bug we've been tracking regarding the game getting corrupt during async shader compilation. we're possibly turning off async shader compile when dx11 is released but it's not my dept so I'm not sure. In the meanwhile if you delete your user shader cache, run the repair tool, and add r_ShadersAsyncCompiling=0 to your user.cfg it MAY resolve the issue but no promises for now

Albert Meyburgh, on 07 February 2014 - 09:47 AM, said:

sorry I should clarify, if you follow these steps as I suggested, you can turn vsync off again, and since async compiling is disabled with that user.cfg flag, the corruption would thus be avoided in the future... so it is a permanent workaround in theory with no need to rely on vsync to force a rebuild... but no warranty as I said I am just throwing it out there since I can appreciate the frustration.

[Butane9000]

Egomane, on 11 February 2014 - 06:35 AM, said:

Did you try the workaround explained in this thread?

As the workaround comes from a developer, it shows that they are aware of it and are looking for solutions. In the linked thread Matthew Craig even told us that they are working on a long term solution with the soon incoming (in march or maybe even next week) implementation of the DX11 render path. That is not refusing to fix it, in my eyes.

@Shamous13
Thank you! Worked for me without the repair tool, but it's still a step that should be performed.

I did try this fix. It worked for one day before happening again. Luckily now the bug is pretty much only prevalent in Frozen City. It used to be all over Forest Colony and Alpine Peaks.

Still this bug has persisted since Closed beta and that's a travesty.

[Grendel408]

So this is weird... I haven't had this issue in almost a year since I upgraded my PC's CPU from an i3 2500... but my buddy has a higher performance PC and has this issue with Frozen City every time. My system is an i7 3770K, 8gb Gskill, ASUS mobo, SSD primary hd, and a Radeon HD 6850. I run my graphics settings in MWO on the highest without vsync... no issue. I've heard players being able to do the workarounds the Devs have offered just to later pop back up later. You may also want to try creating a profile for MWO in your GPU's added software... I know Nvidia and ATI cards allow this, and they can conflict sometimes with ingame settings... if so, allow the profile to let the program (MWO) choose if certain things need to be enabled, and then setup your in-game settings as needed.

Edited by Grendel408, 13 February 2014 - 10:29 AM.

[Robertak]

only deleting of shaders folder heps.. for a while.. then error occurs again.. and again.. its really annoying

[ImperialKnight]

posting a fix for this issue is pointless. the problem just keep coming back any way. after a while, you just go 'meh' and live with it

[JohnAzussa]

knightsljx, on 16 February 2014 - 06:39 AM, said:

posting a fix for this issue is pointless. the problem just keep coming back any way. after a while, you just go 'meh' and live with it

its a feature, not a bug!

[Warge]

Robertak, on 11 February 2014 - 12:07 PM, said:

hope they'll do something fast..

Fast? Not in PGI's case.

[John Mayfield]