Aucune réponse à ce sujet

[Avalon Aurora]

I'm not exactly asking for help to solve issues, as with regular saves and simply opening up the game again this is a relatively minor issue, but I think it is still important for Bioware to know to track down the source of these issues for the purposes of stabalizing later patches.

ME3 suddenly fails and windows fails to fix the problem, forcing the game to close, when certain things happen on my computer. It does this when my anti-virus software AVG, detects and/or is downloading updates, when the computer detects and/or begins downloading updates for windows as part of standard Windows 7 operation, when my anti-virus begins a routine scan of the hard-drive. I suspect it is doing this when any other software takes up a portion of the RAM and/or processing power, especially things that trigger without direct user imput. Many of these checks and activations of software in the background are things I have no idea how to stop, or don't want to stop because it would be a hassle to stop and start it before and after every time I play the game, or wouldn't want to stop for security reasons, especially while connected to the internet, but they have never caused other applications to fail before, so the problem is clearly on ME3's end. Origin is unbothered by these processes, and remains open.

Just for reference purposes, my computer is a Mac mini running Windows 7 in Bootcamp, with 2 gigs of RAM. I barely fit the game's minimum requirements, but it runs reasonably well, in fact I think in ME3 I get a better FPS than ME2 does.

I've also noticed my controls, with some exceptions, especially movement and ability to fire (aiming still usually works) lock up, until I utilize a class-power. This usually triggers after taking damage while facing somewhat downwards, but I doubt it has anything to do with that. My best guess is it has something to do with the barrier between health and sheilds/barriers, when my primary defense goes down and I'm starting to take health damage. It does not happen all the time, and is easily remedied by using a power, but is rather strange, and I thought worth reporting, since it appears to be some kind of weird bug.