1454 réponses à ce sujet

[Autoclave]

As some have pointed out, this specific issue is quite ridiculous.  The game runs FINE on single core CPUs, it is just the movie files that are fudging things up.  Implementing movie files is the least of a company's worries.  Yet Bioware (as much as I love them), have screwed the pooch on this one.

EXACTLY!  Makes me wonder if they declared the double core minimum requirements (which now they try to use as an excuse) only for some movie playing

ME2 runs better on my single CPU than ME1.  

[Gullerback]

I worked out a bit of a Work around for the Final part of the IFF mission if you're getting a blackscreen or Freeze

You WILL have to play this part while stuttering, But its not that bad, theirs no combat.


Put the ME2 disc into you're drive and goto GameData/Bioware/movies, Copy the entire contents back into you're Mass effect 2 Dir under Mass effect 2/bioware/movies.  Overwrite anything.

Now Rename Load_F01.bik or replace it with the Nointro fix one,  Do the same for BWlogo.bik and ME_EAsig_720p_v2_raw.bik

Now remove the -nomoviestartup from you're shortcut and start the game, The mission will now load right, You'll just have to sweat it through some stutter for a while & a load screen will happen which will fix it.


After that just put -nomoviestartup back on you're shortcut and you're golden for the rest of the game

[Hawkeye8890]

misterarmand wrote...

I "temporarily" fixed my issue with the -nomoviestartup, so thanks again to the one who first applied that.

Is anyone else getting very quiet voices during the "personal response" scenes (i.e. the scenes where you get to choose your answer).
All the voices are so quiet and my sound settings have the dialog volume up to max.

Curious if anyone else is having this issue, and if it's related at all to the -nomoviestartup fix--any solutions??

mine seems fine bro =/ everyones speech is great you know with the -nomoviestartup thing but i am using steam maybe thats why its different?

[T1l]

jasonnov118 wrote...

As some have pointed out, this specific issue is quite ridiculous.  The game runs FINE on single core CPUs, it is just the movie files that are fudging things up.  Implementing movie files is the least of a company's worries.  Yet Bioware (as much as I love them), have screwed the pooch on this one.

This is a really interesting problem (what would stop pre-rendered movies running on a single core machine?), but I think what's more interesting is that Bioware have said they're willing to fix it. Not just "We're looking in to it", but "We'll have it fixed in the second patch. Sorry about that.". Speaks volumes for their integrity; yes, they may have ballsed it up initially - but they're fixing it. You can't ask for more.

Thanks Bioware. Miffed I can't play the game at the moment, but glad you're working on fixing the issue.

[Vzzz]

It would be a good thing , to know time order of bik-movies .

 I mean , we could watch them at the same time as we play the game , but now i  don’t  know which of them I should start  ( except , of course , movies of  loading :
load_f01 … load_f15 ) .

Sorry  for my English

Modifié par Vzzz, 30 janvier 2010 - 08:51 .

[lolmanftw]

KuroTori wrote...

lolmanftw wrote...

KuroTori wrote...

Reason why I like for actual users to fix things is because Bioware is a corporation and the process for patching is a ****hole of epic proportions. They're going to release a patch when it goes through sixty six cycles of bull**** corporate structure and not a minute sooner.

Can you explain the problem in detail? From what I understand, you load into the level, and then you move around, and then after a certain amount of seconds freeze? What kind of a freeze is it? Black screen? No CPU response anymore? Background sound still playing without skipping?

Cinematics instantly puts the game into a lag/loop/freeze/whatever you may want to call it. Exactly every 5 seconds the game hangs for 4-5 seconds. If there is a load after a cinematic then there is no problem. Hence why we quick save and quick load after a cinematic. This wouldnt be a problem if there werent engine/ingame cinematics, but there are and mostly after a normal cinematic and they are long. So we gotta wait 10 to more.. minutes until we can quick save and quick load.

Wait a minute.

