1454 réponses à ce sujet

[OrioTecc]

Same here.



AMD Athlon FX-55

GeForce 9800GTX+

2gb ram

[darkblade1079]

Ugh I purchased the collecter's edition at midnight on the dot and this game refuses to work. I spent hours working my way to getting to level 60 .Right when I try to run the game nothing works. i get a black screen and an "Unreal 3 engine button" down below and then the game crashes. I have already used my log on codes for the game including cerberous card but have not been able to even give the game a try. Can I please know what to do to change this?

[Gebut]

I got the same problem, freeze at loading screen.

By using the single core fix, I can make it to when you wake up and everything plays smooth until the next video file plays and I have to save/load to be able to play again.

AMD Athlon 64 3800+

2gig RAM

Geforce 8800GTX.



I might have an Athlon 64 X2 4200+ incoming, will try installing that if I get it.

[darkblade1079]

now here is the funny thing my system shows me with 2 cores not one and even then it refuses to work... All I get is a crash screen and a shutdown window

[Raezaiel]

darkblade1079 wrote...

now here is the funny thing my system shows me with 2 cores not one and even then it refuses to work... All I get is a crash screen and a shutdown window

this isn't a post about crashes, only mass gate golden freezes needing a green square fix !

[darkblade1079]

To be honest as for everyone else I am in the same boat. I can't even bring up the game without it breaking right off the bat. I wonder really if they rushed this out the door before testing for any major bugs

[husq]

Michael Gamble wrote...

Hi all,

I can't offer any solution right now, as there are way too many variables out there. I will have an engineer take a look at this tomorrow, though. It's obviously not the 'single-core' issue that we thought it was. In the meantime, keep an eye out from any new announcements from Chris Priestly with regards to this, and i will update him as i get information.

Ill still be around, but I need to get back to PM work to make sure our PC patch schedule is on-track (yes, we are planning a PC patch in the near future... but unfortunately any new issues since launch will have to be in a POTENTIAL second patch)

PS- don't try to modify the coalesced.ini file, it reads garbled because its actually encrypted on the game build side, so any alteration will undoubtedly cause your game to crash.

For anyone that doesn't want to trawl, this is Bioware's response on page 17.

Spec: Core 2 duo E8500, nvidia GTX 260 sp3 all drivers updated.

I tried waiting for the intro cutscene on the press any key screen to play(which played perfectly) and got past the loading screen after selecting gender.

I then managed to wait through the one frame every five seconds intro movie with the audio working fine - just triggered very slowly so the conversation took forever - and managed to navigate with the lag to the cockpit and get to the character traits part and it froze on the next loading screen. Unfortunately this was before the first save so I'm back to the befinning.

I'll try the movies fix next.

[Qwinn1234]

Okay, here's the thing. I'm on a single processor and, after applying the unofficial blank .blk file patch, the game runs -flawlessly-. Seriously. Better than ME1 does! *Much* better. And this is at 1360x768, with medium graphic settings, which on ME1 would cause lag but in ME2 doesn't seem to cause any framerate drop at all. I have no reason to think I couldn't turn the graphic settings up to high, really.



All that is on a measly 2.86ghz single core processor, with an old NVidia 7600GS 256mb video card.



So, first, let me say to Bioware, whoever worked on making the engine more efficient did an *excellent* job. Seriously. Aside from the issue in this thread, ME2 makes *very* efficient use of resources, and the play quality and frame rates are much improved over any previous game I've played. Kudos.



But... sorry, there's obviously a big but after a 34 page thread...



Because of that, there's no excuse I can see for making dual cores a requirement. Anything that *matters* in this game runs on a single core flawlessly, better than your previous titles, and to make dual cores required just because of some silly issue with .blk's is preposterous. Even the stuttering problem *really* does not need two or more processors to resolve, because we're all aware that we can get that problem after a movie plays, and saving and reloading makes it completely go away. That establishes, without any doubt, that it's not a matter of needing dual cores, it's something that can easily be resolved with a little programming effort.



So, great kudos for great work on making the engine more robust. Now please don't completely *waste* all that incredible effort and accomplishment by insisting on a totally bogus system requirement that really is entirely resolvable. Thanks for listening.



Qwinn

[Qwinn1234]

Oh, and by the way, I pre-ordered my copy of the CE very early on. At that time, there weren't any system requirements publicly specced yet. So I had absolutely no way to know this was going to be an issue when I was offered this game. If nothing else, I think that should motivate toward resolving the problem in such a way that single core users aren't (unnecessarily) barred from playing this game. Thank you.



Qwinn

[Zayin]

