Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
Steam, but through family sharing. There's absolutely no reason it should cause that problem though.
It still doesn't explain it but perhaps something causes the marker responsible for identifying the ledge not to appear and you get blocked. Or some other miniscule miscalculation because of your cpu architecture.
Heaven knows, that's why we players file bug reports and they take a look at them.
One more thing, when you go to the options menu, do you see Advanced graphics options? All I see are Effects and Basic.
Filtering and vsync under Basic and the rest under Effects. Nothing about advanced.
I FIXED IT!!
Ok, I figured if iod's save file didn't work, it had to be on my end. So I tried different settings with my video card, and nothing worked.
Then I remembered reading that most of the bugs in Warrior Within were tied to VSync, and that having VSync turned on fixed them. This didn't work for me, then I tried something crazy:
My monitor's refresh rate was set to 120hz. I set it back to 60hz. Then I tried again and lo and behold, I can grab the ledge.
So holy ♥♥♥♥♥♥♥ ♥♥♥♥, OP, turn your monitor's refresh rate down and keep VSync on. That's how you solve this.
It feels amazing to finally put this bug to rest after 48 hours of frustration. Jesus christ in a chicken basket.
Congrats! Nice job on the ingenuity.
Good that it was a quiet place and not some ledge in the middle of a Dahaka chase :)
Thank you so much! I have GOG version and almost gave up with this game.
For those who are interested, I had a problem similar in The Two Thrones where at the end of the game you have to use pilar with a mecanism that made you jump wich was broken (always falling). It was that the PoP engine have some trouble with multi-core. Disable them and it worked.
With G-Sync enabled, there was still 100-200 FPS, after turning it off - strictly 60 FPS.
So my conclusion: you need to have exactly 60 FPS to avoid this bug (and also there was are other minor bugs when you have 100-500 FPS on modern PC, such as Prince is levitating for 1-2 sec instead of jumping down).
It also explain why not everybody facing this bug, and why it was all good 10 years ago.
The game is actually designed to run at 59fps, not 60. Supposedly, cutscenes go out of sync above 59fps.