search

SteamGridDB / steamgriddb-manager

Automatically find games from launchers on your system and import them into your Steam library with a click of a button.
https://www.steamgriddb.com/manager
MIT License
397 stars 55 forks source link

SteamGridDB doesn't launch games when using Powershell V2 #83

Closed scaires closed 3 years ago

scaires commented 4 years ago

Describe the bug SteamGridDB doesn't launch games if the target PC has Powershell V2. No games launch if the user has this version of powershell, because there is an error in the LauncherAutoClose.ps1 script on line 17, character 71.

To Reproduce

  1. Run SteamGridDB on a computer with Powershell v2 (verify by launching powershell and running $PSVersionTable.PSVersion.Major)
  2. Import games (eg from Epic Store)
  3. Edit game's launch options in steam to remove -windowstyle hidden and add -noexit

The following error should show "You must provide a value expression on the right hand side of the '-' operator”

Expected behavior Steamgrid DB Manager should state somewhere that an updated version of Powershell is required, which should really only impact Windows 7 users who have an older powershell.

Operating System

Installed Launchers

Screenshots

Powershell v2:

image

Powershell v5

image

Log N/A

Additional context I was pointed in this direction by this stack overflow post: https://stackoverflow.com/questions/16149772/cmd-call-to-powershell-you-must-provide-a-value-expression-on-the-right-hand-si

An updated powershell can be found here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=54616

Thanks!

tarheels100 commented 4 years ago

I ran into the same issue. Some sort or warning or message to indicate what the problem is and how to fix it would be useful. Better yet, is there a way to make the powershell scripts used by SteamGridDB compatible with all versions of powershell?

aranel616 commented 3 years ago

Unfortunately, we do not support Windows 7, as Microsoft ended support for Windows 7 on January 14, 2020. If anybody can reproduce this issue on a later version of Windows, please open a new issue.