My system specs:
Vista Home Premium SP2
CPU: AMD Athlon 64 X2 Dual Core 4600+ 2.40 GHz
RAM: 4.00 GB
Video card: nVidia GeForce 9800 GT 1GB
GPU Driver: 296.10
REalTek Audio: DirectX 10 compatible
Direct X10.0 March 2009 or later
Game version:
MassEffect2.exe v1.02
Hi all, I hope someone here can help me. Has anyone encountered a loading issue when coming up to the final battle sequence in the Collector Base?
The details of my problem are as follows:
I come to the end of the seeker swarms section in collector base at the end of the game and go through the doors to finish the level. A loading screen appears. Once the next section of the game opens, my graphics go haywire - I have multiple images of people of the screen, so when they move its like they smear a series of residual images behind them, like a trail. Most of the screen is black, sound is ok. Although the graphics are bad, because the sound is ok, I can work out that I get to the portion of the cutscene where the other door opens and one of my team takes a hit as they come through (Jacob in this case, as second team leader, but he shrugs it off). Then, screen goes momentarily black, then I get this wierd noise like a husk or abomination coming towards me and suddenly I'm dead.
I know from looking at walkthrough vids that this isn't meant to be what happens (!) as this is where the Hold the Line bit kicks in.
Has anyone else come across this issue before? What is really doing my head in here is that I've played ME2 before a while ago and fully completed it, so I'm not entirely sure what is going on. I don't know of any obvious major configuration changes to my machine which would cause this sort of problem.
The only thing that has been similar before is that, when I have run ME2 recently, I've turned my affinity off and
on again on one of my cores to cure the problem of long loading times. This occassionally led to the same graphics issue where I was getting multiple images smearing across the screen. It has never affected loading missions or levels though. However, I've tried running this end sequence from a cold boot with both cores on and it still messes up.
Help!
Thanks for your time
Yazbod
Strange bug stopping loading of Hold the Line segment and final battle in Collector base
Débuté par
yazbod
, avril 28 2012 11:44
#1
Posté 28 avril 2012 - 11:44
#2
Posté 28 avril 2012 - 01:06
Have you recently made the mistake (from an ME-2 point of view) of upgrading your graphics driver from an older one that was working fine for this game? Ever since the GTX 200 series followed their forerunner generation, the Geforce 8000s have been left behind. (All but one 9800 is a renamed 8800 of some sort, forced to "replace" the 8800s when the GTX200 was held up an extra six months past the planned release date.)
Beyond the carelessness about their older GPUs, nVIDIA has also been particularly haphazard at supporting any and all UT3 based games, for any of their graphics processor families. You will almost certainly find this game runs MUCH, MUCH better if you will remove all traces of your current driver with Driver Cleaner, and install one that actually works, from a couple of years ago. I can't tell you which is which, with certainty, sorry, I quit using any Geforces two years ago.
Beyond the carelessness about their older GPUs, nVIDIA has also been particularly haphazard at supporting any and all UT3 based games, for any of their graphics processor families. You will almost certainly find this game runs MUCH, MUCH better if you will remove all traces of your current driver with Driver Cleaner, and install one that actually works, from a couple of years ago. I can't tell you which is which, with certainty, sorry, I quit using any Geforces two years ago.
#3
Posté 28 avril 2012 - 01:29
Hi Gorath, when I first came across this issue yesterday, I was running a much older version of my graphics driver and only upgraded to the newer version as an attempted fix, so unfortunately I don't see the driver update being the issue 
I appreciate your comments anyhow.and might try your suggestion if I don't get anything from anyone else.
I appreciate your comments anyhow.and might try your suggestion if I don't get anything from anyone else.
#4
Posté 28 avril 2012 - 01:56
What else had changed between the last time the game ran well and now? You do know this is a Dx9 game, not Dx10, right? All of the Direct3D APIs are fully compatible with one another, but sometimes there's some backwash from a new version's upgrade, forcing a reinstall of Dx9.
FYI, it's been so long since this was a popular game that hardly anyone who has played it all the way to the end at least once is on hand here any more, and the off-season is already beginning, so the very few coming around now will soon be even fewer. Don't hold any high hopes for anything other than replacing:
1. Drivers, very old ones are in order
2. Entire graphics subsystem, card and drivers. The 9800 is now four years old, which is a very long time for such hardware.
FYI, it's been so long since this was a popular game that hardly anyone who has played it all the way to the end at least once is on hand here any more, and the off-season is already beginning, so the very few coming around now will soon be even fewer. Don't hold any high hopes for anything other than replacing:
1. Drivers, very old ones are in order
2. Entire graphics subsystem, card and drivers. The 9800 is now four years old, which is a very long time for such hardware.
#5
Posté 28 avril 2012 - 02:02
The only issue I've had with my pc since last time I ran ME2 and now is that I had a problem with a corrupted windows update, which led to a trip to the pc doctor as my machine wouldn't boot. I am open to a full re-install, just want to be certain I wouldn't lose my saves as the whole reason for re-playing now is that I can have all 3 ME games played as one experience.
I appreciate my 9800 is v old hardware, but this is what I had last time. I'll look into older drivers though.
Thanks for your time.
I appreciate my 9800 is v old hardware, but this is what I had last time. I'll look into older drivers though.
Thanks for your time.
#6
Posté 28 avril 2012 - 02:47
You're welcome. Incidentally, there have been many incidents involving Direct3D when the ME-3 game has been installed, and came with a conflicting Dx9 version (conflicted with ME-2).
#7
Posté 28 avril 2012 - 03:09
Could you link to a screenshot of the artifacting? Also what is the temp of your graphics card and CPU when the error occurs? HWMonitor may give you a rough idea.
Modifié par no_subject, 28 avril 2012 - 03:10 .
#8
Posté 28 avril 2012 - 03:28
I'm sorry but I have no idea of how to get a screenshot when all the artifacting is going on. I'll see what I can do in respect of temp of graphics card and CPU.
#9
Posté 28 avril 2012 - 03:39
I like Smartfan much better for monitoring temps. You can use it to put whichever part you worry about most (usually the GPU) right on the screen inside your game with it, plus an FPS counter.
#10
Posté 28 avril 2012 - 03:42
Hi. have just run the game again, got stuck in same place but had HWMonitor running in background. Stats are: Core 0 - 43 to 45 degC, Core1 - 47 to 50 degC, GPU 51 to 69 deg C. In my limited knowledge, none of them are running off the scale.
#11
Posté 28 avril 2012 - 06:49
Yes your temps look fine, to get a screenshot run the game in windowed mode, press print screen and paste into mspaint. Make sure the GPU driver is not interfering with the game by going into the Nvidia control panel and make sure all graphics settings are set to 'application controlled' within the profile section. As Mr. Alpha has suggested, you may wish to google for an Nvidia driver that is good for your card, as Windows Update may have installed a bad one. Finally, there is always the possibility that your graphics card may be damaged.
#12
Posté 28 avril 2012 - 09:01
Hi,
I've managed to printscreen as per your instructions no_subject. I've printed an in-game shot of the seeker swarm section, a shot of the cinematic of the end of the seeker swarm section and then the section which should show the cinematic with jacob getting hit as he comes through the doors, but which is awful. These are all below:
Seeker swarm in-game shot:
Seeker swarm cinematic
Hold the line cinematic graphic fail:
BTW I don't see how it could be a graphics card fail given that throughout the rest of the game, everything has been fine and whenever I play other games, like I've just been playing AC Revelations, there are no issues. Not trying to be ungrateful - just confused
Thanks
Yazbod
I've managed to printscreen as per your instructions no_subject. I've printed an in-game shot of the seeker swarm section, a shot of the cinematic of the end of the seeker swarm section and then the section which should show the cinematic with jacob getting hit as he comes through the doors, but which is awful. These are all below:
Seeker swarm in-game shot:
Seeker swarm cinematic
Hold the line cinematic graphic fail:
BTW I don't see how it could be a graphics card fail given that throughout the rest of the game, everything has been fine and whenever I play other games, like I've just been playing AC Revelations, there are no issues. Not trying to be ungrateful - just confused
Thanks
Yazbod
#13
Posté 29 avril 2012 - 08:09
I wanted to eliminate hardware failure as the problem, and those screenshots don't look typical of a failing graphics card. Coupled with the fact that your temps are fine and you're playing other games ok I can assume your hardware is ok. I recommend a reinstall of ME2 In the unlikely event that a game file is corrupt or missing. (Back up your save game but remove game settings when it asks you, incase you have any bad config files). Aside from earlier advice offered with regard to excluding the games.exe from any Nvidia profiling and looking for another driver I'm afraid I have no further suggestions.
#14
Posté 29 avril 2012 - 08:21
Hi no_subject, thanks for your feedback. I appreciate the time you've taken to help me out. I'll go for a re-install and see what happens.
Cheers
Yazbod.
Cheers
Yazbod.
#15
Posté 29 avril 2012 - 11:07
Hi folks, just to let you know the re-install seems to have fixed it. Thanks anyhow.





Retour en haut







