1454 réponses à ce sujet

[alavenz]

Sorry, i forgot to say i was responding to the post by Sephiroth4life.

[Hexivor]

morgenstern2206 wrote...

here you guys go!

http://www.megaupload.com/?d=1KHDBLIL

download that and install it solves the problems with freezing at the loading screen! I have a single core processor... this really does work! Im about 45 min into the game now and it hasnt frozen yet! The game plays amazingly as well I would like to add! What the file does is disables the loading screens and just presents a green screen but the game actually does load now! Enjoy!

This fix definately works for getting past the loading screens. Played the game all day yesterday after I installed it.
DL the file -> Unzip it -> open it up until you see a file named movies -> copy the file and paste it in c:\\program files\\mass effect 2\\bio game.

All it does is replace the loading screen graphic with a green screen. You dont miss any movies.

On an unrelated note - because I am pretty sure this isnt caused by this fix - alot of the cutscenes that use, for lack of a better word, the games graphics (non-cinematic movie type movies, IE: the intro w/ Miranda and the Illusive man) often play very slowly - and cause the game to do so afterwards as well.

Playing through the intro like that is a **** - but once you do that it is pretty smooth sailing except for a few similar scenes that also cause the problem (one example is the advanced training videos on your personal computer that you have to watch for an achievement).
On the bright side, after you do the intro you will be able to quick save (default F5) and quick load (default F9) after these types of scenes and it seems to fix the game-play lag at least.

The game is awesome, just wish I had the money to upgrade my entire rig to a duo core so I could experience it in all its glory.

[Sephiroth4Life]

Ah ok well thanks for the info, at least I can cross that one off my list. And hey RedShaw88, yes that just bestows much more credibility

[U-Schultz]

Slight update
- was having the same problems as everyone else however:

I let the initial splash screens  (Bioware and EA) and did not "press a key" and let the opening video play through then when it went back to the "press any key" screen I did.

I was then allowed to import my saved ME1 character and the game started.

Unfortunately it was all so laggy and choppy (the IM/Miranda scene the the Normandy scene) as to be unplayable. Tried to alt tab in and out but the game crashed. Will keep trying.

Modifié par U-Schultz, 27 janvier 2010 - 02:32 .

[Redshaw88]

*knocks on your door* Yes, I'm representing the church of Jenova's Witness.

[Sephiroth4Life]

Ok time for round 2, found another unofficial "fix" but this one doesn't require any downloading.



I would try it myself, but alas I am at work (I'm a programmer too so trying to to EA's job for them!!! )



Here is what I found

'

Found a fix for game launch crashes:



Use windows "run" option, type "msconfig" - then check newly opened window for "load or download or smth like that" "new parametrs" and switch proccessor count from 1 to 2.



After that reboot and reinstall the game. Good luck.

'



Someone please try this it seems like I possible solution.

Now I know that just changing the number of processors in MSconfig isn't the best option. I just want to know if it will work in general.

I do not suggest keeping these settings only trying them to see if we can help out EA / Bioware anymore.

[Dafatmofo3]

i dunno maybe im dumb but i cant install that fix file

[LuminousLupine]

alavenz wrote...

Ok, so i just took the time to read all of the posts and was starting to get annoyed until Michael's post. I do work in the IT field and so i do understand about this sort of issue and have tried quite a few things to fix the problem. I can also pretty well assume that it is not an issue with the cores as many of us(myself included) have gotten the engine to load. I do have a single core box, but can get to the loading screen after the character customization, which means i can load the meat of the game on my box because there is both cinematics and engine loading involved in getting that far. I am pretty sure at this point it is something that will need to be fixed on their end and i dont care what anyone says i will not put a non official patch on my machine as to the reason that even if it doesnt have some STD on it if it wasnt programmed properly it can cause serious and permanent damage to my machine....

