Repository navigation
Conversation
Please ignore this right now, I've just attempted this again, but with these 2 programs: All of a sudden, these 2 apps are hard freezing my Steam Deck due to high memory usage. PackageInstaller and Body Shop open just fine. I believe this should be altered as this: CSBin\PackageInstaller.exe can be connected to it as well |
Are you saying they don't work with this PR but did before? |
Apologies, it's I think a random bug with Protontricks when I'm using the files from your DXVK build instead of the ones that come with Proton 11, since I have no issues using protontricks-launch on those 2 apps with the Proton 11 DXVK, but with this build, the apps become unresponsive after appearing for a second, or they just crash to desktop, again using protontricks-launch. They do launch fine in Steam however on both builds, I think it's just an unintentional thing of your and my DXVK builds either being intended for windows or something else and Protontricks not liking it? I presume once the config.cpp is merged into the main repo, and DXVK is included with those changes into Proton, there won't be any issues at all. The only change I will now suggest as on the issue page for PackageInstaller from my findings on Content Manager is doing this: I've just tested my own build and that piece of code works in my build :) |
|
How are you using Protontricks with these files? I'm not sure i understand as i haven't used it much. |
What I did was go to Steam/steamapps/common/Proton 11.0/files/lib/wine/dxvk and replaced the files in the i386 and x86_64 folder (except for the vr dll) with the ones from both your build and my build. Both my and your builds had the same issue with Protontricks, but I presume that's because replacing the original dlls broke some links possibly since Proton I think gets built with all dependencies available? That's my guess anyway, but the fact that it works on Steam regardless, makes me think that once this config.cpp gets merged, and DXVK with these changes gets added into the next Proton Experimental version, that the issue won't occur. Putting this in my dxvk build's config.cpp fixed the issue of Content Manager (US Version's named exe) not launching if using the US version of it. #6029 (comment)
Game executables:
I'll attempt to do a config where Sims 2*/Sims2*/TS2* are added instead of all of the exe names. (Except for PackageInstaller, and the Stories titles.) |
|
The If we remove the other entries that regex would boil down to just See this example on regex101.com. The green highlight is a match |
|
I've attempted to fix this in my build by doing this: All exes starting with TS2 or Sims2 started up correctly with this, but any program starting with The Sims 2/The Sims 2 Content Manager in it (the Content Manager exes with different languages including UK English) would not start up and instead start using too much memory than is needed as mentioned in the issue page. So I attempted to fix this by including a wildcard before "Sims 2" but this, for me, resulted in kernelbase crashing right after Xalia displaying it's log in the proton log, so I fixed that by doing the This fixed "The Sims 2 Content Manager.exe" not opening under DXVK, and then I tested two of the other language versions of Content Manager, and tested the Spanish and Czechia versions under their exe names, and I can confirm that both exe names worked and DXVK was able to load the built-in config for them. Successful launch of The Sims 2 Content Manager under DXVK.zip Only one I can't exactly fix atm is the Taiwan version of Content Manager, which shows up as this in English: It's supposed to be this: The downloads from SimFileShare are not the original "CM_XX.zip" files btw, and I'm pretty certain the original downloads did contain exes for every CM version. (** being the language code, TW for Taiwan or CN for China) SOme of the SimFileShare exe names in other languages are not the original names either, but most of them should work as from my own findings, they should have "Sims 2" in the name. The above config that has |
|
@WinterSnowfall came up with this latest eyesore. |
I didn't even realise, but PackageInstaller is located in TSBin for all 3 Sims Stories games! Sorry, I only just re-installed them and noticed that they moved PackageInstaller out of CSBin since that folder is gone on those 3 games for some reason... Body Shop is gone from the stories games as well. This should fix that for the Stories games and then that should be everything done to my knowledge. I just confirmed on my build that the changes in this commit are indeed working, all of the below are working: Content Manager (TSContentManager, and all different language versions of it except for Taiwan, China, and Korea due to different encoding, they can simply be renamed.) |
Should just be |
Closes #6029
d3d9.memoryTrackTest = Trueis likely the only interesting part here, but adding to the current pile instead of making a whole separate entry.Needs a test that it works correctly and also doesn't break the other exe's
Edit: The above only talks about the original Package Installer addition. A catch all for exe's with "Sims 2" in the name has also been added along with TS2ContentManager.