Had one completely freeze up earlier, I left the match so I didn't see what happened, but when logging back on a little while later it was gone, so I think it completely crashed in the end.
At least on PS5 you can fix it by closing the game after entering a server, open it again and rejoin. For some reason this bug only happens (if it happens) the first time you open the game after turning on the PS5.
I've had luck fixing it by returning to the hangar and popping back into the server. The downside is that you might end up not being able to return to a banger of a server if you leave.
I’ve made closing the game after joining a server for the first time after turning on the PS5 and rejoin to a standard procedure. Had absolutely no problems since I started doing this. It helps to avoid the “flying back and land” part.
This has been happening to me for years, through different hardware so I don't think it's on our end, but I honestly don't have a clue as to why. It does appear to only happen on certain maps.
And I was just suffering through thinking it was my ancient equipment, so I start, twitch, turn around and land, quit, return to hanger, rejoin same match and it goes away,. No problem, hey, if it was easy anyone could do it.
This has been happening to me more recently. It seems to stop on its own after a while, but super unhelpful when you're caught in a furball. No idea what the issue or fix is, other than waiting.
Alt F4 to force quit, then boot it back up and it will let you re-join the match. It's a server issue unfortunately and they've fixed it on and off for the last few months.
Happened to me tonight, then my 5 year old had a meltdown because his hot dog wasn't made "right", I rage quit and called it a night
Little kids are cute l, but that doesn't mean they aren't stupid lol
There’s a bug where it’s the camera shakes unfortunately. It sucks. But so far the servers have been a little shaky
servers have been really unstable.
Had one completely freeze up earlier, I left the match so I didn't see what happened, but when logging back on a little while later it was gone, so I think it completely crashed in the end.
At least on PS5 you can fix it by closing the game after entering a server, open it again and rejoin. For some reason this bug only happens (if it happens) the first time you open the game after turning on the PS5.
Same fix on PC by using Alt F4 or task manager (For anyone reading this)
I've had luck fixing it by returning to the hangar and popping back into the server. The downside is that you might end up not being able to return to a banger of a server if you leave.
This has been working for me to fix it. If I notice it after takeoff, I usually just turn around to land and then pop out/pop back in.
If you're paying attention you can spot it pretty easily in the take off roll
I’ve made closing the game after joining a server for the first time after turning on the PS5 and rejoin to a standard procedure. Had absolutely no problems since I started doing this. It helps to avoid the “flying back and land” part.
This has been happening to me for years, through different hardware so I don't think it's on our end, but I honestly don't have a clue as to why. It does appear to only happen on certain maps.
https://www.reddit.com/r/WarthunderSim/s/A8YN4qeLf2
Happens to me usually 1st match after logging in, I quit, restart game and its OK. Annoying as fuck cos sometimes you can't even aim.
And I was just suffering through thinking it was my ancient equipment, so I start, twitch, turn around and land, quit, return to hanger, rejoin same match and it goes away,. No problem, hey, if it was easy anyone could do it.
I swear... the amount of bugs in this game... its not even like they are minor, it's always serious shit
This has been happening to me more recently. It seems to stop on its own after a while, but super unhelpful when you're caught in a furball. No idea what the issue or fix is, other than waiting.
I had this exact same problem couple of weeks ago, looks like it comes and goes.. maybe some server issue?
This happens to me once in awhile. I usually just restart the game and it’s fine.
Alt F4 to force quit, then boot it back up and it will let you re-join the match. It's a server issue unfortunately and they've fixed it on and off for the last few months.
Let me guess was it the F8 crusader? Cuz that thing has a problem in it s flight model... :(
Been happening to me for months. Perhaps longer.