1454 réponses à ce sujet

[Redshaw88]

To be fair, Bioware clearly stated this is a self-help thread. EA's supposed to be covering the technical problems, but they aren't.

[Medhia Nox]

I'll have to go back and check their responses. I didn't see them say: "Fix it yourselves."



It's really small potatoes at the end of the day - I've got more important things to do, but my money will be put to better use in the future.

[eternalnightmare13]

Redshaw88 wrote...

To be fair, Bioware clearly stated this is a self-help thread. EA's supposed to be covering the technical problems, but they aren't.

Sorry, but I call BS on that.  Go launch the game and what do yo see?  A button called 'Support' which takes you here.  I see nowhere where it says SELF help.  BS!

[iniudan]

Ok tested so many shaders, light or what so ever graphical value inside the game text file that my head hurt, found nothing that actually make even a slight difference. So my guess of it been shader related might be bull, but I am not the one who worked on the file so could have easily missed important value.



But this make me think that the lag trouble might streaming related since it affect a greater number of single core then other processor architecture, through other are still affected. But since I got no idea how to tweak that I cannot test and damn too sleepy now anyway, calling it a night and hopping an official solution happen to be here when I wake up or come back from work tomorrow.

[Colinhenry]

I spent 9 hours helping my family move today thinking about how I'm going to buy ME2 (which they pretty much payed for), go home and play it for a few hours, but instead I get a slap in the face after trying to troubleshoot this for 3 hours and finding out I'll probably need a patch?

[Medhia Nox]

And there are single cores that are working fine.



I made a thread in general - only one person responded - but the threads are moving so fast there I couldn't keep it on the front page.

[Lesclaig]

Medhia Nox wrote...

And there are single cores that are working fine.

I made a thread in general - only one person responded - but the threads are moving so fast there I couldn't keep it on the front page.

so singles can run this game?

[lupontralver]

you want to know what makes this even worse? the fact that i cant go to 95% of the sites i tend to go to daily with out seeing a add for this. and every add i see is like some has stabbed me over and over again. i think im going to go cral in my bed and sleep

[khristianm]

AMD ATHLON 64X2 DUAL CORE 6000+

4 GIG RAM

NVIDIA GFORCE 9600 GT 512MB

VISTA HOME PREM SP2

DIRECT X 10.0

GAME WILL NOT LAUNCH. SAME ERROR MASS EFFECT HAS STOPPED WORKING..

[Medhia Nox]

Lesclaig -



I started a thread in General called: "Anyone running Mass Effect 2 with a single core"



There was a guy with a very low end system who said it was running fine. It's the only proof I've got because nobody else would answer - and the thread moved down off the first page way too fast.

[Dorohnl]

Lesclaig wrote...

Medhia Nox wrote...

And there are single cores that are working fine.

I made a thread in general - only one person responded - but the threads are moving so fast there I couldn't keep it on the front page.

so singles can run this game?

  I have a single core AMD 64 3500+, search for my previous posts in this thread and you can see I got all the problems as well. I just used the unofficial fix ( basically its just blank .bik files substituting the loading screen.biks), what I did was making a copy of all the .bik that the patch will substitute and put them in a back up folder in case I want to swap the original .bik files back if Bioware plans to release a patch on this issue.

  The fix does not fix the laggy in game real time rendered cutscenes at the beginning of the game. However, once I managed to get past the main character's new face and job selection the game cutscenes seem to run fine with no shuttering and any other problem. I'll post more if I encounter any other problems.

[Misterbill]

Gah...maybe there is something to this single-core angle. The readme says ME2 doesn't run well on single-core processors (like mine). I must admit I had no idea this was going to be a requirement--if it is, I doubt a patch could solve my problem. I made the apparently erroneous assumption that if my system ran ME1 like a champ, there would be no problem with ME2. My only option may be to return the game.....very disappointing....Oh, ran Dragon Age just fine too...heh...

[rorican]

There's definitely enough anecdotal information that this needs to be looked into, and I would assume that a 17 page thread means there is investigation happening.

khristianm wrote...

AMD ATHLON 64X2 DUAL CORE 6000+
4 GIG RAM
NVIDIA GFORCE 9600 GT 512MB
VISTA HOME PREM SP2
DIRECT X 10.0
GAME WILL NOT LAUNCH. SAME ERROR MASS EFFECT HAS STOPPED WORKING..

Check the configuration program and see what it reports as your "# CPUs" and "# Cores" for me, if you don't mind.

Misterbill wrote...

Gah...maybe there is something to
this single-core angle. The readme says ME2 doesn't run well on
single-core processors (like mine). I must admit I had no idea this was
going to be a requirement--if it is, I doubt a patch could solve my
problem. I made the apparently erroneous assumption that if my system
ran ME1 like a champ, there would be no problem with ME2. My only
option may be to return the game.....very disappointing....Oh, ran
Dragon Age just fine too...heh...

Well, the Dual Core minimum specs have been all over the place.  I know it seems kind of cold to say so, but it seems pretty obvious to me that there's a huge difference between ME 2's appearance in Trailers and sneak peaks and the visual quality in ME 1's videos.

That being said, this loading screen thing doesn't really seem to be a single-core problem.  You'll have problems, I'm sure.  Even in ME1 on a single core you could see strange behavior because missile attacks were set up to be parralel processed so sometimes you'd see the geth missile attacks sort of "lurch" at you instead of smoothly fly around.  In DA I really noticed it at the end where I was fighting 40 enemies at once and there was a 2 or 3 second delay between my strikes and my damage calculations.