I've had the same problem but that's nothing new. I've been following this thread since release day afternoon but quietly lurked in the hopes that a fix would quickly be found. Then yesterday morning my three and half year old power supply died and I had to fix that. Fun fun. I figured I might as well post.



I haven't tried the unofficial fix for the loading screens yet; I'm wary of doing things like that in games. But if that is the only option for Single core users, I'll have to do it.



Here's my rig specs:



Processor: AMD Athlon™ 64 Processor 3200+, MMX, 3DNow, ~2.5GHz

Memory: 1.5 GB RAM

DirectX Version: DirectX 9.0c (4.09.0000.0904)

Video Card: NVIDIA GeForce 9800 GT

Sound Card: Realtek AC97 Audio

[SojournerN7]

I am technically in the same boat, but I just really wanted to play ME2.

Trying the unofficial fix really does work except, but I took a few diffrent steps. I backed up all the loading .bik movies to a backup folder in the Mass Effect 2 root directory, and moved the "blank" loading .bik files from the fix in. The unofficial fix also has two .bik that would replace the Bioware and EA logo that I didn't want to replace, so I left them out.

The game did stutter, quite painstakingly until I got to a point to where I could save, shutdown and restart my computer. So far I haven't had any problems and it's run smoothly since on my Single Core Athlon 3800. I just haven't had enough time to play ME2 and see if the problem is resolved for now.

I don't wholly endorse the fix, but wanted to say I've actually had some success to those who might want to give it a try. Just back up your .bik files that it replaces first.

Modifié par Sojourner83, 28 janvier 2010 - 12:30 .

[lolmanftw]

Zoulezz wrote...

to lolmanftw

90% of users that have this problem have single core, and many 2 core users have stated that their config file says they have only 1 core.

<- single core. Bioware clearly stated it has nothign to do with the cpu, hence why ppl with dual-cores have the same problems. Its a bik video problem and/or windows issue. Nothing more. Like I said dont missinform.

[Qwinn1234]

lolmanftw:

I think they were wrong, as were we earlier in the thread. Many of us were shouting, screaming that it wasn't a single core issue, and we were quite upset when a Bioware person said it -was-. Well, turns out it looks like they were right initially, and we were wrong (as was the poor Bioware guy who listened to our screaming). If people with duo cores were having the problem, then they got their system to recognize the second processor, and then the problem went away, then it IS a single core problem.

That said, let me repeat, it's an entirely *avoidable* single core problem. The movie playing bits that are requiring a second processor are totally trivial and superficial, clearly not worth the problems it is causing, *and* clearly resolvable via programming since saving and reloading can completely fix the issue. See my post about 5 posts above this one for the details.

BTW, I hereby apologize for any upset I may have expressed over the Bioware poster who said it was a single processor issue.

Qwinn

Modifié par Qwinn1234, 28 janvier 2010 - 12:37 .

[Phonzo]

hmm maybe onto something qwinn.



It'd be great if those with multicore processors fired up the configuration tool and went to the system tab.



It should list your cpu model, type (includes family and stepping) and finally the # of cpus and the # of cores.



Please tell us how many cores the config utility is seeing.



In terms of single core users this makes sense as the game is streaming and loading information while each intro movies plays for the next gameplay bit. This also explains those who have applied the patch but occasionally experience lag primarily in the galaxy map. That is because the game is again loading data while you are flying around the galaxy map. Normally one core would do the grunt work of loading the data while the other was dedicated to your flying around.

[lolmanftw]

Qwinn1234 wrote...

lolmanftw:

I think they were wrong, as were we earlier in the thread. Many of us were shouting, screaming that it wasn't a single core issue, and we were quite upset when a Bioware person said it -was-. Well, turns out it looks like they were right initially, and we were wrong (as was the poor Bioware guy who listened to our screaming). If people with duo cores were having the problem, then they got their system to recognize the second processor, and then the problem went away, then it IS a single core problem.

That said, let me repeat, it's an entirely *avoidable* single core problem. The movie playing bits that are requiring a second processor are totally trivial and superficial, clearly not worth the problems it is causing, *and* clearly resolvable via programming since saving and reloading can completely fix the issue. See my post about 5 posts above this one for the details.

BTW, I hereby apologize for any upset I may have expressed over the Bioware poster who said it was a single processor issue.

Qwinn

hmm I see but I'll still stick to my version of the "windows beeing the problem or something else but not the single cores". Why? Because there are single core users with win7 that dont have that "freezing after cinematics" problem. Moreover if there was something wrong with the single core then the game shouldnt've been able to play at all.

:>

Modifié par lolmanftw, 28 janvier 2010 - 01:07 .

[NatChaos]

nice to see we have a better idea of what is wrong now..



either way, i've basically given up on playing ME2 any time soon. just stopped by to read up on what i've missed. back to dragon age

