Gaming witcher 3: tutorial bug?

  • Thread starter Thread starter mrgone
  • Start date Start date
  • Views Views 16,855
  • Replies Replies 8
Joined
Nov 6, 2002
Messages
1,387
Solutions
1
Reaction score
579
Trophies
4
Age
48
Location
close to the oktoberfest
XP
3,482
Country
Germany
when it comes to quen during the tutorial the following happens:
1. u cast quen
2. vesemir hits me repeatedly, me not taking damage
3. then he casts a spherical shield, i guess this is his quen, although i did not get the sphere when i cast it
4. then i am advised to make a quick hit (y), but if i press x or y the msg appears: you cannot do that right now ( i play german version, so just my translation)
5. then no progress

anny support? ideas ?
 
Don't know if you figured it out, but this happened to me too at the same Quen part. I had to just restart the game and load my last auto-save file. The 2nd time through the tutorial everything worked as it should. Weird
 
  • Like
Reactions: mrgone
Don't know if you figured it out, but this happened to me too at the same Quen part. I had to just restart the game and load my last auto-save file. The 2nd time through the tutorial everything worked as it should. Weird

i tried it now at least 3 times, but never started game from scratch, will try that next.


who of you plays the cart under atmosphere? without emunand?
 
That was a day one glitch in the original version of Witcher 3 on Xbox and PlayStation. Interesting that has returned on the switch’s complete edition. They patched it in a week originally. Could be they did this on purpose to prevent pirates or to stop early buyers.
 
so, i passed the part. without starting a new game or anything else.
just only do what he tell you to do. dont do more. dont move.

That was a day one glitch in the original version of Witcher 3 on Xbox and PlayStation. Interesting that has returned on the switch’s complete edition. They patched it in a week originally. Could be they did this on purpose to prevent pirates or to stop early buyers.

yeah, googling brought me to a forum post from 2015 about that bug.
must be a crazy bug to fix or else it's pretty embarassing.
 

Site & Scene News

Popular threads in this forum