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
Unfortunately, I cannot. I cannot access the M menu when this happens, neither can I click ESC to open up the menu, nor hold ALT to switch to a story character. All I am allowed to do at that point is to move the camera and look at the fast travel menu.
It always happens no matter what I do different (Even tried to restrict my NAT to see if it changes anything) nothing works, and the fast travel consistently locks my game and forces me to restart in order to do anything.
This has happened in public, solo, invite only lobbies, populated or otherwise.
For me this has only happened when travelling to North Chumash, what about you?
If so that could be the problem but otherwise i have no idea why this happens.
There is always a chance in normal pup sessions that cheater simply mess with the rest, which creates such trouble because it was valid strategy to harass session with missiles and quickly escape through fast travel if anyone went after the sub
could be also some bug related to too many assets present in a fully crowded session
tested north chumash in invite only and mine worked normal
Year ago these things never occurred, at least not to me.
There are two options to break the "hard bug":
1. Restart the game;
2. Click "Home" button and join on session to one of your friends (if online).
This is actually not a "Kosatka fast travel bug", it's related to server issues (on R* side), I'm getting the "Transaction pendidng" a lot. It has nothing to do with the Kosatka itself, or any mission or anything related to using the submarine, it's just server issue in general. It goes as far as stopping my car dead in the spot with a black confirmation screen. It happens quite frequently in recent days.
Imagine doing some time sensitive mission and you're driving fast on the Los Santos freeway, then you get "Transaction pending" followed by the confirmation screen, that reads something like "we're sorry, but we're unable to connect to the R* services right now, please try to reconnect later" and you're prompt to hit ENTER to close this screen, while you do, you end up back in the game, but now your car is standing still on the spot, but your precious time still runs. Again it's not related to the Kosatka at all. And it might not even be related to your internet connection, like I mentioned, it's on R* side. Some days it's fine, some other days "Transaction pending" happens a lot, followed by that black confirmation screen.
And while the game is Peer2Peer, R* does indeed have servers for matchmaking, profile saving and other stuff, if those go out, you can't pretty much play the game, since you get "Tramsaction pending/Transaction failed", confirmation screens (that stop you dead in the spot) and other similar stuff. R* should really focus on fixing their stuff, damn it.
And I am seeing a lot lately that "transaction pending" thing just constantly loading at the bottom of my screen spinning away even when I have made no transactions.
might recommend verifying file integrity through Steam.. maybe disable any firewalls, antivirus/antimalware, or other 3rd party programs that might be interfering..
My kosatka is completely unusable when it comes to fast traveling.
Every single place I try it says transaction pending then the game gets stuck.
Only way to get out of it is by pressing ALT CTRL DEL to close the game.
Typical rockstar, happy to take your money but not happy to fix basic issues in this 10 year old game.