1454 réponses à ce sujet

[v0rt3x22]

140+ is an understatement

[Michael Gamble]

DarthLuck wrote...

Michael Gamble wrote...

having said that, - again - we are looking at seeing what we can do for a proper fix (and again, NO promises). we have patch 1 coming out in the next few weeks, but the fix to this will have to go into patch TWO (if at all).

don't worry, we are reading this thread and we are aware of the issues. whether or not we can come up with a patchable solution to the issues remains to be seen.

Please understand the situation we're in Bioware, 140+ people can't play the game and are waiting for an update. I understand the problem isn't that important and they're might be no fix at all.

of course we understand the situation you're all in. its why we're looking into it.

[Hammer_Of_God]

Well thanks for keeping us in the loop & I'll be holding thumbs like crazy that you guys can come up with a fix for us soon.



I think I can speak on behalf of every frustrated sod here, we all just cant wait to play this game (hence the endless bickering) & we REALLY do appreciate your effort to help us out BioWare!

[lolmanftw]

Michael Gamble wrote...

DarthLuck wrote...

Michael Gamble wrote...

having said that, - again - we are looking at seeing what we can do for a proper fix (and again, NO promises). we have patch 1 coming out in the next few weeks, but the fix to this will have to go into patch TWO (if at all).

don't worry, we are reading this thread and we are aware of the issues. whether or not we can come up with a patchable solution to the issues remains to be seen.

Please understand the situation we're in Bioware, 140+ people can't play the game and are waiting for an update. I understand the problem isn't that important and they're might be no fix at all.

of course we understand the situation you're all in. its why we're looking into it.

All the general workarounds we, the commnuity, have found is mainly because we have some knowledge of the unreal engine.. I think it would help if you could give us some details, that what could cause the freezings after the cinematics for the single core user, and the other issues adressed here, so that we can find a solution/workaround ourselves, like we always did with other games. Im not saying you're doing a horrible job, Im just stating that there are some junior/senior devs around here that could help our problems get solved faster.

[LuminousLupine]

Michael Gamble wrote...


...

I really hate to sound like a broken record, but the simple fact is that the min-spec was explicitly listed as dual core. there's a lot of double talk going on on this forum. but i just want to see, from what you have all posted, and what we have seen, this IS a single core issue. the folks that have two RECOGNIZED cores and are still having an issue must be crashing from another (notnearly as widespread) issue.

...

Well, you say it's a single core issues, but  if you know what it is, why did it slip past you, and why isn't is fixed in five hours? I guess that's better then ignorance and silance.

( I still think that's BS because of how
hardware handles threading. I'll buy it's a issue with a thread; Howerver, I do not think the standard allows it to be physically possible to be as you say.)

Modifié par LuminousLupine, 31 janvier 2010 - 09:08 .

[fainez]

well i just tried to exchange my broken pc copy at my local gamestore for the xbox version, paying the difference of course. basicly was told to **** off and that im SOL.....

[MockAffiliatus]

I'm using a single core, and I was also having trouble with ctd after picking a gender. I worked around that using the -nomoviestartup affix in the shortcut menu. I've been putting off getting the IFF stuff done because im having issues with landing on the citadel, and i figure the two are related. basically, whenever I dock, the screen goes black. Can't move, can't nothing, but I can hear 'citadel' audio in the background, and the audio isn't looping so i assume it hasn't crashed. I tried two separate shortcuts, etc... but im basically back to square one where i can't get past the main menu. anyone have any ideas?

[madcat10101]

bioware

can i just say that its an incredible experience  on both games.   ok nice etys over.  why can't you get what us gamers want.  i installed mass effect 2 on friday.  not only was i greeted with a half screen with my triple head 2 go ----- doh   ((everyone has or wants triple head support these days   come on get a grip!!!! ))   so that what started it.
then i played the game  and   omg  was amazed - what a job man -  i have dragon age as well and guys    you rock ------ ok nicetys over again    --- why the f  is it crashing after mission 2 - ie the one one on the planet that i blow away the big robot and then talk to the tela and the oher guy - and find out im againts the collectors. i am so disapointed that you have launched a game like this. it even crashes to the degree that i have to reboot. im not even going to bother telling you my rig, but all other games work flawless, and i spent a grand last year on upgrades, so guess for yourself.  guys i love you to bits but come on, we pay your wages and you have delivered a fantastic dissapointment. i await a patch with th2go support for 3840x1024 and no crashes.

iv said my peace

Modifié par madcat10101, 31 janvier 2010 - 09:18 .

[BladeRyo]

@Michael Gamble



So saying that the minimum req is dual core to play a bik movie that works alone anyway, ingame?

Again we say, the game FLYS on single core and older VGA like x1950. I get double framerate than in ME1, that i am playing now for different choices since i finished ME2 and i am currently bored.

Movies ingame go smoothly, game without movies goes unbelievably good 40+ FPS, it only stutters after the movie finishes to play, full movie or dummy file, same thing.

THAT CANT REQUIRE A DUAL CORE, this is some minor/major screwup that should be easy to fix.

