-
Notifications
You must be signed in to change notification settings - Fork 164
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
Wine Support #102
Comments
WinForms simply doesn't support Linux, this isn't a directory issue, nor are games ever found in ProgramData. The program doesn't have any standard location it looks through for games, for Steam in particular it parses ACF and VDF files branching from the base installation directory to all library directories to eventually all game directories. The same can be said with slightly different methodologies for the other supported game platforms. Thus, assuming your games are installed properly, this feature should not be necessary at all and you're likely trying to use the DLC unlockers on games they don't support (such as illegitimate base games). |
No, winforms does work on linux with wine (which is a compatibility layer). It behaves like a VM that just puts your real file system in a different spot from what this program expects. So selecting your steam base directory (instead of assuming which place it is in) would be what would be needed. |
In that case then, I suppose the real issue then is the absence of the registry to point the way towards the Steam installation directory automatically. You need to realize that the discovery of the Steam directory and all other directories required for that matter work flawlessly on Windows, their location is not just "assumed". I'd have to look into how wine operates their file system and/or installations to see if automation of finding the Steam directory or game directories is possible, and fall back to a manual directory selection function should it not be. The goal of the program is to automate as much as possible for the user, so I'm hesitant to add manual functions where they could easily be automated of course. |
I would love manual directory selection also .... I have some games that I am "trying" that are stream games before buying as my daughter changes her mind about games so much I don't like to put out the money just to have her quit them a week later. I use Windows 11. |
You don't need manual directory selection, and matter of fact for your case you don't even need this program at all, the unlockers this program uses are for legitimately owned base games. An illegitimately owned game would come with a completely different crack that includes DLC. |
I would love to see this working with proton on the steamdeck. I know its not your fault, but if your program can be get to work on proton or wine and have the dlc's unlocked, it would be awesome So not sure if it is a container issue or path issue (not sure if those are the correct terms). I can access via some kind of "explorer" the files, and see the windows files as well |
For now we can follow this guide on Reddit to get it working on some games. It uses the SmokeAPI files from this repo. Works flawlessly with Tabletop Simulator. Instructions copied from the Reddit post:
|
Too bad, this won't work anymore with Steamv158 dll |
Pinball FX was updated lately and the DLL was moved to another place : Engine\Binaries\ThirdParty\Steamworks\Steamv158\Win64 |
I want to add that i had some limited success in running CreamInstaller on Nobara. Adding it as a non steam game successfully lets me see and successfully use CreamInstaller on any game i have installed on my primary partition. However it doesn't let me see any game I installed in my secondary partition, listed in steam in another library. Letting me manually select an additional library would definitely solve the problem. That, or looking "harder" for more libraries i guess. But adding a manual folder check does sound easier. |
On linux (and Im assuming MacOS) Steam library locations can be found from While I think Heroic will be harder since currently at this point they do not have a library system like Steam https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/issues/ 1673. I think by default it would install at |
This worked for me. |
Maybe adding instructions for Linux would be a good idea, simply adding the .exe as a new game and forcing Proton is enough 👍 |
those instructions work if your games are on a single library. last time I
checked, multiple libraries won't work on Proton.
Il mar 25 giu 2024, 14:27 Gpinchon ***@***.***> ha scritto:
… Maybe adding instructions for Linux would be a good idea, simply adding
the .exe as a new game and forcing Proton is enough 👍
—
Reply to this email directly, view it on GitHub
<#102 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6J5B3VKPUNEYQ6G35NCH3ZJFO43AVCNFSM6AAAAAAYAUBKICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYHAYDENZXHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Well, it could be specified as a limitation of the current version in the instructions to avoid further bug reports on this "issue" while @pointfeev works on it if he feels like it. It could also just be specified as a limitation of the project for Linux 🤷♂️ |
I can confirm that this method works without a hassle. You really just need to add CreamInstaller.exe to Steam. Distro: Debian 12 |
my issue is that this method works perfectly only of the main library. any
secondary library that you might have on other volumes is not recognised.
Il sab 6 lug 2024, 10:13 nauxnam ***@***.***> ha scritto:
… Maybe adding instructions for Linux would be a good idea, simply adding
the .exe as a new game and forcing Proton is enough 👍
I can confirm that this method works without a hassle. You really just
need to add CreamInstaller.exe to Steam.
I tried using this on Deep Rock Galactic (disabling koalageddon was my own
choice you can enable it).
Screenshot_20240706_110726.png (view on web)
<https://github.com/pointfeev/CreamInstaller/assets/12861777/b314eb2d-8815-4268-95c9-9d5f263587bb>
Screenshot_20240706_110754.png (view on web)
<https://github.com/pointfeev/CreamInstaller/assets/12861777/e33eeae7-6f53-4c97-804a-97a2f2e4a1a5>
Screenshot_20240706_110907.png (view on web)
<https://github.com/pointfeev/CreamInstaller/assets/12861777/44046903-ea2a-4e37-9e52-b8df7497f98b>
—
Reply to this email directly, view it on GitHub
<#102 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6J5B62IWS6IDD3YP4Q34TZK6RJLAVCNFSM6AAAAAAYAUBKICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRG4YDENRSHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I would love for this to allow selecting the game location manually for non standard installation locations. More specifically I am requesting this because on Linux (using wine) the steam games are in the Z drive in a non standard (not a ProgramData folder) location, which makes it impossible (without linking directories) to use this software. See also #101.
I am not sure if this would fix all Linux issues and work with all games, but this seems like a somewhat easy-ish to implement solution, and like something that might be useful for linux gamers as well.
The text was updated successfully, but these errors were encountered: