6 réponses à ce sujet

[Vandermear]

I have no idea if this is the right place but the tech support self help just dose not seem like the right place.  

I have reached the point near the end of the game where Black Garrius should be summoning the Nightwalker, only my game glitched and did not.   So in a bit of anger, and since my last autosave is over an hour of work away I switched over to one of my other characters in a different campaign and played that for a while.  today when I was going to attempt to re-cover the ground I lost from the glitch, my autosave had be overwritten from the other character.    
So is there someone out there who could give me a hand, either by bumping me past the fight to the cut scene, or by rewinding my game to just before the fight with black Garrius and the Nightwalker?

 

[Vaalyah]

First question, as usual. Is your game patched? (just for understanding the glitch problem)

[Vandermear]

I got it through Steam, and the claim that they keep everything up to date with all of the most recent patches for me. So when ever a patch is posted, Steam should be automatically updating my games for me.

[kevL]

Try this

Weird problem with Garius at the keep battle

--
edit, ohh, and I hope everyone takes blazin130791's advice:

Glad to see this got sorted. I'd just like to say this is a good reason you should save much more often than every 5 levels. It's not hard and has saved my ass from lots of game breakers in lots of games.

My personal philosophy is to make a unique slot-save every few hours when things 'feel right'. Preferably just before a transition advances the game. Then, on top of that, i use F12-quicksave every 15 minutes, when there's no hostile monsters or combat around

Modifié par kevL, 08 février 2011 - 10:00 .

[Vandermear]

Ok that problem is solved but now I ahve a whole bunch of highlighted zones that when I mouse over them they are speech triggers.

[Vandermear]

And never mind y last post, that problem sorted itself out when I exited the game and then played again later.

[kevL]

k,

btw, those triggers showed up because you were still in DebugMode ..



( big yellow squares on the ground? DebugMode 0 )