Guild Wars 2

In the personal story mission Under Siege for The Vigil storyline, after manning the trebuchet to destroy the risen siege weapons there is a cutscene immeidiatly after destroying the last one, and after the cutscene my camera was still focused on the trebuchet and didn’t follow my character. I was able to control my character but he eventually walked out of my line of sight. I exited the game and redid the mission again and the camera still stayed with the trebuchet, I was able to walk back to the trebuchet and re-enter it and then exit and the camera followed my character properly.

Happened to myself also, appears to be a fault in the trebuchet memory allocation once you complete destroying enemy siege weapons, tried it three times tonight, even after graphics card software update.

I got a bug report request screen, sent through each time.

Grievous.3568:

In the personal story mission Under Siege for The Vigil storyline, after manning the trebuchet to destroy the risen siege weapons there is a cutscene immeidiatly after destroying the last one, and after the cutscene my camera was still focused on the trebuchet and didn’t follow my character. I was able to control my character but he eventually walked out of my line of sight. I exited the game and redid the mission again and the camera still stayed with the trebuchet, I was able to walk back to the trebuchet and re-enter it and then exit and the camera followed my character properly.

this is the exact problem thats happened to me multiple times, i now cant continue with the story…

I have this exact problem. I have submitted a bug report but I’m
curious how long these things usually take to fix. Im really
enjoying the story and would like to see it through.

Small workaround my friend told me.

After the cutscene, use the NPCs minimap dot to guide yourself back to the treb, then interact with the treb (press F) and it should go back to normal.

Hope it works.

That worked. Thanks so much.

Same problem but the workaround does not work. It crashes as soon as the cut-scene ends, so there’s no time to interact with the treb.

Tinkerbell.8743:

Same problem but the workaround does not work. It crashes as soon as the cut-scene ends, so there’s no time to interact with the treb.

Same here.