Skip to main content
New Participant
July 28, 2025
Question

Golf + stuck on black loading screen.

Recently my golf + game decided when it wants to work and when it doesnt some days it starts up no problem, other days it just sits on a black screen everytime u open the application what do i do?

    2 replies

    Participant
    July 28, 2025

    Golf + stuck on black loading screen.
    If you're experiencing a black screen when launching or playing Golf+ on your Meta Quest headset, several potential solutions exist: 
    Immediate troubleshooting steps
    Reboot your headset: A simple restart can resolve temporary glitches. Hold down the power and volume down buttons simultaneously for at least 10 seconds to force a hard reboot.
    Check/Charge your headset: Ensure your headset is adequately charged, as a depleted battery can cause a black screen. Plug it in for at least an hour or two to ensure sufficient charge.
    Open the Oculus menu: Try pressing the menu button on the left controller or the Oculus button on the right controller to see if the menu appears. If it does, try launching Golf+ from there. 
    Further solutions
    Reinstall Golf+: If game files are corrupted, uninstalling and reinstalling the game might help.
    Check for updates: Ensure both your headset and Golf+ are up to date.
    Check network connection: Try connecting to a different network to rule out Wi-Fi issues.
    Reset Guardian: Clearing and re-setting up your Guardian boundary can sometimes resolve app launch problems.
    Launch from a different entry point: Try launching Golf+ from the phone app or voice command instead of the app library.
    Disable Experimental/Developer Features: If enabled, these features might conflict with app launches.
    Free up storage: Ensure you have enough free space on your headset (at least 3-5 GB).
    Factory Reset: As a last resort, if only Golf+ is affected, a factory reset can resolve issues but will erase all data. Back up important data first. 

     

     

     

     

    New Participant
    August 8, 2025

    I've got the same issue on my Quest 2.  Removed and installed 3 times - exactly the same outcome.  Very frustrating!