the only driver I've gotten Mass Effect and Mass Effect 2 to work with reliably are version 126.96.36.1991 (and it runs quite well, too). Any newer driver - up to and including 188.8.131.529 - causes the games to crash once the "esc" key is hit from in-game to access the in-game menu (e.g. for a save).
There are several postings on the issue on the web, e.g. http://social.bioware.com/forum/1/topic/131/index/7535912/1.
This is a pity, as the newer drivers cause other games such as Dragon Age to display much better than the older .2361 drivers. But I don't want to keep changing the driver just to play the game.
I'm running the game on a mid 2011 Macbook Air with an i7 processor. However, the problem is not limited to Macs - above Bioware forum link describes the issue on a Toshiba.
Does anyone have a similar experience? Has anyone been able to solve it? Does Intel know of the issue and is, perhaps, working on a solution?
Kind regards, and thank you for any replies.
Just want to say I'm having the exact same issue as well. It really sucks because the new drivers make the game run a lot better but not being able to access the menu makes it unplayable. Luckily I had an old restore point that should let me play the game again, but I'm praying a new update will fix this problem.
Hello my loved company intel I have a problem games Mass Efect 1games periodically takes off after 10-15 minutes after the game abozh when you go in the game menu it freezes and we throw out in Windows
I know that this is a problem in the drivers graphics adapter game on the system unit with processor Core I3 2105 HD3000 hope to address in the next version of driver
Update: I've had a few interesting crashes from Mass Effect 1 running under the HD 2622 drivers: a message is shown that I should clear up hard drive space as the system has run out of virtual memory. I'll try to write down the exact error code(s) next time this happens. Meanwhile, I've reduced the anisotropic filter level on the game from 8 to 4, this might possibly help (fingers xed).
This is the crash error message:
Ran out of virtual memory. To prevent this condition, you must free up more space on your primary hard disk. MallocLarge(size = 27709440, type = 4096, protect = 4, VM = 1986908160/2147352576)
... when this message is shown, I usually have to use alt-ctrl-delete to invoke the task manager where I can then quit Mass Effect.
It'd be great if you could have a look and possibly fix. Thanks!
... this might be something to do with Windows 7 64 bit. The MallocSize error in Mass Effect (and other applications) turns up quite often on Google. After some digging this might be an explanation:
I'm going to try this on the console:
> bcdedit /set IncreaseUserVA 3072
Funny thing is, this did not happen with the old drivers I used (2361 if I recall correctly).
... and another update: Applying the "Large Address Aware" flag to the Mass Effect executable as per
using the tool
actually helped. I have had no more MallocSize errors in Mass Effect 1. Now I'm a very happy camper with the 2622 drivers :-)
... oh, and for all those who find Mass Effect 2 a bit too dark -
The Bioware forum has an entry on one of the shaders used by Mass Effect 2:
The problem with both of those is it leaves the colours washed out and unrealistic.
I did find another fix on some other boards and thought I would post it here for people too. I dont take credit for this fix, just want to pass it on.
In your Mass Effect2\\Engine\\Shaders folder there is a file called UberPostProcessBlendPixelShader.usf
find this line:-
and change it to
float3 x = max(0,InLinearColour);
You can also change the 0.004 to something closer to zero, like 0.001, to make the effect less rather than removing it, or to something larger to make the black crush even worse.