Loading screen crashes, though?  That seems really unlikely.  At the very least there'd be a more graceful abort process during initial program launch rather than a freeze.

Modifié par rorican, 27 janvier 2010 - 06:48 .

[Lesclaig]

There must be something funky for the beggining CGIs. conformation on single cores is nice. I know about the fix ive tried it and its unbearable. id really like to watch the cgi smoothly for the first time (dont wanna ruin my experience).

[Medhia Nox]

The poster wrote (Gotthammer): 

"I'm playing on a P4 3.0GHz...it's pretty 'old'; mobo's old, too. (both are like, what, 5 yrs old?)
Only 'new' things are the added 1GB RAM (for a total of 2), and my 8800GT 512 MB Inno3D GPU.

I have most of the graphics settings turned on w/ AF at 2x.

I haven't had a problem yet and the game is kinda smooth (granted I'm sure I've had some FPS 'dips'/'hits', but that's probably my fault for wanting to up the settings). Heck, I think ME2 plays smoother than ME1...(then again, I tend to blame 'bringing down the sky' for that. that expansion, on 2 installs, seemed to screw up ME1 somehow)"

- So, this guy is running on a P4.

How's "he" doing it?

I imagine that there are others - but the threads are flying in General and nobody saw it.

Modifié par Medhia Nox, 27 janvier 2010 - 06:47 .

[TheEdri]

I never had a speck of trouble with Dragon Age or Mass Effect 1 and I've always though well of Bioware. I'm willing to sit and wait for Bioware to fix the mess their game seems to be for so many of us, this is just day 1. Fingers crossed I'm not still staring at this post in a couple weeks with slim hope.

[Medhia Nox]

Well - I'm going to bed. Keep the fire's burning folks - we need to get this fixed.

[khristianm]

[quote]rorican wrote...

There's definitely enough anecdotal information that this needs to be looked into, and I would assume that a 17 page thread means there is investigation happening.

[quote]khristianm wrote...

AMD ATHLON 64X2 DUAL CORE 6000+
4 GIG RAM
NVIDIA GFORCE 9600 GT 512MB
VISTA HOME PREM SP2
DIRECT X 10.0
GAME WILL NOT LAUNCH. SAME ERROR MASS EFFECT HAS STOPPED WORKING..
[/quote]

Check the configuration program and see what it reports as your "# CPUs" and "# Cores" for me, if you don't mind.

1 CPU AND 2 CORES

[jimmy_hoffa]

Made an attempt to modify the Coalesced.ini file in the ME2\\BioGame\\\\Config\\\\PC\\\\Cooked folder. The game appears to crash with any modification made to the ini file, however. I've used the Mass Effect tweak guide from tweakguides.com to compare the ini variables and there are many similarities. I'm going to experiment with trying to run ME2 without Coalesced.ini in its folder and call it a night.

Edit: No such luck, I know I'm missing something in the Coalesced.ini file since it's an unorganized mess if it's opened in notepad. Current anecdotal evidence indicates that the intro cinematic's stuttering is not related to processing power since there is stuttering on some duo and quad core machines.

Modifié par jimmy_hoffa, 27 janvier 2010 - 07:32 .

[rorican]

jimmy_hoffa wrote...

Made an attempt to modify the Coalesced.ini file in the ME2\\\\BioGame\\\\\\\\Config\\\\\\\\PC\\\\\\\\Cooked folder. The game appears to crash with any modification made to the ini file, however. I've used the Mass Effect tweak guide from tweakguides.com to compare the ini variables and there are many similarities. I'm going to experiment with trying to run ME2 without Coalesced.ini in its folder and call it a night.

Edit: No such luck, I know I'm missing something in the Coalesced.ini file since it's an unorganized mess if it's opened in notepad. Current anecdotal evidence indicates that the intro cinematic's stuttering is not related to processing power since there is stuttering on some duo and quad core machines.

If the file is missing linebreaks then it probably uses Linux style return carriage characters.  WordPad understands and can save those characters.

[Michael Gamble]

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.

Modifié par Michael Gamble, 27 janvier 2010 - 07:49 .

[Michael Gamble]

Lesclaig wrote...

Oh and when the game is fully installed it is just under 12gb. It's not 15gb like the box says, I've heard that the installer has a problem but ive checked most .rar and they there. Unless im missing something.

the box specs a conservative number for our largest SKU. that is why. ~12gb sounds about right for english.

[maxxman1971]

love buying a game i can't play...don't know my specs but it a brand new high end gming pc...runs all other games at lightning speed



i let the intro movie run at the "press any key to continue" screen...let me start the game then when i made my character it locked up at that load screen...way to go bioware..and to think i was looking forward to the old republic...now i dont know

[thitche]

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.

thank you for the update, time for bed for me now weee.

[Qwinn1234]

Thanks for the reply Michael. At least you've clearly read the thread and understand the issue.

I really hope we don't have to wait *two* patches to get this problem sorted. This bug makes the game completely unplayable, if anything's ever been worthy of a hotfix/emergency patch, this is it.

If nothing else, make it a totally separate patch that only people having this problem should attempt to install, that way you don't have to fear messing up the game for people who are working, and for those of us with the problem, you can't make it any *worse*.  Considering all the variables, the end users may really be the only testing bed you have available anyway.

Qwinn

Modifié par Qwinn1234, 27 janvier 2010 - 08:05 .