469 réponses à ce sujet

[milan20]

Many thanks but i have solved this issues.

[PiZdrot]

Tab16 wrote...
.....The non-loading bink videos do not stutter, they play fine, but after the video finishes and the game goes back to normal , non-video gameplay, the game stutters. This can worked-around by saving and loading a game.

I confirm it.... RADVideo installed last version.

[getterg]

MockAffiliatus wrote...

fortunately, i managed to get onto the citadel using the above suggested work-around and a fresh re-install. Unfortunately, I can't seem to move on past some loading screens. so, i can use transports between the ward levels and the presidium, but if i try to go to the factory level, the 800 block (loyalty missions), or even try to reload a file, the game crashes. I don't have any issues with stuttering or glitching bink movies (when they play), but this other stuff is making it hard to progress.

Got the same problem, im guessing it has something to do with single core too.

[Torop]

bjdbwea wrote...
I can't confirm that. All bink videos actually play without problems (only the initial Normandy destruction video has only music, but no voice). The main problem wasn't mentioned in your list: AFTER any bink movie (except the "green" ones) has played, the following real 3D scenes stutter badly - basically one second of smooth movement, then five seconds freeze, and so on. Saving, then reloading completely fixes it. Since the loading movies are completely irrelevant, and there's already the quick-fix available, this problem I described is the main issue.

Yes... I have some problem. I hope Bioware is solve this issue.

[XX-D4rKAng3L-XX]

DarthLuck wrote...

XX-D4rKAng3L-XX wrote...

I might sound stupid but I dont know if I have a Single-Core or a Multi-Core.

How do i check it?

One of my friends told me that in Task Manager > Performance, in Cpu Usage History, if there is 1 box, it's single
core, if there are 2 boxes, it's dual core.

What do you mean 1 box?
I see 4 boxes two small ones on the left and 2 big ones on the right.

[XX-D4rKAng3L-XX]

DarthLuck wrote...

XX-D4rKAng3L-XX wrote...

I might sound stupid but I dont know if I have a Single-Core or a Multi-Core.

How do i check it?

One of my friends told me that in Task Manager > Performance, in Cpu Usage History, if there is 1 box, it's single
core, if there are 2 boxes, it's dual core.

What do you mean 1 box?
I see four boxes two small ones on the left and two big ones on the right.

Modifié par XX-D4rKAng3L-XX, 02 février 2010 - 07:10 .

[XX-D4rKAng3L-XX]

http://www.edbott.co...r_mem_small.jpg



Thats how my performance tab look in my task manager.



I called the company and they told me its a Dual-Core,

I wasn't sure so i wanted to ask you guys.



BTW : These are my processors

Intel® Corse™2 Dou CPU E6550 @ 2.33GHz

Intel® Corse™2 Dou CPU E6550 @ 2.33GHz



Thanks.

[widmowy]

Hello everyone,



What I can tell you is that the best solution is to buy dual core CPU. I did it today and all problems just gone :-))) And I bought Athlon 64 dual core 2,5 GHz.



Have a lot of fun with ME2!

[Rockman900]

Makers breath! So, what we have right now is that the game can only be played on a pc with duo or more processors? This is unheard of. I know I know, single cpu's are a thing of the past now-a-days, but still many people use them.



So, be honest with me: do you guys think Bioware can magically patch the game to be compatible with a single cpu instead of a duo or more? Or should everyone just buy a duo or be satisfied with the work arounds you guys came up with?

And I thought my nice Nvidia GeForce 275 GTX was the answer to everything...

[Misterbill]

I have been playing using the -nomovies workaround on my single core AMD 64--game running very smoothly. I found I could get to the Citadel by using normal startup and the "wait for the movie on the Press Any Key" screen--I just loaded my latest save and was able to get there. There was a bit of stutter on the Galactic Map screen, but once I landed everything worked fine. However, I was not able to load a save from Citadel running normally (got loading screen freeze), nor could I load a save there using -nomovie (black screen with what sounded like normal audio).



I don't know if there is any combat on Citadel, but this obviously doesn't work well for that unless you (unlike yours truly) never die in combat and need to reload a save. However, I was able to talk to Anderson and the Council, complete non-combat quests, and do some shopping. Hope this helps while we all pray to the PC gods for a patch to bail us out....

[DashRunner92]

Rockman900 wrote...

Makers breath! So, what we have right now is that the game can only be played on a pc with duo or more processors? This is unheard of. I know I know, single cpu's are a thing of the past now-a-days, but still many people use them.

So, be honest with me: do you guys think Bioware can magically patch the game to be compatible with a single cpu instead of a duo or more? Or should everyone just buy a duo or be satisfied with the work arounds you guys came up with?
And I thought my nice Nvidia GeForce 275 GTX was the answer to everything...

To be honest, single cpu's are not a thing of the past. There are single core cpu's that are more powerful than du core cpu's. I think Bioware can patch it, but i'm definitely going to be looking to upgrade to duo core. 

