[Solved] Potential Bug on Path of fear?

[Lethe]

So i got in the valley in the path of fear, and there is a particular stone trigger for that giant flute i can't move, I'm pretty sure this should be a bug because in other people's play through video, they have no trouble moving that stone. my problem is that the stone won't move or move very slowly then got stuck.

[JoaoB]

I also have the same bug

[arsnasir]

Hey everyone,

I came across this issue as well and realised that it might not be a bug afterall. What I did was that I had reached the second set of stone triggers on the left hand side wall (while facing front) without ever using the first trigger because it is not necessary to use the first trigger to keep moving ahead.
If you simply cross over to the right hand side, then jump across without using the folding bridge (which is possible), and then use the rope arrow to come back to the left side, you never actually activated the first trigger on the left. This is what I did and, therefore, it doesn't work.
The idea is that these mechanisms are based on wind blowing through all of them which is why they are synchronised. Every time the wind blows, all the mechanisms are activated one-by-one. My understanding is that this is the reason why the second set of triggers might not work if the first one had not been activated.
I was able to 'fix' the issue without reloading a previous save or having to change my display settings. Hope this helps.

Cheers.

[Phantom Liberty]

Found the solution, at least the one that worked for me.

Seems like the code for pushing the triggers is tied to your frame rate. The higher it is the harder it is to push. Simply cap your fps to 60 and try again. Also try 30 if you still have issues with some of them.

I'm running a 9900k & 2080 ti getting 120fps. Only one of the switches worked but that was probably because my fps was lower looking in that direction. Capping to 60 worked like a charm for most of them but I had to cap to 30 fps for some as well.

[Daniel-k]

@Phantom Liberty, you saved my gameplay, thank you! I would never thought about changing fps or resolution. In my case, I had to try multiple different combinations of: refresh rate (Hz) + resolution + resolution modifier. But finally I found working setting and get through this level.

[Stack]

Not solved. Still bugged cannot progress. Uninstalled

[noname]

I had this issue yesterday. Limiting the FPS to less than 60 helps. I capped it at 50. Use the tool called RTSS to do that.

[Izumi]

Originally posted by Clementine:

Yes this is a bug i reported 25 days ago and still no answer. I fix this on PC by change resolution to lower (i play on Full HD) and HOLD the button to move until works( do not release the button). You probably die dozen times because the button moves slowly but it works

That saved my life. Holy SH*T, My last Manual Save was at 38% while I played at 78%.... damn, I'm glad it worked with lower resolution. And btw I didn't die trying it, I just had to back up 1 time, before the spears come out.

[miersuzzemes]

Uninstalled

[coLo]

I found a solution. Lower res to 1366x768, go to window mode. Then Push, before the trap goes off, let it go, hide in the corner (behind the statue is the nearest safe area) then repeat until you see progress. This is indeed a bug that I think would require changing of environment to fix. I pushed it like 10-15 times (without dying and slowly you can see progress).

[RageOfPerun]

Originally posted by miersuzzemes:

Uninstalled

This is an Optional challenge not even the main game

[Hovercraft]

I had exactly same problem, and I tried dropping frame rates (could not go below 60fps).
In anyway it seems that you need to push the stone multiple times, it kind of got stuck at 70% on first couple of tries, and it took another 2-3 tries to get it going. It resets if you die...

[eggy ladd]

The only solution for me was playing in windowed mode, lowering res to 1366x768 and using vsync at half sync at the same time. Still, it took me couple of tries. This game and its developers are so bad that they don't even care about this bugs. They just want to get more money from the Tomb Raider name, so they just make a ♥♥♥♥♥♥ game that is worse than the previous 2 with full of bugs and non-sense things.

[Lazyeyegamerz]

Originally posted by coLo:

I found a solution. Lower res to 1366x768, go to window mode. Then Push, before the trap goes off, let it go, hide in the corner (behind the statue is the nearest safe area) then repeat until you see progress. This is indeed a bug that I think would require changing of environment to fix. I pushed it like 10-15 times (without dying and slowly you can see progress).

The solution i did was just seting the v-synk too half and that fixed it(No window mode)...dont use v-synk...just turned it on so i could potentialy fix it witch it did :D

[mattycoombes]

Honestly? I don't think this is a bug. It seems as though this particular stone is a bit stuck, and requires multiple attempts to move it in the slot. It's an absolute pain in the ass (and kind of reminded me of old school Tomb Raider games where grind and precision was necessary all the time!)

Here's my solution: When you get to the stuck stone, after the spikes retract, walk up and push it half way. Then release and get off the spike floor. Repeat this method a few times, while always giving yourself enough time to calmly step off the spikes. Sometimes the stone will reset, some times it'll stay half way. Eventually the stone will be right on the edge, and all you need to do is repeat the method and it'll fall in. No VSYNC, no changing frame rate or windowed mode. Just good old fashioned annoying, irritating puzzle solving.

EDIT: Holy ♥♥♥♥♥♥♥ ♥♥♥♥ after doing all this I fell off the ♥♥♥♥♥♥♥♥ zipline. Be careful guys and girls!!!

[smashsmack]

I just had the same exact problem. I turn off V-Sync, went windowed mode and the lever finally started to push after a few tries. I'm still not sure if this is a bug, or was done intentionally, but it was pretty damn frustrating experience to an otherwise good side quest.