CragnarTheCrimson

joined 1 year ago
[–] CragnarTheCrimson 1 points 1 year ago (1 children)

how do I manually install vkd3d through lutris? Also what log would I need to look at? I've tried running lutris from the terminal and reading that but didn't learn much.

 

this technically isn't a "crack" but it's within spitting distance of being one and it is still trying to circumvent DRM so this felt like the best place to ask. I'm using a downloader which has a free and paid tier, with the free tier limiting the amount of times you can use it per day. Since in linux you run everything in a prefix instead of natively, I figured it would be childsplay to figure out where it is storing the count and wipe it, thereby functionally giving me unlimited downloads.

This worked well enough, and I've pinned down a few places I know it's storing the count, but I'm at the point now where I'm bordering on thinking it's just dark magic.

Basically, I can get the count to reset if I delete config.ini from the software's working directory and paste in a reference prefix. But, if I then use the software, close it, and delete config.ini again, when I reopen the software it still knows that it's been used and recreates config.ini. This means that it is using something in the prefix itself to store usage information. (which is entirely expected of course, otherwise someone on windows could just re-extract the software and keep using it indefinitely with ease) However... if I then run a "diff -r -q" on the used-prefix (i.e. : the prefix where the software is storing that it has been used) and the reference prefix (i.e. : the prefix where the software doesn't think it's been used) these are the results

Files ./DOWNLOADER-PREFIX/drive_c/users/USERNAME/Temp/C41224A1DBA496C1FCF3946547B13945/540617BF672B559CF8DACEDD9AF401C5 and ./DOWNLOADER-REF-PREFIX/drive_c/users/USERNAME/Temp/C41224A1DBA496C1FCF3946547B13945/540617BF672B559CF8DACEDD9AF401C5 differ
diff: ./DOWNLOADER-PREFIX/drive_c/windows/system32/_nvngx.dll: No such file or directory
diff: ./DOWNLOADER-REF-PREFIX/drive_c/windows/system32/_nvngx.dll: No such file or directory
diff: ./DOWNLOADER-PREFIX/drive_c/windows/system32/nvngx.dll: No such file or directory
diff: ./DOWNLOADER-REF-PREFIX/drive_c/windows/system32/nvngx.dll: No such file or directory

With the "No such file or directory" errors being symlinks to linux equivilants of windows binaries. This indicates that the place where the software is storing it's usage information must be /USERNAME/Temp/C41... however I can delete that along with config.ini and it will still somehow know it's been used and set itself to the correct number of remaining uses.

Again though, I can get it to reset back to the default value if I paste in the reference prefix and delete the config.ini file. So, somehow, it's storing data within the prefix that doesn't show up anywhere on a diff scan; it's storing data without storing data.

I genuinely have no idea what is going on here and frankly I didn't even think something like this was possible. I'm half inclined to blame it on some networking check or some such but, well, then how can I spoof it by pasting in the reference prefix? I can't think of any explanation for how it's spoofable by deleting the prefix and replacing it with a reference one, but if I then use the software and compare the new prefix with the reference one it was copied from, then reset the differences, the result is still somehow a tainted prefix. (despite, according to diff, them being the same)

[–] CragnarTheCrimson 1 points 1 year ago* (last edited 1 year ago) (3 children)

by "manually install it" do you mean install it natively like I mentioned, or is there some way to actually manually update VKD3D through lutris' flatpak? If relevant, the VKD3D version listed under "Runner Options" is v2.9 and the Wine version I'm using is lutris-GE-Proton9-9-x86_64

Also, is it possible some of flatpak's sandboxing is causing issues here as well? The list of changes I made to the default flatpak permissions (using flatseal) are

1 : turned ON - GPU acceleration
2 : turned OFF - All devices (e.g. webcam)
3 : turned OFF - All user files
4a : ADDED access rights - /run/media/username/second-drive/Games
4b : ADDED access rights - ~/Games/

and everything else is not listed as having been changed by me within flatseal. Looking over these, I can't think of why any of them would be causing a dx12 issue, but I thought It'd be better to list them just in case. (as mentioned, while I do have my issues with flatpaks, I do still appreciate the ability to sandbox applications more thoroughly)

[–] CragnarTheCrimson 2 points 1 year ago (5 children)

update : shocker, installing lutris actually natively fixes the issue. This is why I avoid flatpaks. In any case if someone does actually know how to fix this with a flatpak installation I'd still like to know since it's annoying to have two seperate lutris installations on my machine and I do prefer the sandboxing of the flatpak install.

 

I've installed a dodi repack and I've installed it inside of a lutris prefix. The game launches as expected, however I have a high end GPU and I want to try enabling ray tracing to see what the performance vs fidelity change is like. However, in order to enable ray tracing I need to launch the game with directx 12. If I add -dx12 as an argument however the game doesn't launch, instead it pops up an error saying "DX12 is not supported on your system. Try running without the -dx12 or -d3d12 command line argument". I'm not sure if this issue is game specific or not, I thought so at first but the more I think about it, I don't actually know for sure if any of the games I've launched in lutris have been using dx12 or not, so it could be an issue with every one of my games and this is just the first one where it's been relevant.

(lutris is installed via flatpak if relevant. Despite my general distain towards flathub and the centralization of package distribution, being able to install sketchy software inside of a sandbox is a big plus. Most windows malware doesn't really work inside of wine anyway, but keeping it inside of a flatpak confined to a single directory means even malware like ransomware that would target all drives indiscriminantly can't affect my host system)