[MoonChildTheUnholy]

Ok i can confirm that i also do not have the issue with the IFF mission and all is normal on my side except for the loading screens, the game runs faster than ME1 on my humnle rig so go figure



What i did was just use the unofficial "fix" which replaces all your bink loading files (no plot videos lost! just loading screen logo animated replaced by green image).

[Rockman900]

DashRunner92 wrote...

To be honest, single cpu's are not a thing of the past. There are single core cpu's that are more powerful than du core cpu's. I think Bioware can patch it, but i'm definitely going to be looking to upgrade to duo core. 

I defiantly agree, there are single cpu's more powerful than duo or quatro cores. However, ME2 is (I think) one of the first games to not support single cpu's. Now that is strange don't you think? 
Me too spend the last two hours searching the internet for a upgrade to either quatro or duo core...

[Ragingsaint]

The IFF part im having trouble with is as soon as you get it, and you fight the reaper core, my game doesnt respond. is there any solution?

[Slvrsur]

Thanks all, for the comments but no one so far has told me how I can get the fix and how to use it, LOL!!



I have a single core AMD 64 and get stuck right at the loading screen start.

[Pikie 1 dog]

Hey metalcalf i was just wondering if that quick save and quick load thing works in the beginning Normandy blowing up tutorial mission, i am going to try it anyways right now.

[Spiro12]

Pikie 1 dog wrote...

Hey metalcalf i was just wondering if that quick save and quick load thing works in the beginning Normandy blowing up tutorial mission, i am going to try it anyways right now.

It doesn't.  The game will not save until after you are revived in the lab.

[Pikie 1 dog]

Darn it, I was hoping it worked. Thanks for responding anyways Spiro. Now I was just wondering is there any way to get past the second loading screen, the one after creating your character, without a patch or anything?

[The Cu Sith]

After finally getting the game installed (I had the data error problem when trying to install) everything works fine except ONE loading screen. I know this thread is for people with single core processors but maybe someone can help me. I've gone and done a lot of exploring and missions, but whenever I try to get the Omega station the game will play the docking video and get stuck in a loop for the loading screen. I don't know what the issue is as it's the same loading screen used to get to the Citadel and I had no problems with that. Thanks for any help.



Oh and by the way, some system specs:

Intel Q9400

4GB Ram

ATI 4890

[schizo-v]

Game runs beautifully with the exception of having to play with -nomoviestartup on the shortcut. So much fun! I love you BioWare!



... okay, on topic now. I was looking at Coalesced.ini in BioGame\\Config\\PC\\Cooked. I can't edit it, because it looks like compiled config files or something and the game crashes if I touch it. However, there is a section in there called [Biogame.Movies] and there are a few interesting settings in there.



[BIOGame.Movies]

TimeBetweenSyncChecks=0.8

DoSync=true



I feel like if I could disable the sync, it might make the game run more smoothly after the video has played. It's just a hunch, but the reason I have this hunch is interesting, albeit fishy. Time between sync checks is 0.8, I assume seconds - that feels like how long the game plays after returning to realtime 3D before freezing for five seconds. Then another 0.8, freeze, etc.



