Aller au contenu

Photo

Lair of the Shadow Broker Bug(s)


  • Veuillez vous connecter pour répondre
82 réponses à ce sujet

#76
mcsupersport

mcsupersport
  • Members
  • 2 912 messages
1) Try a reinstall of the dlc.
2) Try a new download with a clean broswer(like a new install of google chrome), after clearing cache and deleting the previous files, then reinstall.
3) Google it using advanced search social.bioware.com for the domain.
4) If that doesn't work, post specs and a better report using the sticky at top of forum as a guide to posting.

#77
Baramon

Baramon
  • Members
  • 375 messages
@Cerispace: Have you updated your game and video drivers? Except for a couple of areas where the cutscenes do this weird "smearing" effect, most of the game-killing/freezing glitches should be gone. What type of video card (and version of drivers) are you using?

#78
Lagerosi

Lagerosi
  • Members
  • 1 messages

jjcoolay wrote...

I had a similar problem with the dlc. I got it to work after I started a save file that
Was earlier in my game and played the sidequest I had not done. After doing zaeeds
quest, I went back to the shadow broker dlc and all was well.


I believe this to be the core of the issue.  unfortunately they did not code in anything to prevent you from taking the dlc quest to early.

#79
Sarah_SR2

Sarah_SR2
  • Members
  • 564 messages
Luckily I haven't had these game breaking bugs on my laptop but I have had problems nonetheless with this DLC. The Vasir boss fight at the azure causes the game to crash out to the windows desktop very frequently. The last time I played it I think it crashed this way 4 or 5 times during this fight and I had to task manager the game to end the process. The laptop is running a Core i7 Q720m, Radeon 4750 and Win 7 Pro 64 bit (vanilla but fully patched).

#80
mcsupersport

mcsupersport
  • Members
  • 2 912 messages
@Sarah
You may try setting core affinity to just 2 cores and see if it makes a crash difference. Rumors going around that microsoft messed up intel multi core threading, or at least that is what someone else on the forums said, DA2 tech forum.

Thankfully, I haven't had but a handful of crashes in the entire time playing, and have so far missed most of the game breaking bugs everyone else has.....I just hope I continue to be as lucky, since I really enjoy playing the game.

#81
Sarah_SR2

Sarah_SR2
  • Members
  • 564 messages
^^ I may well give that a try if it happens on my current playthrough. I've not heard of any issues with gaming performance related to threading on the quad core Intel CPUs but there could be I guess? In fairness to ME2, that Vasir fight is the only part of the game where I've had an issue so I've escaped lightly compared to what I've seen of others on this forum. And like you, I hope I continue to avoid problems as I love playing the game too :o)

#82
GASFaceMC

GASFaceMC
  • Members
  • 1 messages
@Joel Shepard Thanks worked out for me bro :D

#83
ccd_97

ccd_97
  • Members
  • 7 messages

Xlyrith wrote...

I haven't been able to find a topic that suits the needs of this (could be looking in the wrong place) but I seem to have run into a rather large problem in LotSB  during the skycar chase I encounter an entirely black screen minus flashing lights, (that I have no clue what they mean) the "target aquired" box in the bottom right and the subtitles of Liara talking. Not sure what is causing it but it is very frustating and is keeping me from playing that part of the mission and by extention the rest of the DLC. Posted Image Everything is fine (except the normal graphic bugs) up to that point and for that matter I even considered that the helmet I was wearing was blocking the camera but after running through to the error in question with a different helm, I confirmed it was not. To expand the chase loads in I can see a 1/2 second of the background then everything goes black.

I would appreciate any help on the subject thank you.

~Xlyrith

I downloaded this crack MASS.EFFECT.2.V1.02.VITALITY.NODVD and it worked (i kept the blur motion off and also used the patch 1.02)