Some Outriders players are jumping into the game only to realize their HUD is not showing up. As it turns out, this is a common bug that seems to make the entire HUD invisible. Fortunately, there’s an easy way to fix the missing HUD bug and restore all of the game’s missing heads-up display details.
Outriders | How to fix the missing HUD bug
The missing HUD bug in Outriders is caused by an issue with the game’s heads-up display settings. Every now and then, the game will set all heads-up display elements to invisible, making it seem like there’s no HUD. You can fix the problem by reloading the game, toggling the HUD settings off and on, or by simply fast traveling.
If you dive into the Outriders settings menu, you’ll notice a series of toggles used to show or hide various HUD elements. These usually allow you to customize the heads-up display to your liking. However, the bug seems to set all elements to invisible.
According to Square Enix support, this is a known issue that the team is working on patching. In the meantime, they’ve provided an official workaround to fix the missing HUD bug. All you need to do is return to the game lobby, then re-enter the game. With luck, all of the HUD elements will reappear.
However, one user on the Outriders subreddit has provided their own solution that seems to fix the bug for for a number of players:
- Return to the game lobby, then disable all HUD interface options
- Enter a game, then re-activate all of the interface options
Basically, the solution is turn all HUD elements off, then turn them back on again. Exiting to lobby and then re-entering a match should also work, and some players have mentioned that fast traveling seems to fix the issue as well. Still, the best fix appears to be disabling and then re-enabling each element manually.
The missing HUD bug is a known issue in Outriders, and the developers are currently working on a solution. In the meantime, you should be able to fix the error by restarting the game, or by toggling all of the HUD elements off and then on again. Hopefully this issue will be worked out in a future patch.