I've done a twitch of multi-threading with SDL. If it was a issue with a thread, the program was poorly designed indeed to have stalled and/or not detected the crash of a thread. Bio-Ware has made decision I question as marketing garbage and inane, but they've not do something that green in a long time that I know of. (Not even sure where it's" a single core" issue idea started. It would be no different then if a dual core was assigned three threads. It would just load-balance the thread the same way a single core would.)

[Redshaw88]

I will do that, sir. I will mess with my msconfig without any clue of what I'm doing, delete the game which will redownload (on my ****ty dorm wireless) at 50kbs a second, so that I can see if your idea has an IDENTICAL outcome to where EVERYONE else on this thread is at.

[Phonzo]

the issue isn't just affecting those with single core-cpus, people have posted with dual cores, and quad cores all with the same issue.

[DarthLuck]

I'm not going to buy the game on Jan 29 anymore, this problem will probably affect me, as i have a Single Core CPU. I'm still going to buy it but after a patch/fix that completely solves this problem

[Sephiroth4Life]

I'm sorry Redshaw I missed your posts stating some ideas, instead of whining all day I'm trying to see if we can identify the issues. If you have ****ty wireless then don't do it.

It was merely a suggestion and your sarcasm gets us no where closer to a solution than posting you are a Jehovah's witness. If you have an idea post it otherwise quit while you're behind.

[ImBanginUrGirlFriend]

I have the same problem as everyone else. As an FYI, the lag everyone experiences during some of the "movie/cutscenes" is caused by the CPU spiking. I ran the game in window mode which helps the lag a bit, but I was also running Sysinternal's Process Explorer so I could watch the behavior of my 2 CPUs. Most of the time one of the CPUs is nearly at 100% but the other is only at 50%. During those "movie/cutscenes" both CPU are at 100%.



The game still "halts" if I don't watch the intro when is says "Press any key". It also halts after all the intro movies and you do your character customization. Interestingly, when it "halts" the CPU usage of both CPUs drops to 0%.



My specs:

Motherboard: EVGA nForce 750i SLI

CPU: Intel Core2 Duo CPU E8400 @ 3.00GHz

Memory: 4GB RAM

Video Card: NVIDIA GeForce 8800 GT 512MB VRAM

Sound Card: Sound Blaster X-Fi Xtreme Audio

OS: Microsoft Windows XP Professional Service Pack 3 (5.1.2600)

DirectX 9.0c (Mar2009) or later

[Redshaw88]

First, I'm passive-aggresive super-****.

Second, by all means try, try away; I'll keep cracking, cracking wise away.

Third, it read "Jenovah's Witness." Not Jehovah. A play on words, my friend, mocking the game of your namesake. Wish I could take credit for it.

[Redshaw88]

If you have an idea post it otherwise quit while you're behind.

Also...


http://social.biowar...06/index/782620

[Nineven]

Sephiroth4Life wrote...

Ok time for round 2, found another unofficial "fix" but this one doesn't require any downloading.

I would try it myself, but alas I am at work (I'm a programmer too so trying to to EA's job for them!!! )

Here is what I found
'
Found a fix for game launch crashes:

Use windows "run" option, type "msconfig" - then check newly opened window for "load or download or smth like that" "new parametrs" and switch proccessor count from 1 to 2.

After that reboot and reinstall the game. Good luck.
'

Someone please try this it seems like I possible solution.
Now I know that just changing the number of processors in MSconfig isn't the best option. I just want to know if it will work in general.
I do not suggest keeping these settings only trying them to see if we can help out EA / Bioware anymore.

There is nothing like this in msconfig, perhaps in regedit, but I wouldn't know where to look.

[LuminousLupine]

Honestly, I think they did multi-thread Mass Effect 2, and the they have a bit of "legacy code" and a last second 'fix' messing with each other between the normal start-up and the intro video initialize something funny. I think the loading screen is the main() loop sitting on it's hands while whatever thread would be loading the game crashed. The main loop is asleep waiting for input, and the thread(s) have errored out. So CPU is 0%, and the main loop is just sitting on it hands waiting for single(s) that will never come.



(If that is indeed the case, and may I suggest Bio-Ware create a global variable for each thread, and have some iteration of the thread update that variable with a either the system clock, or if it's SDL the ticks (time the program has been running). Then have the main loop do something like "if(abs(CurrentTime - ThreadUpdate) > 2000) throw TreadTerminated;".)

[Sephiroth4Life]

Ok I looked here at work @ msconfig I probably should of done that before, oh well. Closest I could find was in the BOOT.ini there is a section called advanced options.

In here there is a /NUMPROC which I can only assume is the number of processors field that the fix was referring to.

At this point I don't suggest actually trying this since messing w/ the boot.ini can really mess up your computer, but I will do it when I get home -it's worth a try.

Also for redshaw, ah I misunderstood the original jenovah/jehova statement it's actually quite funny.

And yes messing w/ msconfig can be dangerous so proceed with caution if any of you actually try this.

[dremhunk]

there really shouldn't be a problem considering that ME1 works and pc are more powerful than any console

[LuminousLupine]

dremhunk wrote...

there really shouldn't be a problem considering that ME1 works and pc are more powerful than any console

Should work in a honest world, and do are rarely the same. ME1 had the a like storm of issues Day-1 from SecuROM screwing with Ring-0 (A.K.A. The kernel), and throwing errors there. Although that set of "awesomeness" crashed my system outright with a bluescreen of death.

[Medhia Nox]

I must say - how does the 360 run this game - but suddenly you need a moderately current computer to run the PC version. Is that programming laziness? I don't know the particulars behind it - but it doesn't seem logical.



I find it interesting that Mass Effect is supposed to finish up on this generation console (meaning the 360) - but obviously not the same generation PC.



Now, I know PC's change - but seriously - the strength of the platform is that there can (should) be a wide range of PCs which would run a game at different graphical/speed strengths.



Though - of course - it seems to be nothing to do with dual core vs. single since there have even been quad core users with the problem on here.



I'm just hoping that this game doesn't sit here for days - weeks - before I actually get to play it. I love Bioware games, but this has eaten up some good will.

[NatChaos]

so, i come back from work, 16 hours later...



to see we were locked cause we were being ignored (and yes, when you LOCK an entire thread because you don't actually read what people are discussing, you ARE ignoring it.) then unlocked again, i assume because its much easier to read posts when your head isn't lodged somewhere warm, moist, and smelly.



THEN to see we were ignored yet again, and told i fail for paying money for the sequel to my favorite game. (yes, saying sorry, you didn't read the system requirements is a really warm fuzzy way of saying you fail)



then to see we finally WERE actually paid attention to, only to be told sorry, your problem is tertiary. not that i expected a patch to be immediately delivered (pipe dreamers), or even in a few days, but that "oh, we are working on a patch, but we're still not going to fix your problem. we'll fix it in another 2ND patch that we're not even planning at this moment."



cynicism aside, i still like bioware, mass effect is still my favorite game, and i will still wait however long it takes them to address the issue... that being said, bioware, i brought some lube to help ease it in.

[lolmanftw]

Well heres a sum-up to what I personally think is the actual problem for the freezings after small cinematics.



Since this happens, extremly rare but apparently it did to some other user besides single core ones, I can assume that its not entirely the cpu, but in fact the Windows XP is.



From what I've read single core users with vista/win7 have no problems at all with the game. No freezings, nothing. On the other hand everyone with a single core, dual core, quad core and windows xp have loads of problems.



So I think its safe to say that besides the cinematics beeing terribly developed or the configuration, having windows xp may be a big no no aswell..



Perhaps the devs will have a better way of finding a solution this way.



example: ( I have winxp single core, game starts freezing after small cinematics - if there isnt any load after, if there is then its ok - cause loading solves the freeze - my friend has single core win7 - no freezings AT ALL - )

[Medhia Nox]

To Paraphrase Alistair:

"Don't you just love it how a war brings people together?"

---

Oh, and they said it will "possibly" go into a second patch Nat. Welcome back to the madhouse btw. We're a support group -

----

LOLmanftw -

Well, I do have an option to grab Win7 - and now I think I'll do it. It won't be any time soon, but within the next day or so - our problem will no doubt still be around - so I'll definately keep in touch.

Modifié par Medhia Nox, 27 janvier 2010 - 04:11 .

[DarthLuck]

lolmanftw wrote...
So I think its safe to say that besides the cinematics beeing terribly developed or the configuration, having windows xp may be a big no no aswell..

Perhaps the devs will have a better way of finding a solution this way.

example: ( I have winxp single core, game starts freezing after small cinematics - if there isnt any load after, if there is then its ok - cause loading solves the freeze - my friend has single core win7 - no freezings AT ALL - )

No no not this again (Halo 2 PC)

EDIT: This also means that my single core is (perhaps) not the problem! yay

Modifié par DarthLuck, 27 janvier 2010 - 04:13 .