Yeah that makes total sense! Hopefully they can access and look at some of our data files that are possibly causing issues to help figure out this problem.
I guess another option would be to give us an option to do a hard reset on our binds. Let us have the option to clear out all of our binds in a way that resets it fully. The option we have in the game does not fix this issue. We could at least take note of all of our settings and then do a hard reset and then put back all of our binds.
I have the exact same problem since the last update. This is getting really annoying. I’m also on PC. Getitng in the car is easy, getting out with the same keybind does not work, neither with another keybind. The only solution, whihnc is not a solution, is drive the car in the ocean or let teammate destroy the car.
Yep, that’s exactly what I have. We basically can’t use vehicles. And in squad games the best we can do is stand on a car if the team is using it.
I know there is a way to fix this. Hopefully, Epic can spare enough time to figure it out.
Another example that I remembered:
Before many seasons ago, this worked fine (using same keybinds for opening inventory and leaving vehicle), it used to have priority to leave the vehicle. Now it wrongly do both (and since leaving vehicle is a hold action, in stw, opening the inv at same time breaks it and completely stops exit), this is worse than my original example with creative vehicles… I can only leave the boar on the video by double jumping (which is a gameplay action that also dismounts it)
Still can’t exit as of today Sept. 23rd 2026.
Another issue that may be related to this thread:
Yeah it could be related. I just don’t understand why I can’t bind ANY key to my exit vehicle. And it’s the only action that is causing issues.
Thank you @PixelandPoly and @Sprintermax, I’ve shared that info with the team.
Thanks @Flak ! I really appreciate the team trying to solve this issue. If there is any other info or things the team would like us to test on our end just let me know.
Wow, I really hope this fix works! Thanks again to everyone who has been working on this!
FORT-1145232 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 42.40.
