We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To reproduce this issue:
Then observe that in games.js, the paths to the game executables in your network folder are written in the form of //host/path, e.g.:
games.js
//host/path
{ "th08": "//vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/vpatch.exe", "th08_custom": "//vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/custom.exe" }
But the host part in the paths should really be written in the form of \\host, and without editing games.js to something like the below:
\\host
{ "th08": "\\\\vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/vpatch.exe", "th08_custom": "\\\\vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/custom.exe" }
thcrap_loader will fail to start the executables with bad paths, with the following error:
Failed to start <thcrap path>\<executable path> The system cannot find the path specified.
The text was updated successfully, but these errors were encountered:
A possible fix would be to add a special case in str_slash_normalize ensuring that network paths start with \\ instead of //
Sorry, something went wrong.
As a temporary workaround you can map the network drive to give it a drive letter.
No branches or pull requests
To reproduce this issue:
Then observe that in
games.js
, the paths to the game executables in your network folder are written in the form of//host/path
, e.g.:But the host part in the paths should really be written in the form of
\\host
, and without editinggames.js
to something like the below:thcrap_loader will fail to start the executables with bad paths, with the following error:
The text was updated successfully, but these errors were encountered: