Aucune réponse à ce sujet

[Avalon Aurora]

Lots of people seem to have the 'game not starting' issue, but I'm having an extremly weird variant of it. For me, the game starts successfully about 15% of the time. The place where it fails when it does is after the origin-styled sign that says opening Mass Effect 3, it finishes up the various waiting cursor stuff and then nothing happens no matter how long I wait, and I can't start the game because it acts like it is already started even if I try to open/play it after that. I wind up having to go to the task manager and force quit ME3, and then try to open it again. It only works successfully some of the time, and trying different methods of opening it doesn't seem to matter (such as, from start menu, from origin, from the binaries folder, wheather or not I have origin open before trying to open it, opening it in administrator mode, etc.) for  how often it is successful. How I know it has opened successfully is when after the cursor waiting stuff ends the taskbar shows the ME3 application bar with the ME3 little icon on it, rather than the origin one, appearing. After that it always finishes opening successfully.

Just thought I'd report this issue, as while it isn't entirely game-breaking, the fact that it happens could possibly help Bioware deduce the issues that others are having who can't open the game at all, or only when doing weird tricks, and Bioware knowing about it increases the chances of them fixing it.

I'm running Windows 7 Professional 32 bit version on a MacMini through Bootcamp. 2 gigs of RAM, 2 GHz Intel Core2 Duo processor, and use AVG Anti-Virus Free Edition 2012 as my anti-virus software. My internet is connected by Eithernet to the router, over a very fast and reliable DSL connection through AT&T, with mostly default settings other than some security stuff, and standard Windows Firewall (I think, there might be some other firewall(s)).

The fact that the opening successfully seems totally random regardless of methods used is a particularly confusing factor to me, making no sense based on my knowledge of programming and IT stuff. Repairing the game didn't change anything. The most likely factor I can think of is that the game is extremly sensitive to background activity in the RAM while opening due to some kind of RAM management issue in the launcher, likely related to Origin, rather than ME3 itself, due to calling on some of the wrong RAM sections or something.