Mind that I've done the loading screen replacement, but other movies play fine, it's just the lag the game suffers after one has played that I am curious about. Is there any way to mess with the settings in Coalesced.ini? I tried pasting adjusted copies of the above lines (such as DoSync=false) into My Documents\\BioWare\\Mass Effect 2\\BIOGame\\Config's .ini files, to no avail... guess I could try injecting it into other ini files, trying to override the settings in the uneditable, cooked Coalesced.ini. I guess I could edit it with a hex editor but I don't want to get sued for tampering or whatever (even though that doesn't seem likely).

[aries32487]

@spiro12

In order to complete IFF, rename your green load folder to something other then movie, and rename your full movie folder to Movie. Load the game. DO NOT PRESS ANY KEY. Wait for the trailer to play once. By allowing the trailer to play before pressing a key you can get past the loading screen bug but with lag. Press any key. Suffer through lag as you reload. Access the galaxy map. You will see some cinimatics and cut sceens. You will have to navigate through the ship in a noncombat playthrough, then suffer some more cut scenes before you ever get the chance to save. It will take a long time, but once you're through it, you're through it.

WHAT IS THE GREEN LOAD FOLDER? Are there 2 folders i have to rename? there is only one folder i could find that i think you are talking about and that is E:\\Games\\Mass Effect 2\\BioGame\\Movies

[MajFauxPas]

schizo-v wrote...

Game runs beautifully with the exception of having to play with -nomoviestartup on the shortcut. So much fun! I love you BioWare!

... okay, on topic now. I was looking at Coalesced.ini in BioGame\\\\Config\\\\PC\\\\Cooked. I can't edit it, because it looks like compiled config files or something and the game crashes if I touch it. However, there is a section in there called [Biogame.Movies] and there are a few interesting settings in there.

[BIOGame.Movies]
TimeBetweenSyncChecks=0.8
DoSync=true

I feel like if I could disable the sync, it might make the game run more smoothly after the video has played. It's just a hunch, but the reason I have this hunch is interesting, albeit fishy. Time between sync checks is 0.8, I assume seconds - that feels like how long the game plays after returning to realtime 3D before freezing for five seconds. Then another 0.8, freeze, etc.

Mind that I've done the loading screen replacement, but other movies play fine, it's just the lag the game suffers after one has played that I am curious about. Is there any way to mess with the settings in Coalesced.ini? I tried pasting adjusted copies of the above lines (such as DoSync=false) into My Documents\\\\BioWare\\\\Mass Effect 2\\\\BIOGame\\\\Config's .ini files, to no avail... guess I could try injecting it into other ini files, trying to override the settings in the uneditable, cooked Coalesced.ini. I guess I could edit it with a hex editor but I don't want to get sued for tampering or whatever (even though that doesn't seem likely).

Yeah, my game locks up about .8 seconds after I select New Game...
Maybe your'e on to something.
Anyhow, I have to reinstall my XP just to play the game. Which is like cutting off your ++++ just to have +++!

My system:

Win XP SP3
AMD Phenom X3 710

After reading the lengthy thread on load screen lockup, I discovered my OS does not utilize all three cores, but it knows they are there. Three processors are listed under processors in device manager, but only one graph in task manager, one core in system info. Been like that for 6 mo or so...
The problem is that I used my old OS hard drive in a new machine....
If this sounds like you, odds are you need to reinstall XP. I'm guessing this is because XP doesn't install the multi core kernel unless you have a multi core CPU, meaning single core kernel is standard.

XP does not have a magic boot.ini fix like Vista does... gotta reinstall. I'll be using a new HD so I can fall back to existing and perfectly working XP SP3 which can't run the game.

Every time I think about this it becomes more obvious that the game could have been optimized for single cores, but that someone instead went out of their way to make it not work for single cores at all. ME2's technology is the same as ME1: same Unreal Engine 3, same Bink movies, so what gives? Why the need to eliminate a hefty percentage of the consumer base? Too much money? Too many fans? lol I go too far, I apologize, but someone has to say it. Everyone is wondering: why.

[ironbluefox]

Should have posted this here since its more appropriate my issue is #1 as outlined.

When i start the game just after clicking the male story line it goes to loading video then freezes and i have to force close but I found the using the -nostartupmovie trick allows me to play the game normally.

so I got an idea I went to my call of duty modern warfare 2 directory and went into my binaries on my mass effect to removed the binkw32.dll and substituted the CODMW2 binkw32.dll which is version 1.8.23.0 a significantly older version IT WORKED the game in the normal areas like main menu and in game cut scenes ran like crap thou but it got over the hurdle and allowed the game to fully load like it should normally.

the .dll from left for dead 2 which its version is 1.9.17.0 didnt work had the same effect as the one it comes with trying borderlands .dll now game is running crappy but not as bad as 1.8.23.0 it DID fully load like supposed to game runs better at version 1.9.14.0 and still plays lots of lagging and stoppage in cut scenes and normal menu.

also Note the version that comes with Mass effect 2 is version 1.9.5.0. Installing mass effect 1 now going to continue testing.

Mass Effect 1's binkw32.dll is version 1.8.21.0 it acts just like Mass Effects 2 version 1.9.5.0 so no new progress just the same crap as it orginally was. But I can run mass effect 1 just fine going to try dragon age: orgins .dll its the same version but might be something different.3kb difference but no luck running out of Ideas.

Even with sucessful runs with older .dll's attempting to try and run with them in windowed mode still cause the freeze and crash but in full screen had no problems. So in turn I am at a loss on what to do. Also now the switching out the .dll's doesnt work  now so I have no clue as what I figured out really.

Modifié par ironbluefox, 03 février 2010 - 05:45 .

[MoonChildTheUnholy]

Ok i spoke too soon, the game was going great but now after doing Legion quest i wait for IFF to be installed so i go to the galaxy map, an ingame chat starts about the IFF and i have to go with the shuttle, but then the game goes to a black screen and it stays there, i can hear the sounds in the background but it seems that part just doesn´t want to load. :/

[bjdbwea]

If you want to edit the Coalesced.ini, you need to make sure that it always has the same amount of characters. So if you change a "true" to "false", you'll need to remove a character somewhere, maybe a 0 where it doesn't matter - make sure to find a position where it doesn't create new problems. Likewise, if you remove a character, you have to add one somewhere else. Yeah, since several important options already can't be configured in-game, not even providing a proper ini file is another bad thing. This is not like BioWare used to be. And there people said the ME 1 PC port was bad... Anyway, I've already tried a lot of changes in that strange Coalesced.ini, but nothing seems to have any effect whatsoever on that awful stutter bug. If you find anything, please, post it here.

Modifié par bjdbwea, 03 février 2010 - 04:59 .