GTA IV helicopter glitch still exists and makes the games final mission unbeatable

[Commander Cool]

I've seen this reported as early as 2013 but the glitch is still present today and is getting worse as CPU speeds improve.

I have a 8700k and this makes the final mission unbeatable in the new complete edition rerelease.

When you jump from a dirtbike to the helicopter that Jacob and Roman and piloting you need to quickly tap space to pull yourself up or a if gamepad.
This is impossible everytime you hit a or space the screen glitches and Niko won't move regardless of how fast you tap.

The only workable solution is to pause the game before the jump open task manager and set CPU affinity to only use 1 CPU core for GTA.
This is not a good workaround for a rerelease that cares more about patching out content then fixing game breaking issues.

Music was removed from radio stations multiplayer was removed and this game breaking bug that means anyone with a CPU faster then most in 2009 which is everyone will be unable to progress past the final mission.

[Selvator]

Ye this issue and quite a few others are popping up more and more as we get faster CPU's
I run the game on a 240 Hz monitor and if the game gets above 100 or 140 I get weird issues like NPC's that cannot open doors or are stuck at them, cutscenes zoom in way to much and bikes turn to quickly making them almost unusable.

I use MSI Afterburner that has an FPS lock build in that caps my FPS on demand in games like these.

However if anyone else has these problems and want an ingame patch/solution take a look at GTA 4 Fusion Fix:
https://github.com/ThirteenAG/GTAIV.EFLC.FusionFix/releases
And check the readme as well.

It fixes and patches a lot of stuff in the game and adding stuff like an ingame FPS limiter to fix these kind of issues a long many others.
In fact the script bug at high FPS at the last mission is actually fixed with this patch as well

[K3N]

i tried the core thing and it didnt work does somebody have an idea how i can make it work?

[Markie]

Автор сообщения: K3NP4CH1

i tried the core thing and it didnt work does somebody have an idea how i can make it work?

Disabling CPU cores to avoid the issue is a very rustic workaround. You're basically counting on your CPU being slow enough to drop the frame rate just enough to avoid the issue with a limited core count. Not sure why someone even came up with that.

[K3N]

Автор сообщения: Markie

Автор сообщения: K3NP4CH1

i tried the core thing and it didnt work does somebody have an idea how i can make it work?

Disabling CPU cores to avoid the issue is a very rustic workaround. You're basically counting on your CPU being slow enough to drop the frame rate just enough to avoid the issue with a limited core count. Not sure why someone even came up with that.

do you have an good idea how i can make it work then?

[Markie]

Автор сообщения: K3NP4CH1

do you have an good idea how i can make it work then?

Just limit your frame rate through any method instead.

[Selvator]

Автор сообщения: K3NP4CH1

Автор сообщения: Markie

Disabling CPU cores to avoid the issue is a very rustic workaround. You're basically counting on your CPU being slow enough to drop the frame rate just enough to avoid the issue with a limited core count. Not sure why someone even came up with that.

do you have an good idea how i can make it work then?

Have you tried the Fusion Fix I posted?
It fixes a lot of high FPS problems as well as allowing you to set a fixed FPS through the ingame menu.
Of course you could still cap the FPS through Nvidia or MSI after burner

[MrEWhite]

FusionFix fixes this problem.

[PsychoManiac189]

Автор сообщения: Markie

Автор сообщения: K3NP4CH1

i tried the core thing and it didnt work does somebody have an idea how i can make it work?

Disabling CPU cores to avoid the issue is a very rustic workaround. You're basically counting on your CPU being slow enough to drop the frame rate just enough to avoid the issue with a limited core count. Not sure why someone even came up with that.

I did this and it worked like a charm. Pause the game literally just before you hit the marker (orange or yellow) and switch it to 1 cpu (cpu0) and then turn it back on when you close the door on the helicopter. I will be using FusionFix from now on though

[redriot_12]

Автор сообщения: SirDuck

You gotta turn Vysnc on and set your resolution refresh rate to the 60Hz option. Then it'll let you do 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

THIS WORKED!! Thanks

[pottavia2]

