BloodSlut
Pretty much this, your post could still end up on search engine results, people could share your post through posting the URL on other sites, etc.
It just means there’s better connectivity and (hopefully, in the near future) better content serving. Also you don’t need to create an account for every single site (if you dont want to)
This confuses me as to what the long term appeal of a lemmy or mastodon account is. Would general users be better off joining kBin, while users who want to only interact with mastodon, or only interact with lemmy, and not with each other, would join either lemmy or mastodon?
It sounds like KBin has the best support for acting as an alternative frontend for lemmy and mastodon. If someone on lemmy links to a mastodon post, or vice versa, you have to leave the instance to go view and interact with the post, but on kBin that could not neccesarily be the case.
It just seems like having some sort of universal frontend would be the most flexible and not have any downsides.
That makes sense! I guess for me, personally, if I want to be able to access and interact with multiple types of media I should create an account with a platform that supports multiple other platforms like kbin does.
I wonder if there will be a platform that is dedicated to supporting as many of the other large fediverse platforms as possible.
Thanks for the explanation!
Yeah, its pointing out of the wine directory too.
I actually ‘fixed’ it by creating a symlink to the home folder, and the installer ends up creating a folder with a set of DLLs:
- D3DCompiler_47_cor3.dll
- PenImc_cor3.dll
- PresentationNative_cor3.dll
- vcruntime140_cor3.dll
- wpfgfx_cor3.dll
I think some of these could be installed into the prefix using winetricks, but I’m not sure about the others.
Although this does ‘work’ (and by work i mean it gets rid of the current error, the entire installation process is still borked but now it’s just further down the line) I’m not sure I’m comfortable with the fix. Ideally, I would prefer everything getting installed to reside within the WINE prefix. Finding out what was throwing the path error would probably help but I’m not sure how to figure that out or if it could even be changed.
I already have dotnet installed natively (driver, runtime, SDK, and targeting pack). If I could figure out exactly what was calling the error I could have a better sense of what’s going on.
The weird thing is that the game itself is running Mono, which Lutris appears to automatically set up when creating a prefix, and even if the launcher/game isn’t recognizing it, I don’t know why it would be trying to use .NET, let alone installing and accessing prerequisites outside of the prefix.
The game_slug is just an internal ID for Lutris, it would be used for if/when I upload the installation script to the Lutris website.
Installation through Steam was a no-go, I’m not sure Steam and stock Proton have the tools required to get this running, and Heroic likely wouldn’t be much different.
The game itself is an alpha-test under NDA, so I can’t disclose too much, (and why I haven’t been able to find much helpful information searching online). It has a standalone installer and launcher which is what I believe is causing the most issues. I can get in contact with the devs but I’m trying to avoid bugging them since there is not currently planned support for Linux.
Another thing I just thought of is that maybe the installer executable isn’t being run by the WINE prefix made for the game? It could explain how the path is both pointing to the installer’s directory even if outside of the prefix, and why its trying to install dependencies outside of the game’s prefix
Okay, so there’s nothing actually wrong with `DOTNET_BUNDLE_EXTRACT_BASE_DIR’, its just that its being inherited from the system and ends up tacked on to the filepath of where the installer executable is.
I think I need to locally clear the env var in the WINE prefix, but I am unsure how.
@ShaunaTheDead@kbin.social @bgtlover@linuxrocks.online
I got it to work!
Clearing the environment variable by adding
system: env: DOTNET_BUNDLE_EXTRACT_BASE_DIR: DLLs
allowed the launcher installer to properly handle the DLLs by creating a folder in the Game’s directory.
It appears that the game installs and launches fine, I’ve yet to test the actual gameplay, but that’s next.