[gimmethegepgun]

MockAffiliatus wrote...

I'm using a single core, and I was also having trouble with ctd after picking a gender. I worked around that using the -nomoviestartup affix in the shortcut menu. I've been putting off getting the IFF stuff done because im having issues with landing on the citadel, and i figure the two are related. basically, whenever I dock, the screen goes black. Can't move, can't nothing, but I can hear 'citadel' audio in the background, and the audio isn't looping so i assume it hasn't crashed. I tried two separate shortcuts, etc... but im basically back to square one where i can't get past the main menu. anyone have any ideas?

From what I read, -nomoviestartup prevents you from being able to enter the Citadel, in order to go there you need to have -nomoviestartup off, and likely need the green loading screen one in case you hit a loading screen somewhere there.

[blorbie]

Michael Gamble wrote...

DarthLuck wrote...

Michael Gamble wrote...

having said that, - again - we are looking at seeing what we can do for a proper fix (and again, NO promises). we have patch 1 coming out in the next few weeks, but the fix to this will have to go into patch TWO (if at all).

don't worry, we are reading this thread and we are aware of the issues. whether or not we can come up with a patchable solution to the issues remains to be seen.

Please understand the situation we're in Bioware, 140+ people can't play the game and are waiting for an update. I understand the problem isn't that important and they're might be no fix at all.

of course we understand the situation you're all in. its why we're looking into it.

Hello - It seems like there are a few issues facing the community with single cores and dual+ cores that are being recognized as single cores.  The main one is that they cannot play the game, which has been partially solved with the -nomovie workaround so that those troublesome .bik files are not utilized and the freezing-cinematics are skipped.  However, people have written that this results in a very incomplete playing experience, especially for a BioWare game where the story is such an integral part of the playing experience, and the cinematics are a key driver of that storyline.

Therefore, it would be wonderful if either BioWare or the community could support a fix that goes one step further than the -nomovie workaround.  For example:

1)  People want to see the cinematics when playing the game
2)  People need to use the -nomovie command so that the cinematics are not displayed
3)  It is easy to alt-tab out and see the cinematics online (youtube for example, or BioWare could host them).
4)  However, people do not know which cinematic they should look for and do not want any spoilers that might happen by reading the titles of potential cinematics when trying to find the right one.
5)  The issue posed by #4 would be solved if there was a coding for cinematics (i.e. XGH14), but then people would not know which cinematic to search for online.
6)  Therefore, could we have a quick, simple fix for single core users that somehow tells the player when they have passed over a cinematic with the -nomovie command and gives them the codename for that cinematic (i.e. XGH14).  Then they could easily watch it online (BioWare's site or otherwise). 
7)  In order to address part 6, some people on this forum might have some good ideas, but I would ask for an unobtrusive and entirely optional patch that puts something in your journal or codex like "Most recent cinematic:  XGH14."  Only people who download this optional fix would be able to see this.  Or perhaps, someone from the community, instead of those green screen .bik replacement files, offer replacement .bik files that just display text such as "XGH14."  

If something like this were offered, it would go a long way towards delivering the full playing experience offered by Mass Effect 2.  I believe this would also placate a lot of the community who acknowledge that their expectations are not being met with the current lack of BioWare-supported fixes for this apparently widespread issue.

Thanks for reading this post.  The ideas above, especially in part 7 are just some initial thoughts.  I would love to see other people offer their insights on making a workaround that would let people view the cinematics online.  I also think that this would help BioWare assist their loyal community in the near-term given that a much more technically complex fix is many weeks (months?) away, if it exists at all.

PS:  Sylenced is awesome, and I am not sure how this workaround would address the Citadel issue.

[bjdbwea]

Michael Gamble wrote...

we have patch 1 coming out in the next few weeks, but the fix to this will have to go into patch TWO (if at all).

So it'll be weeks until the first patch, and then even more time until patch two, which - hopefully - will address this issue?

Given that simply saving and reloading completely fixes the lags, there really can't be that much to change in the code. If this issue really was the reason for making multi core mandatory, that would really have been a bad decision. Why discourage potential buyers? Many RPG players don't always have the newest hardware. They could play DA perfectly, and ME 2 too, if not for this bug. Please think about this. If ME 3 will still be developed for the 360 (thereby always limiting the hardware power you can assign), a single core CPU should then still be able to run the game. Don't artificially create problems that might hurt your sales, is in your own interest.

Modifié par bjdbwea, 31 janvier 2010 - 10:21 .

[Shofah]

To Michael Gamble

the best part of your last reply was that you stated its a single core issue. I have a single core AMD FX 64 processor and with the -nomoviestartup temp fix have been playing the game with no issues at all aside from not being able to watch any of the movies. The fact that bioware would create a pc game and make it for dual core processors just to watch the movies its totally absurd, whats even worse is that you can not come up with a fix for what is an easy issue, the movies should not require a dual core to veiw them.


Minimum System Requirements
* Windows XP, Vista, or 7
* 1.8GHz Core 2 Duo Intel or equivalent AMD CPU

