Terminals, doors, etc become inoperable
#26
Posté 28 janvier 2010 - 07:16
#27
Posté 28 janvier 2010 - 07:29
#28
Posté 28 janvier 2010 - 08:38
#29
Posté 28 janvier 2010 - 09:03
If you read my http://social.biowar...ex/813204]other post[/url], it appears that selectable objects, and in particular the blue rectangle halo over them is NOT an object but just a lighting setting... Why they did that I don't know.
I know that having LensFlare=False in the ini file will create this situation.
So I may conclude that somehow you end up in the same mode, maybe a graphic card behavior, or some settings that leads to the same.
Now, having interactable objects as graphic settings flares is plain incomprehensible...
Hope this leads you guys in the right direction to fix your issue...
Modifié par Kriss_T0ff, 28 janvier 2010 - 09:05 .
#30
Posté 28 janvier 2010 - 11:08
#31
Posté 28 janvier 2010 - 11:10
#32
Posté 28 janvier 2010 - 11:37
Playing in the lowest resolution windowed mode; and then using the [esc] [esc] trick and hammering down on the spacebar (given that your key bindings are the default ones) OR saving and reloading (hit F9) and hammering down on the spacebar OR a combination of both but playing in the lowest res in windowed mode has helped. Temporary but not permanent. Check out the thread (link below) if you'd like join the nagging with the rest of us having this same issue. We really want a patch that'll fix this!
http://social.biowar...779091/3#821736
Modifié par 7th_Phoenix, 28 janvier 2010 - 11:38 .
#33
Posté 28 janvier 2010 - 11:47
#34
Posté 28 janvier 2010 - 11:54
#35
Posté 29 janvier 2010 - 10:39
#36
Posté 30 janvier 2010 - 12:42
#37
Posté 30 janvier 2010 - 01:06
Ghosthunter2012 wrote...
This is most frustrating
Its beyond frustrating its a game breaker, im currently locked in the com room after obtaining grunt be nice to be able to get out and see what happens next!
Oh and yes reloading doesnt help did the whole mission from scratch and erased the first saves i made and i still got it, to my mind may as well take the damn game back and get a refund because its totaly unplayable with this
#38
Posté 30 janvier 2010 - 05:27
eveynameiwantisfekintaken wrote...
Ghosthunter2012 wrote...
This is most frustrating
Its beyond frustrating its a game breaker, im currently locked in the com room after obtaining grunt be nice to be able to get out and see what happens next!
Oh and yes reloading doesnt help did the whole mission from scratch and erased the first saves i made and i still got it, to my mind may as well take the damn game back and get a refund because its totaly unplayable with this
Aye, I'm not even that far into this game (stuck on the first mission, can't even get the gun out of the locker) seriously though Bioware needs to get a patch out on this quickly, or at the very least post to one of these forums saying that they are working the problem.
#39
Posté 01 février 2010 - 09:28
GodofEmperors wrote...
Geekhippie wrote...
After getting Grunt, I am called to the briefing room, but there is no blue square to access Illusive man.
I am stuck and can go no further in the game. This is NOT ACCEPTABLE.
FIX your broken game. I like the game, but I just can't go past that point.
EA live chat said a patch is coming out the 9th of February. Are you kidding me? Why wait until then to patch this
BROKEN GAME!!!
So more or less none of can really play this game until February 9?
I really hope they fix this in the patch.
Also has anyone contacted a moderater on this matter?
found on http://social.biowar...779091/5#898555
#40
Posté 01 février 2010 - 09:29
Modifié par Ghosthunter2012, 01 février 2010 - 09:30 .
#41
Posté 01 février 2010 - 09:37
#42
Posté 01 février 2010 - 09:39
zacrobmer wrote...
Did any of you guys change your key binding's? There seems to be a glitch that if you change your key bindings, the spacebar in particular it causes UI and cursor errors.
I tried Changing mine and it didnt change anything, sadly I have to say, some of us may just have to wait until the patch comes out...
#43
Posté 01 février 2010 - 09:43
#44
Posté 01 février 2010 - 09:44
Modifié par BaronIronBlood, 02 février 2010 - 10:28 .
#45
Posté 01 février 2010 - 11:22
The causes appears to be how the game reacts to having a cursor in the game in things such as the main menu or in the freeze time mode (which I imagine the console versions ME2 was specifically designed for do not have to deal with) and how transitioning back into the game causes some kind of conflict between the cursor location/state and the invisible crosshair that serves as the views center point for interactions. (You should notice sometimes when looking at a interactable object with this problem, the game will flicker constantly between recognising and not recognising the object)
As others have said, looking at a interactable object and then going to the main menu and then returning to the game and quickly pressing the spacebar before the game loses awareness of the object works and appears to force the game back to working as intended.
I have also found that avoiding as much mouse movement as possible when going back into the game from the main menu or freeze time screen greatly reduces the chance of creating the problem as well.
---
How exactly this problem made it through the QA process for the PC platform however is baffling.
Modifié par Tikigod60, 01 février 2010 - 11:27 .
#46
Posté 02 février 2010 - 10:26
#47
Posté 02 février 2010 - 10:31
Andrew5819 wrote...
Return it and buy an Xbox.
Only thing I'd use XBox for would be a doorstop. Probably not even then as a brick works better and doesn't cost as much. As for the issue, at times it occurred too but I fixed it by saving the game and then reloading it.
#48
Posté 05 février 2010 - 01:48
#49
Posté 13 février 2010 - 06:17





Retour en haut






