Aller au contenu

Photo

Game Crash Report - Reflective Armor Prototypes


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

#1
LuPoM

LuPoM
  • Members
  • 637 messages
I was just moving the plates of the puzzle when, moving the right one where the beam originates, the beam hit the wall on the right and the game crashed.
I don't know if it happened to anyone else, anyways those are my specs:

Intel Core2Quad Q6600
4gb Cell Shock DDR2 Ram
NVidia GeForce GTX 260 running the latest WHQL drivers
Windows 7 x64 with the latest updates

Game running at maxed out standard (nothing forced through the nvidia drivers) settings in 1920x1200.

Edit: It happened only that time.. I tried to cause the game crash again and it didn't happen.. this time ti went smoothly without a crash..

Modifié par LuPoM, 03 février 2010 - 10:27 .


#2
Miriel Amarinth

Miriel Amarinth
  • Members
  • 390 messages
Wow, interesting. The same thing happened to me last night. Was on the station where the VI went wild and in the research wing (i think) I moved the far right panel 3 times, the beam hit the wall and WHAM, I crashed to desktop. When I reloaded, I set the other panels in the correct position first and then turned the right panel only once - I didn't crash that time.



I thought the CTD was probably a fluke, but if you crashed in the exact same spot, doing the exact same thing it's probably a persistent bug and not related to hardware/drivers. It's also the first and only crash I've experienced in ME2 so far. Still just in case these are my specs:



Core2Duo E8400 3.0ghz

4gb ram OCZ reaper (ddr2 - 800mhz)

Nvidia geforce 9800gtx - 186.16 drivers (provide better stability in another game)

Windows 7 Ultimate 64-bit + latest updates

#3
MoriarTC

MoriarTC
  • Members
  • 15 messages
Same ... Beam hit wall Crashed the game. Maybe it's a CTD Beam ^_^

#4
Miriel Amarinth

Miriel Amarinth
  • Members
  • 390 messages

MoriarTC wrote...

Same ... Beam hit wall Crashed the game. Maybe it's a CTD Beam ^_^


I'm willing to bet that right in the spot where the beam hits the wall there's a plaque that says "aim here for free BEER" luring unwary players to their doom. ^_^

#5
sb.seed

sb.seed
  • Members
  • 43 messages
btw it doesnt matter wear the beam hits it will crash once the beam is past that first reflective plate...there have been multiple threads on this problem. hopefully when they get around to releasing a patch it will fix the issues....but since EA is involved dont hold your breath.

#6
rswh0310

rswh0310
  • Members
  • 5 messages
so.. if we bypass this puzzle, would if affect anything in the area? cuz im having the issue too

#7
rswh0310

rswh0310
  • Members
  • 5 messages
I dont know if this helps, yet to try but this is what Mass Effect Wiki has to say.

After reaching the research lab, repositioning the reflective armor so that the beam fires into the wall may result in a crash. Currently, there is no patch for the bug. You can, however, prevent the crash from occuring by moving all the mirrors aside from the one that would alter the path of the beam. When all mirrors aside from that one are positioned correctly, look away from the beam and the reactor, and the game should not crash to desktop.


http://masseffect.wi...esearch_Station

Modifié par rswh0310, 05 février 2010 - 10:46 .


#8
Titan8883

Titan8883
  • Members
  • 16 messages
Ugh, same issue here... it's not always at exactly the same time, sometimes I can get a little ways through the puzzle before it crashes...

#9
Roelandtstorme

Roelandtstorme
  • Members
  • 30 messages
Confirmed that looking away from the beam avoids the crash, but if you look at it at anytime...crash. How odd!

#10
Talmook

Talmook
  • Members
  • 4 messages
Wth, why is this bug even in the game, shoddy

#11
noctoi

noctoi
  • Members
  • 57 messages
Im having the same prob, looking away doesn't help as this is my first time playing so I have no idea what Im meant to be doing with the beam in the first place... *cries* This is the first prob I've had with the game so Im kind of amazed that it hasn't been fixed if its a known bug. With so few real probs to fix this should be a piece of cake to patch...