It started giving me the infamous mscorlib.dll error (998) ando there's no way to change it.
I tried everything possible with the settings, changing resolution, shader, textures, everything.
It keeps crashing and informing me of a failure in loading mscorlib.dll (Win32 error: 998).
Now there's more thant a reason why I need the latest ATI driver AND the Control Center, reasons it would be long and unneccessary to explain here.
What I can't swallow is the fact that I played L2 for a year without any hassle, and I learned the lesson that says "always download the latest video driver for your video card", and now I am stranded here with all my friends playing and me completely unable to enter the game.
And the only workaround is installing an older driver?
Sorry, I can't. :(
I need (and I am sure lots more are in the same situation I am) a fix for this, I think it would be fair t have a game running with the latest driver available for our videocard. Especially when we are suggested to upgrade those drivers as soon as they are available.
Please someone read this and give us some answers, some workaround, some fix that doesn't revolve only around: "downgrade to an older driver".
What if I say "upgrade your client to an higher level of stability and compatibility?".
I don't want to sound bitter but I am so sad, 3 days into C4 and I am unable to login. And I am sure you all know I am paying money for this :(
Please, do something :(
--
Falconeer
P.S: I could try to work for a brief short time with the Ati Control Panel instead of the Ati Control Center, but looks to me that the latest 6.2 driver doesn't have an option for Control Panel, only Control Center, as if you install the first part of the multipart download you get Driver Only but without Control Panel at all.
I know this isn't the fix you wanted to hear, but if you remove your current 6.2 Catalyst Control Center driver and install just a plan drive you will be able to play for the time being.
Look for the low speed download section and install the plan driver only.
I have been fighting this issue since the 5.10 CCC drivers.
I did find a work around fix for the 5.13 drivers that worked for me at least it was using only .NET 2.0. I reported the issue to support and they looked into it.
They said they couldn't reproduce the error with the current 6.1 drivers with .NET 1.1, at that time i was still using the 5.13 drivers. So i upgraded to 6.1 with no troubles. Then the next day i got the same error again, i checked ATI to see if they did any updates.
And wouldn't you know they came out with 6.2 drivers the same day, so i upgraded once again and the errors stopped.
So i don't know what to tell you other then to play with it. Maybe removing the NET 1.1 and installing 2.0 will fix your problem.