Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closing and Reopening the Steam Window is Needed for Games to Launch Properly with Hybrid Graphics Laptops #11654

Open
BugsyReportsy opened this issue Jan 10, 2025 · 2 comments

Comments

@BugsyReportsy
Copy link

BugsyReportsy commented Jan 10, 2025

Your system information

  • Steam client version (build number or date): 1733265492
  • Distribution (e.g. Ubuntu): Pop_OS! 22.04, Linux Mint 22, EndeavourOS (Presumably happens with every distro.)
  • Opted into Steam client beta?: [No]
  • Have you checked for system updates?: [Yes]
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
  • GPU: Nvidia+Intel

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

When launching games with a laptop that uses hybrid graphics or PRIME switchable graphics, they would often freeze a few seconds after launch unless I close and reopen the Steam window first. I originally thought the issue was specific to certain games in my library failing to launch properly, but I had just figured out it was entirely because of my laptop's hybrid/PRIME graphics setup. This seems to occur most consistently with games running with Proton, but this sometimes happens with native games as well.

Steps for reproducing this issue:

  1. Launch a game and then exit it after it launches.
  2. Launch the same game again just afterwards.
  3. Close and reopen the Steam window, then launch the same game again.
  4. Repeat the steps above with a game running on Proton.
@kisak-valve
Copy link
Member

Hello @BugsyReportsy, this issue should also be mentioned to your video driver vendor if it hasn't been already.

@BugsyReportsy
Copy link
Author

BugsyReportsy commented Jan 10, 2025

Hello @BugsyReportsy, this issue should also be mentioned to your video driver vendor if it hasn't been already.

This bug has occurred since at least NVIDIA driver 545 and is still happening on driver 565. This happens with Ubuntu's, Arch's, and Pop's drivers, so I don't think this is vendor/packager specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants