Game Lags to the point of unplayability in Giantwoods

3

I’m currently playing Van Helsing 2 on a PS4 pro. I’m playing coop on fearless difficulty. I’m currently at the giant woods. The problem is so many enemies have spawned (mostly stick lizards) that the game is literally unplayable. I am barely able to move and cannot attack as the game is lagging so much. My coop partner has the same issue when connecting to my game. We both have the same issue if we play solo. We have managed to run around and speak to the giant stone heads (with the hope of progressing the story and leaving the area) but after speaking to them all the ice wall doesn’t open and all objectives are removed from the map meaning we are stuck here. I have tried reloading the game, teleporting to different areas (with respawn enemies turned on and off) but there doesn’t seem to be a way to reset the board. Does this mean we need to start a whole new playthrough? I think it’s very poor game development to allow so many enemies to spawn that the game can’t cope to the point where there is so much lag the player can’t move or attack

This post was edited 355 days ago by Warlord99956
Store Page
Share
3 comments
Game Lags to the point of unplayability in Giantwoods
Your Thoughts? Please login to place your opinion. Not a member yet? Register here and now!
344 days ago

Hey Warlord99956,


Thanks for contacting us, we're going to look into the issue. Please make sure that you interact again with the first Stone Head - the one who gave you the errand to talk with the others - in order to lift the Ice Wall.

343 days ago
damngreatcoffee

We tried that but none of the heads were available for further interaction. I think it was due to the fact the board was so messed up and suffering from so much lag from the sheer amount of enemies that had spawned. In the end we had to start a new playthrough. We ran through the board and interacted with the stones straight away, avoiding the stick lizard spawners so as not to break the game again. 

343 days ago
+1
Warlord99956
I see, we apologise for the inconvenience and will try to address this issue with an update as soon as possible.