This article has a talk page!This is a sub-page of Bugs:Grand Theft Auto V.
|
To do:
|
Franklin And Lamar
Floating Cat#
When playing this mission with 'Distance Scaling' set to a low value, the electricity box seen in the yard doesn't spawn in. This causes the cat scripted to be in this sequence to float.
Cut-scene UI Issues#
For the cut-scene where Franklin and Lamar get into the cars, when the player waits until the evening in in-game time (around 23:00), the cut-scene showing Franklin and Lamar getting into the cars glitches out and accidentally keeps the mini-map on screen.
Repossession
Disappearing Showroom Cars#
After leaving the showroom, the player can turn around and come back to the showroom. When the player does this after driving roughly one block, the cars will have mysteriously disappeared.
This happens due to the game not respawning these cars when the area is loaded back in.
Wrong Ped Damage Audio For Lamar#
During the driving to the meeting section of this mission, when Lamar gets hurt he uses the generic male pedestrian damage sounds. Throughout the rest of the mission Lamar does not have any damage sounds.
Glitched Enemy Spawning#
When climbing over certain objects during the shootout scene, for some reason, all enemies will be spawned in at once instead of them spawning in waves. This glitch is commonly used in speedruns of the game.
Paleto Score Setup
'Shooting The Alarm' Sequence Break#
During the Paleto Score setup, if you enter the 'shoot the alarm' sequence without a gun you'll be instructed to buy one. If you kick the alarm during this sequence the mission breaks. As this causes the alarm to activate during a sequence where it should be impossible to activate. This leads to a sequence break where the alarm will be going off, but nothing happens. The mission blips also glitch out during this. If the player after doing this glitch goes to the gun store, buys a gun and then travels back to the bank the mission will continue as if nothing happened. Completely skipping the 'shooting alarm' part as that was already completed.
Glitched Bike Race#
When the crew is sitting in Michael's car at the gas station, a motorcyclist pulls up in front of them and leaves a bike near Michael's car. This bike is later used by Trevor to race against Michael whilst driving back to Trevor's meth lab. This sequence can be broken by spooking the motorcyclist, which can be done by pointing a gun at him. This sequence break causes Trevor to stop moving after leaving Michael's car and it causes a floating copy of the motorcyclist on his bike to spawn at the endpoint of the race. This sequence break can also cause the ending cut-scene to be skipped entirely, which leaves Lester in Michael's car.
Predator
O'Neil's Jumping Out Of Car#
During the O'Neil's chasing sequence, the player can force the O'Neil's to jump out of their car by lighting their vehicle on fire. Even with the O'Neil's no longer driving the car, the vehicle will keep on driving to the endpoint where the cut-scene triggers. Said cut-scene puts the O'Neil's back in their car, which prevents this glitch from having an actual impact on the missions gameplay.
Chopper Invulnerability#
During the mission Predator, after getting into Trevor's Chopper, the chopper is made invulnerability to explosions. This is done so the chopper can survive the O'Neil rocket attack. The effect is however applied to early in the mission, allowing the player to exploit this invulnerability. The choppers invulnerability can most easily be seen in Fort Zancudo.
This invulnerability is also applied when flying back to the airstrip at the end of the mission. Though, due to how Chop was programmed in the mission, he isn't actually seated in the chopper which allows him to die to explosions whilst inside the chopper, which triggers a mission fail. The rest of the characters do survive explosions targeted at the chopper.
Monkey Business
Collision-less Crate#
At the end of the mission Monkey Business, after dropping the crate containing the nerve agent onto the back of a trailer, said crate will have no collision properties. This glitch does not work when a mission fail has happened and the bug doesn't occur on mission replays.
