Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
BTW, capping the framerate of your game also works. (to 60 fps or 30 fps if you still experience problems) with, for instance, a program like RivaTuner Statistics Server to get past this bug. Just saying this as a general FYI/PSA.
Here is another
install Fraps
set it to fps 30
start it while playing Final mission
when you hang under the helicopter trying to crawl up start recording with fraps.
Then press forward (hold) and tab space like a mad man until Niko crawls into the helicopter.
after that you can turn of fraps and play the rest of the mission.
Hi there, owner of i5-7600 quad-core here. The mission was done in the first try w/o any issues. My v-synch was on. Try with it.
Rockstar games are not designed to go above 30fps. GTA 5 starts to bug out, even RDR2 starts to bug out.
I don't know why they keep tying stuff to the framerate, it's a bad practice especially for modern standards. Even for 2008 standards tbh
. I Run GTA V flawless at 144 frames with 0 laag or bugs.
In GTAIV it's same problem,the only solution is turn on the VSync,the fps will lock at 60 frames and you can do anything without problems. Just try it bro.
You are outright lying. At 144+ frames you would be failing "Complications" over, and over, and over. Because a car is vibrating so hard it scares simeon into failing the mission.
Also, any physics props become heavier at higher framerates. And cars go physically faster too.
In red dead redemption 2. Core drain rate is tied to framerates. The faster you run the game, the faster they drain.
I am talking about GTA V where i can set it to 144fps and like i said my game runs flawless so that this guy is saying
'Rockstar games are not designed to go above 30fps. GTA 5 starts to bug out, even RDR2 starts to bug out.'
so basicly this SirDuck is saying you cant play Rockstar games above 30 frames,
which is a lie
yes his patatoe PC might not be able to play above 30 fps?
but others will.
Really annoying to even test the solution for this since it takes like 20 minutes just to get to that point in the mission every time.
I just completed that mission not sure what cpu you are running but just before taking the jump i paused the games and set cpu affinity to only use cpu 0. I then made the jump pulled myself up to the helicopter and as soon as i had control i paused the game and switched back.
I completely get you when i had it happen to me i turned the game off and was almost going to never try to beat it again until i found that solution.
It's a horrible bug to still have considering the game was launched in 2008 and firing up the new version of the game it has copyright 2006 to 2020 indicating that they had updated the game in some ways.
Ugh, no idea why it didn't work. Ordinarily, I'd just test it a few times in case I screwed something up, but when it takes so long - why bother?
I did almost exactly what you've described and I do have a fairly good processor. i7 8086k at 4.00 Ghz (kept at stock speeds). As soon as I see the target for the boat to reach to engage the helicopter jump, I tab out and switch the game to Core 0. Go back in, drive the boat to the yellow arrow under the helicopter, engage the little minigame, spam the button to get Niko in. The only thing I didn't do was tab back to re-enable the other cores. Mainly because the helicopter seems to spin out of control and explode almost immediately with a prompt that says "get back in the helicopter" (even though I AM in the helicopter!).
It happened when I didn't touch the affinity settings and happened almost exactly the same when I tried this fix.
Having a game that's buggy AF with zero intent to ever fix it is shameful enough. It's a whole new level when a seemingly-unavoidable bug makes the game virtually impossible to actually finish at all and the developer continues to sell it.