just to watch movies? the game plays fine on a sinle core yet you code the movies to only work on a dual core? seems as though some thought should have gone into the coding of this.

[grantbenjensen]

I didn't realize it was duo-core when I bought ME 2. I downloaded the thing to skip the movies but it still lags a lot. Just wondering if there was a way to make it run faster . I already turned the graphics to the lowest settings.

[silfo87]

I used the nomovie command and I am breezing through the game but...anyone find a fix for the citadel? black screen with sound.



Thanks

[NotACom]

First, a huge thanks to Michael Gamble for taking the time to post about this issue. Even if your post was a little unsettling in that you suggest we may not ever see the fix for this issue in a patch. Still, having someone update us is great. I remain hopeful that you guys can actually get this fix into a patch, and in a timely manner.



I just hope Bioware takes this issue seriously, even though it seems to be affecting only single core machines which are under the min. spec for the game anyway. However, I will say that when the game actually works it looks and runs much better than ME1 on my single core PC.



Even if some of us express ourselves in different ways (some are very mad with Bioware it seems) we are all here because of our love for this game, and we all want to be able to experience it as it was meant. Let's keep reminding Bioware of that fact, rather than insult them.



Who knows, maybe our dedication to the game will inspire Bioware to make sure that this issue gets fixed.

[ueadian]

Ok I crash at the character creation loading screen everytime, tried reinstalling, I have a Core 2 Duo so it's not because I have single core, so I don't know why the mods keep insisting its because we don't meet miminum specs. I would return this game if I could, its stupid I paid for it only to have it not get past the character creatoin, total fail on your guys QA testers. Here are my specs :
Core 2 Duo 2.2 ghz
Windows XP Home edition
2 GB Ram
200+ GB free HD space
Nvidia 8800GT
BTW: Config utility correctly identifies my computer as dual core. CPU'S : 1 Cores : 2 also, "no movie" fix does not fix it.

Modifié par ueadian, 01 février 2010 - 12:45 .

[pistolpwn]

Im haveing a similar issue but i only experence it at one loading screen, the one where you get in the blue suns ship to recrute archangle. the sound still runs and the animations for the loading screen run fine but it never makes it past the loading screen, I usually give up after 15+ min.

Here are my specs:

Intel core quad

windows 7 home premium

4GB ram

Nvidia 8800 GT

[schizo-v]

For everyone that has tried the "no loading movie" fix (or even those who haven't), feel free to try this small replacement mod which turns the loading movies into single jpg frames. Same idea as removing the loading movies, but with a bit more flavour. Each is just a frame taken from its corresponding animation.

ME2 was freezing up because it was having trouble playing the HD video while loading the game resources. This eases the load, essentially. Hope it helps!

dl.dropbox.com/u/398143/Files/ME2-SimpleLoadingScreens.zip  (2,047 KB)

Modifié par schizo-v, 01 février 2010 - 01:28 .

[aries32487]

i am able to play the game with the single core fix, but right after i finish legions mission, when i click on the galaxy map, i get this conversation saying i should use the shuttle while the AI runs test on the IFF. then it freezes, never lets me get to the map. does this have to do witht the same problem? Is it a new problem? Or am i the only one?

[schizo-v]

aries32487, Doug4130 seems to have the same problem. We have been discussing it here. We're trying to find a way around it.

[Virgil-ShadeOfReason]

Has anyone considered converting the .bik files to somthing a single core procceser could read and telling the game to read those?

excuse me if i dont make sense, im new

[schizo-v]

Virgil, single core processors and can play them fine... outside the game. The problem is that it's trying to play the video while also extracting and loading game data. I assume on a dual core system, one core plays the looping video while the other does the loading. As for converting the .bik files to something simpler: that is what I did in my small mod above that replaces them with still images.

I tried just compressing the loading video before I changed it to still images. Unfortunately, it still froze on the computer I tested it on. Maybe if the videos are compressed enough, it could play while the loading is going on.

Modifié par schizo-v, 01 février 2010 - 03:07 .

[brekke777]

Just adding to the mix here, its not a single core issue. I have a dual core Intel CPU and 8800GT, and regardless of everything I've tried (new and old drivers, reinstalls, fixes added) my game crashes -every- time at the 2nd loading screen after the Normandy/Lazarus cutscenes.



LOL, Bioware, you guys will never know the buttering up it took for my wife to greenlight me buying this game, but come on its ME2! ITS BIOWARE! They're one of the last great bastions of PC gaming! They'll be there for us! errrr... wait. But yeah, I was almost OK with watching my wife laugh at me for buying a 50 dollar paperweight, till I heard any fix would be the -second- patch. Seriously? Oh well..I'll give ya'll this one. BUT ! Don't.... doooon'ttttt drop the ball on SWTOR. I'll cry forever. PLS DON'T!

[ueadian]

brekke I have that EXACT system spec and the EXACT same problem, if you figure anything out pls let me know as the "fix" users have found does not work. I agree not a single core issue since we both have duo core and a 8800gt