Shadow of the Tomb Raider

Shadow of the Tomb Raider

Visa statistik:
Denna tråd har blivit låst
Lethe 8 feb, 2019 @ 1:45
[Solved] Potential Bug on Path of fear?
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.
Senast ändrad av Lethe; 26 dec, 2019 @ 17:33
< >
Visar 31-45 av 66 kommentarer
L17TLEY89 1 maj, 2021 @ 4:13 
hi i had the same problem as this, the switch would not work kept getting killed.
after reading these and due to a previous problem in the game where i was running to high of an fps where the date code stones would not turn,
i done this to get past this switch. In the game graphics menu i set my settings to min 50hz lowest u could set then ran half frame rate setting looked like crap but the switch worked 1st time with these settings. just put them back to normal after hope this helps
Ursprungligen skrivet av 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.

Thank you for this, worked a treat. :steamthumbsup:
-0.0001x 9 jul, 2021 @ 10:17 
omg... rea;;y just push the damn thing few times... wasted 3 hours running all over the place.... anticool man
cold 31 okt, 2021 @ 9:33 
v-sync @ 60fps fixed this for me. dont think this is intentional why would changing fps fix it? Person who suggested this was on purpose is a tool
texaskatliami 8 nov, 2021 @ 13:26 
@Phantom

Ursprungligen skrivet av 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.

this worked for me ty I gave award as well
drivel 9 nov, 2021 @ 16:32 
Still a problem. Lowering res, using half speed vsync, and windowed mode worked for me.
Pandemonium 3 dec, 2021 @ 13:30 
Had this bug happen to me I play on a 120hz screen had to cap it down to 60 to progress lol!
HomeChicken 18 dec, 2021 @ 8:48 
THIS IS AN EXTREMELY ANNOYING BUG

I mean give me a break. Stone levers are SO wack. Just don't work. Doing the above -- **1/2 refresh rate** at 1080p with DLSS turned off to try to force it to run at 30 fps worked.

The WORST thing is that:
1) you CANNOT just go to an old save file if it has already saved
2) you are on path of fear so the only way forward, it forward (restated you cannot backtrack), and
3) fast travel IS NOT available at this point.

Basically, you have to just remove ALL good graphics, make it run at like 30 fps and then it can work.

How long has this game been out and they STILL haven't fixed this bug??!!!!!!

Just SO stupid.
Rasta 20 dec, 2021 @ 11:50 
Ursprungligen skrivet av 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.
Thank you! I turned on Vsync to half of refresh rate (30) an it worked on first try
Prospect 4 feb, 2022 @ 14:35 
Hello everyone. I've just met with this problem. Then I decided to share my own experience and my solution. I've spend a few minutes for this bug but at last passed the mission. Of course I did record it for the people who had the same problem.
https://www.youtube.com/watch?v=uOIudbLSXOs
Snake 1 jul, 2022 @ 11:37 
Another way around that has worked for me in this instance and some of the previous challenges is to set your game to exclusive full screen mode and set vsync on at 60Hz, as it seems the game engine breaks a bit when running above this and not locked in.
hieronymusishere 22 jan, 2023 @ 12:37 
This worked for me, tried moving the actuator rock and it wouldn't move. Immediately after that i set this values in the graphics menu and it worked:

DirectX12: Yes
*Resolution: 1366x768
*NVIDIA RTX DLSS: Disabled
*Intel XeSS: Ultra (after leaving the menu, the frames plummeted in the menu but the game ran fine, i don't know what happened)
*Full screen: Yes
*Exclusively full screen: Yes
Monitor/screen: NVIDIA 1660 Super (my graphics card)
Brightness: about 80/75%
Resolution modifier: 100%
AMD FidelityFX CAS: No
Refresh rate: 60hz
Vertical sync: Pending: enable graphics configuration
HDR: No
HDR Luminance: 100%
Smoothing: Intel XeSS
Stereoscope: disabled

* settings in switched on and off without any consideration and worked somehow, i don't remember the order but this are the settings i used to make it work.

My game is in spanish so some words may be not translated correctly, this are the only settings is tweaked i don't know it it'll work with other people
Stalkkiler 4 feb, 2023 @ 13:19 
Ursprungligen skrivet av 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.
This one worked for me,
Playing on nvidia GeForce now) now I save much more often
someoneevil 7 apr, 2023 @ 18:15 
You just turn on vsync. You do not need to do anything else to fix it. Graphics still look great doesn't seem to hurt anything by doing just that.
Pezatron 29 apr, 2023 @ 7:32 
F U Tomb Raider, uninstalled now
< >
Visar 31-45 av 66 kommentarer
Per sida: 1530 50