The problem you described seems like an active process hook. The exact same happens if you run a process monitor with the Mass Effect 1 exe, and then start disabling things in order to get SecuROM to stop hooking (which I did, as the ****ing thing rootkitted itself into my system - it became near impossible to remove it later, and uninstalling the first Mass Effect does not remove SecuROM from the system entierly - though that's a separate topic and these days one can google programs that will seek and remove those rootkit files).

But ME2 doesn't have SecuROM... and you're obviously not blocking active memory hooks.

Something is being blocked, which in turn creates that "freezing" spike. I wonder what.

Actually IIRC it happens exactly like that. The spiking in the first Mass Effect did not occur (you alt-tab, you enable the process to be blocked, you alt tab back into the game, and it's all good until you transition from the area you are in, to another area. Then it starts spiking exactly like that.

Maybe it's trying to read something from the previous area which it can't after you've loaded the new one.

You would need to get someone who knows what they're doing to process check the ME2 exe to see which process exactly is spiking (getting a denied return).

This will definitely be fixed in the patch if they're aware of it, so I guess that's some solace for you.

This is quite similar to Unreal3/Mirrors Edge.. Well not quite but.. the cinematics would freeze the game completly. So we found a command in the configuration which isnt anymore since it was incorporated in the game engine..

[BladeRyo]

Ok, lets recap the situation about movies.

Movies are BIK files, that give us a lot of headache, animations are in-game movies rendered by the game engine, so you can see different members of your group, weapons and armors. So we avoid the confusions.

On some PCs movies wont load, like starting a new game or import char, so we can replace the movie files with empty/dummy files, game then loads and we can play. Also called the green movie/loading screen.  This only affects loading screens
Fix and instructions are on GameCopyWorld.

Stuttering "after" movies is AFAIK a single core issue (still no confirmation any dual core owner has this problem, and i mostly see AMD CPUs having troubles). The movie play fine ingame, the movie plays fine in BINK player, so the movies are not the problem. Problem is after the movie ends, the game stutters, like 1-2 sec gameplay, and then 5-6-7 sec of game freeze, and so on....making it unplayable, if you are a persistent idiot like me, you will make it in the stuttering and save your game and then reload. Stutter goes away....until the next movie anyway.

I tried everything on this movie stutter issue, full-screen/windowed, sound on/off, disabling sound in windows completely. I replaced the ME2 files in binary folder with older files from ME1 thinking older versions would help, they didnt. Tried replacing/renaming the movies from ME2 with movies from ME1, still stutters, used dummy/empty BNK files, got the stutter...to conclude, there is nothing wrong with the movies, the game somehow craps itself after playing a BNK file.

This are solutions for the movie/loading issues. Other stuff like newest drivers for VGA, MoBo, sound card go without saying. They often help.

We got a response from BioWare that they are aware of this "stutter" issue, and that is scheduled to be addressed in 2nd patch.
First patch is already under works then I guess, it would be nice if BioWare gave us some kind of current change log for patch No.1.
ETA on ether patch is currently unknown.

Modifié par BladeRyo, 30 janvier 2010 - 10:28 .

[DobryNETvor]

SOLVED!!

For all Multicore Processors USERS: I have the big prob with run ME2 cause i gotta i5-750 /4cores/. I SOLVED problem with run this game.

1. I will download an CPU-Z program, and start it to check my processor work with 1 or 4 cores.. there was prob, that it works in 1 core...



2. I will download the lattest version of BIOS and install it...

3. After restart of PC, Win 7 32bit was install drivers and after second restart was in Task Manager 4 cores..



4. I run the GAME AND IT WAS RUN WITHOUT ANY FREEZING....



Tip: Try to upgrade BIOS as me.. Just write, if it works on yours PC likes on mine...

[Dimtree]

Are there any other games that specify a dual-core minimum?

It's possible, even probable maybe, that this is a sign of things to come.

Perhaps all us single core users will just have to stump up for a new CPU and motherboard.

[DobryNETvor]

Dirt 2

[lolmanftw]

Dimtree wrote...

Are there any other games that specify a dual-core minimum?
It's possible, even probable maybe, that this is a sign of things to come.
Perhaps all us single core users will just have to stump up for a new CPU and motherboard.

unlikely.Im running ME2 maxed out and have 30+ fps with one core. Sure my vga card does all the work but single cores are still ok.

Modifié par lolmanftw, 30 janvier 2010 - 10:52 .

[Tricky_Rich]

Well I'm just incredibly glad that Bioware are looking into this. I've got an AMD single core and I took a calculated risk getting this game, as Dragon Age ran fine maxed out.



Bioware are well within their rights to say, "I'm sorry but the minimum specs are for dual cores only, we can''t help you." (Even though we all know that the GAMEPLAY part of the game runs fine on a single core.)

[Dimtree]

@lolmanftw

Yes, my single core handles games well, which makes the loading freeze more frustrating.

[v0rt3x22]

It's funny how people are waiting for a patch - when several solutions have been posted already - and noone is trying them out.

[schwerttau]

Got my copy of the game today (retail version).. and well... can't start a new game.

Didn't read all the pages, but some of them but I'm not sure if I have the problems everybody else have or had.

Tried to "create new game", selected a gender (no matter what), then the cursor disappears, the computers are still there but everything dynamic (menus, scrollers and stuff) is gone. Nothing happens anymore.

Is this the problem others have/had too, or is this not the same?

Win7 64-bit (still the rc, will have to install the full some day)
E6750 (dual-core)
4096MB ram
nvidia gtx-275 (latest drivers)
changed language in installer from german to english.

tried the rename load_f01.bik-trick but this did not solve the problem.

[-Dakeyras-]

vOrt3x22-> maybe because people wants to play to their game with the game complete. Actually we have no idea if the video we could miss using those temporary fix are important or not.

I mean, isthere a lot of video like the one at the beginning showinfg the Normandy getting hit by something?

Modifié par -Dakeyras-, 30 janvier 2010 - 11:52 .

[thedace]

You can view the videos with Bink player and risk potential spoiler. I check about 10, none were important.

[v0rt3x22]

-Dakeyras- wrote...

vOrt3x22-> maybe because people wants to play to their game with the game complete. Actually we have no idea if the video we could miss using those temporary fix are important or not.

I mean, isthere a lot of video like the one at the beginning showinfg the Normandy getting hit by something?

Well I posted a solution that doesn't involve removing videos - and noone bothered to get back to me - on whether it works.

I'm posting repro steps here:

*Note: I only tested this on WIndows Vista Home Premium* (Dual Core only)

1. Deinstall your current NVIDIA PhsyX drivers from the Add / Remove Programs section.

2. Insert your Mass Effect CD 1 - go to: \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\software\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ and install "PhysX_9.09.0814_SystemSoftware.exe"

3. Start Mass Effect 2

4. Alt-Tab back to Windows - hit CTRL-ALT-DELETE and bring up the Task Manager.

5. Select the "Processes" Tab and scroll down to find "MassEffect2.exe"

6. Right-Click on the process and select "Set Affinity"

7. If you have a dual core - you should see "CPU 0" and "CPU 1" selected.

8. De-select "CPU 1" and hit ok. Close the Task Manager.

9. Continue (or restart, to be sure) the game.

- I have had no trouble so far.

It's still crashing though - so Bioware should still look into this.

Modifié par v0rt3x22, 30 janvier 2010 - 12:07 .

[KuroTori]

schwerttau wrote...

Got my copy of the game today (retail version).. and well... can't start a new game.

Didn't read all the pages, but some of them but I'm not sure if I have the problems everybody else have or had.

Tried to "create new game", selected a gender (no matter what), then the cursor disappears, the computers are still there but everything dynamic (menus, scrollers and stuff) is gone. Nothing happens anymore.

Is this the problem others have/had too, or is this not the same?

Win7 64-bit (still the rc, will have to install the full some day)
E6750 (dual-core)
4096MB ram
nvidia gtx-275 (latest drivers)
changed language in installer from german to english.

tried the rename load_f01.bik-trick but this did not solve the problem.

First post, page 47.

This is what happens a second before you freeze on the first loading screen.

Doesn't hurt to try it anyway.

[SouperTrooper]

v0rt3x22 wrote...

It's funny how people are waiting for a patch - when several solutions have been posted already - and noone is trying them out.

why would you say that?  A ton of people have tried/tweaked the solutions posted.  While we can play the game it's still not ideal since we're missing out on bits of it.  Some people like myself are playing through.  Others chose to wait so tehy can get a complete experience.  Also this thread is 50 pages now.  For someone who just purchased the game it's not easy to make sense of all the solutions posted here anymore.  It'll take time and searching before they get there.  

[Zerberrus527]

hmmm someone else cant pass the IFF Scene? try the way that KuroTori posted but still black screen

[-Dakeyras-]

v0rt3x22 -> For me it is simply because I have a single core, and your method seemes to be for multiples one.

[Onedeadlyhit]

I downloaded the blank loading screens, It stopped me freezing at the start of the game. In game action runs extremely smoothly on 1400x900 resoloution, some cinematics lag and some dont, I only just downloaded the game today of steam

[dremhunk]

yea my problem is single core problem, I had a doul core but I killed it by playing Crysis.

the Cpu now is a 2.93 Intel and it ran Crysis for fine why can't run this game fine? well the movies that is

after reading this thread and looking at my system, and talking to a friend. I was thinking it was dual core all this time loil

I'm up grading my pc when the Intel release project offset any way.

It's sucks that I can't play mass effect movies right that is the best part about mass effect.

I am not going to return my CE I am just going hang on to it. I have tons of games I have not played or finshed yet any way. lol

In cluding dragon age, it's just that mass effect is one of farvite games of all time. I had it preordered months in adanvce only to find out I can't play all of it, only part.

I sstill love my bio-ware games

Modifié par dremhunk, 30 janvier 2010 - 01:01 .

[schwerttau]

KuroTori thanks for your answer.

I uninstalled the game and reinstalled, just in case.

Then, I did what v0rt3x22 recommed. Not even that much, I just changed cpu assignment to "one core". It worked.

Next, I installed all the DLC I was able to get:

- Inferno Armor
- Blood Dragon Armor
- Zaeed - The Price of Revenge
- Normandy Crash Site

Problem there again. So it seems to be related to the DLC.

Next, I removed all DLC the hard way (deleting folders) because I did not found another way to uninstall the game.

Started the game again, removed on core again: works.

Will try to nail down which DLC causes the problem or if ALL of them are responsible for this.

[edit]
tested so far: 

- official dlc (not armor): doesn't work/start


[another edit]
deselecting one core is not necessary (in my case). it is the dlc which causes my problem. sad though

Modifié par schwerttau, 30 janvier 2010 - 01:54 .