Chow do you own this?
NAll of those environment variables and a custom build of Proton? Youβre probably going to need to ask whomever told you all of those
NThatβs the longest configuration I have ever seen in any log presented here
NFor example, youβre using
When the option to disable fsync is already in Heroic
When the option to disable fsync is already in Heroic
NThen you have disabled DXVK, but I donβt know if that is for a specific purpose
Whmm i will try and remove that line and see if that works. The env option was mentioned in a cachyos forum post
WYea that doesn't help, the game icon is in system tray, but no window pops up, like it really can't find a video driver but there is. Also, sure it says it in log but using nvidia. I have tried propietary driver and open driver
NYou shouldnβt be installing DXVK via Winetricks. Setting your windows version to winxp by installing that via Winetricks isnβt ideal either
NPretty much all of the environment variables and the wrapper options look like theyβre hodgepodge copied
NAlso, you shouldnβt be using the use dedicated GPU option either
WI was playing around with the GPU option. Ok recreated a new prefix to clean slate. I am noticing when trying to use system wine i get "(01:24:22) ERROR: [Backend]: Couldn't find all library folders of Wine Default - wine-9.0 (Staging)!" Is there a way to find out which library it is looking for?
Cagain, how do you own this game? it's not free to play
WTechnically it is, but there is an initial cost(and yes I did pay for base and upgrades)
Cthen that isn't free to play, but carry on
Cplease post a new log
WRis your kernel module enabled too?
RPROTON_USE_NTSYNC=1 is all you need when it comes to ntsyncRbut from my testing the cachyos build is really unstable, many games just don't work
Ryou can verify that by checking if
/dev/ntsync existsWβ― ls /dev/ntsync
crw-r--r-- 10,123 root 8 Jan 04:39 ο /dev/ntsync
crw-r--r-- 10,123 root 8 Jan 04:39 ο /dev/ntsync
WIf i directly launch the eso64.exe, which is the actual game and not launcher it works.
Rlike I said, the proton version is really unstable
Rmany things will just refuse to work
WYea, atleast the launcher anyway and even plain wine and wine-staging is an issue
NYou need to enable DXVK and VKD3D in settings
WI mean if it is not complaining about vkd3d and dxvk, other wine versions will go to like stack overflow and starting debugger and that is it
Ddxvk allows games that use directx 8-11 to function vkd3d does the same but with dx12.. if you want to play games, generally you need this enabled as basically all pc games require direct x.
Without it you are using the limited wine3d which supports directx via open gl.. which is slow and buggy.
Without it you are using the limited wine3d which supports directx via open gl.. which is slow and buggy.
Dgranted, looks like you are using some custom proton? i suspect it has dxvk and vkd3d enabled by default if so
Dalso why custom proton (honestly why all this random custom stuff? is there a specific reason for it?)
Nthinking about it now, you're probably right that it's enabled by default
Nhowever, this part in the log gives me pause and makes me think that is in fact complaining about dxvk and vkd3d
Nntsync I'm guessing
Dah makes sense abuot the libvkd3d stuff you mention.
Dhonestly maybe worth it to just run stock proton-ge
Dim not sold that there's gonna be a big perf bump with it esp in a game that's pretty old on a system like that
R@loathingKernel this is something you may want to see
AThanks for the ping, which version is this @ndowens?
WI think it's 9.0-20250102. But just seen there is one newer I can try later today
AThis build is meant to be used with the SteamLinuxRuntime enabled, you have it disabled. The second error that happens when using its wine directly is expected, the one that it can't find libvkd3d-shader.dll, because you are skipping the proton script.
Roh proton here was added as Custom Wine
RI completely missed it
WAh. If I use proton instead of wine portion, it gives using fast sync but no error no launch of gui. I will retry using SRL
AAlso, don't bother with ntsync in that proton, it is borked badly in subtle ways. We never added it in a regular release, I just wanted to test ntsync with slr.
WGotcha. Mostly wanted to mess with it and use and maybe overtime it gets better
WGuess I will just go back to fsync then
AI cannot make it better myself, it is beyond my understanding of wine internals. But there are a few people looking at it with me, maybe it does get better, maybe it doesn't.
WWell by it gets better, I mean the developer of ntsync, if still maintained that is
AIt is, and that's my hope too
Whmm I am now getting i386-linux-gnu-capsule-capture-libs: warning: Dependencies of /usr/lib32/dri/nouveau_drv_video.so not found, ignoring: Missing dependencies: Could not find "libLLVM.so.18.1" in LD_LIBRARY_PATH "", ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib no mater which proton i use. I do have libLLVM.so.18.1 in /usr/lib