[Demonite Dreams]

Qwinn is right, imo, as far as running the game on a single core. From what little of the game I can play, it runs flawlessly with absolutely zero lag even on my single core. Mind you, I can't say the rest of th game will be that way but thats because I can't play the flipping game. But from what I can see, there's no reason to require dual cores except maybe to expidite loading for those WITH dual cores... ME1 loads slower and lags more for me than ME2 does. Did ME1 require dual core?

[Maevriel]

Just reposting for Phonzo as my earlier response is now buried. I was stuck at loading screen like everyone else here with no suggested fixes working. Discovered that one of my cores on my dual core was in fact disabled. Enabled it and now the game is playing flawlessly with the dual core processor. IntelCore 2 CPU 6700 @ 2.66GHz

[Torop]

I have this problem too (Intel Celeron D CPU 3,33 GHz).
Has passed more one day, but problem still no solved.
How many time still we wait?
Somebody have ways to solve this problem?

Modifié par Torop, 28 janvier 2010 - 01:45 .

[Admiral K]

Just chiming in here in regards to an above poster's comments on the dual core requirement. A good many of us played ME1 on single core systems, and it ran well. I, for one, am also able to run DA:O almost flawlessly at a 1366x768 resolution with my vid card set to medium settings. And even though I bought my copy of ME2 on launch day, lots of folks ordered theirs weeks ahead of time before so much as a word was said about system requirements.



So, even though Bioware reps may point out that ME2 isn't optimized to run well on single core systems, when January 26th rolled around, what more, really, should they have expected? Since we were all such big fans of the original, of course we had plans to run out and buy the sequel. Which is why this entire dual core thing is nothing more than a bunch of silliness IMO.

[Myliel]

I agree with what Admiral K said, I enjoyed the first one so much I preordered the second as soon as I could, way before the technical specs were posted, I've been waiting for this game for months now, and come release I cant even try it out... damn.



And yeah, this single core thing is silly, my computer can easily handle the game if it werent for that stupid video issue, please please fix it...

[Reginmund]

Qwinn1234 wrote...

lolmanftw:

I think they were wrong, as were we earlier in the thread. Many of us were shouting, screaming that it wasn't a single core issue, and we were quite upset when a Bioware person said it -was-. Well, turns out it looks like they were right initially, and we were wrong (as was the poor Bioware guy who listened to our screaming). If people with duo cores were having the problem, then they got their system to recognize the second processor, and then the problem went away, then it IS a single core problem.

That said, let me repeat, it's an entirely *avoidable* single core problem. The movie playing bits that are requiring a second processor are totally trivial and superficial, clearly not worth the problems it is causing, *and* clearly resolvable via programming since saving and reloading can completely fix the issue. See my post about 5 posts above this one for the details.

BTW, I hereby apologize for any upset I may have expressed over the Bioware poster who said it was a single processor issue.

Qwinn

Disagreed. I have both my core up, and the game still freezes. Please do not make random judgement if you have no understanding of what is going on.

[Nineven]

hyrrulke112 wrote...

forget it, Bioware wont just released some half-finished patch that give us a green screen instead of the usual loading screen. when an official patch will be available, it will fix thing so they can ALL WORK PROPERLY AS THEY SHOULD HAVE IN THE FIRST PLACE...

... and that is, no matter how much time its gonna take...

That's not a patch from Bioware, and you use it at your own risk.

[Phonzo]

Reginmund wrote...

Qwinn1234 wrote...

lolmanftw:

I think they were wrong, as were we earlier in the thread. Many of us were shouting, screaming that it wasn't a single core issue, and we were quite upset when a Bioware person said it -was-. Well, turns out it looks like they were right initially, and we were wrong (as was the poor Bioware guy who listened to our screaming). If people with duo cores were having the problem, then they got their system to recognize the second processor, and then the problem went away, then it IS a single core problem.

That said, let me repeat, it's an entirely *avoidable* single core problem. The movie playing bits that are requiring a second processor are totally trivial and superficial, clearly not worth the problems it is causing, *and* clearly resolvable via programming since saving and reloading can completely fix the issue. See my post about 5 posts above this one for the details.

BTW, I hereby apologize for any upset I may have expressed over the Bioware poster who said it was a single processor issue.

Qwinn

Disagreed. I have both my core up, and the game still freezes. Please do not make random judgement if you have no understanding of what is going on.

as per my earlier post it may be up in BIOS but for whatever reason the game may not see it. Confirm in the configuration utility and let us know what it says. 

[Omen85]

I can confirm this, I just managed to get my second core to start working.

Now it doesnt freeze on loading and it doesnt go slow on the cinematic afterwards. I didnt change anything other than the cores on the processor