I failed this mission nearly 20 times because of this glitch and threw my controller across almost through my 65" old. LOL
Then I Uninstalled the 1st person mod..still nothing. Finally I capped the frame rate at 60, and still while Niko was dangling from the helicopter pressing A on a x360 controller, still he was stuck.
Finally I was thinking it must be tied in with console coding of 30fps, and _finally_ Niko got in that helicopter and took out Jimmy P.

I'm using IceEnhancer Natural with a real vegetarian and high resolution roads with the 1st person mod.

In 4k at 120fps+ it looks GTA V quality.
While GTA V was just fun crazy over the top fun, the realism and storyline of IV is simlly unmatched.
And playing it in 1st person and updated graphics is one heck of an experience, some 16 years after it's release, it's still as powerful a story as it gets.

[fenderjaguar]

Автор сообщения: Selvator

Of course you could still cap the FPS through Nvidia or MSI after burner

fusionfix has MUCH less input lag. you can even cap at 30 fps and it still feels sharp
not that RTSS or nvidia drivers are laggy or anything (they are not), it's just they don't have access to hook the code necessary to cap in a low latency manner here

[Incarnate]

Cap fps at sixty. All Rockstar games are designed for meager-ass consoles, so the physics will spazz out at high-speeds. That's my rule of thumb for most games. That's sadly just a reality of playing games made pre-2012.

Anything made pre-2004 should probably be locked at 30, and, as the dude above said, have the CPU set to "one" in the "affinity" section in Task Manager.

[Selvator]

Автор сообщения: fenderjaguar

Автор сообщения: Selvator

Of course you could still cap the FPS through Nvidia or MSI after burner

fusionfix has MUCH less input lag. you can even cap at 30 fps and it still feels sharp
not that RTSS or nvidia drivers are laggy or anything (they are not), it's just they don't have access to hook the code necessary to cap in a low latency manner here

True, fusion fix seems to handle lower FPS/Capping better then doing it through 3rd party like Nvidia or MSI Afterburner I would advice anyone with any weird issues above 60 FPS to use Fusion fix and cap it at 60 fps, if you don't mind installing a mod/fix.
Fusion fix in theory even allows you to go higher then 60 fps and still don't have problems with missions that get bugged at higher FPS such as the mission mentioned in this thread.

However in my own experience when I play a mission I still cap the game at 60 FPS through ingame Fusion Fix settings, one of the problems I have noticed above 60 FPS is that for example NPC's have a hard time with doors, whether it is a car door or building door they seem to get stuck in them and not being able to continue, in missions this can be game breaking since an NPC get's stuck, so just to be sure I still cap the game at 60 fps.
Fusion fix is the best option here since you get little to no input lag, tearing, glitches etc.

For any other game however I have set an option in my MSI afterburner, I have set a universal FPS lock at 60 whenever I press ALT + N .
If anyone reads this and plays any other "old" game pre ~ 2012 etc. like Incarnate mentioned you may want to always have a shortcut to cap any game at 60 FPS to prevent bugs.
In my own experience I never had to cap any old game to 30 FPS to prevent bugs, 60 cap has always been enough for me but depending on the game your mileage may vary :)

[Markie]

Also worth mentioning FusionFix's frame rate cap works alongside DXVK's Vsync implementation perfectly well (which is not always the case when mixing frame limiters with Vsync) and you get both low input lag and visual smoothness without having random tearing due to things not syncing up properly which is really great.

[fenderjaguar]

Автор сообщения: Markie

Also worth mentioning FusionFix's frame rate cap works alongside DXVK's Vsync implementation perfectly well (which is not always the case when mixing frame limiters with Vsync) and you get both low input lag and visual smoothness without having random tearing due to things not syncing up properly which is really great.

to be honest, I tried DXVK vsync (d3d9.presentInterval =) and it's amazingly low input lag, even without a frame rate cap on top to cut down on buffered frames. it also works with your "presentinterval" like being like a swap interval, where (on 60hz) 1 will effectively cap at 60fps with vsync, then 2 will sync/cap at 30fps with vsync, with perfect frame pacing, but with hardly any input lag. although I was trying this on 240hz with the present interval at like 5//6/7/8 etc, so maybe it's the faster scanout of the high refresh rate which is leading to this very low latency