Closed compicat closed 1 month ago
Looks like the latest merges might have broken it. I'll have a look in a couple hours.
Thank you.
Looks fine on my end. Please make sure your repo is up to date by running git pull
first.
If the issue persists, please attach your logs.
I m trying use ntsync5 by putting false to others (esync, fsync, winesync etc.), can this be related?
Here are the logs:
@compicat Same here. Maybe we have something else enabled that Tk does not?
@Tk-Glitch Sorry.. forgot to paste the customization.cfg file in case of any obvious mistakes. customization.zip
@SveSop Hi, i finally managed to compile Ntsync5 wine. I was using default-tkg local before. Now, i ve dchoosen staging instead of default-tkg esync off, fsync off, childwindow off, fastsync off, proton fs on and of course ntsync5 on. It compiled clean-staging wine-tkg-git. Ntsync5 is working flawless with patched CachyOS kernel and after installing necessary aur packages on my system. I hope it helps.
Fails for me.
childwindow-proton.patch -- ( Applied child window for vk patch )
patching file dlls/win32u/ntuser_private.h
patching file dlls/win32u/vulkan.c
patching file dlls/win32u/window.c
Hunk #1 succeeded at 462 with fuzz 1 (offset -1 lines).
Hunk #2 FAILED at 1762.
1 out of 2 hunks FAILED -- saving rejects to file dlls/win32u/window.c.rej
Still fails for me as well unfortunately:
-> cherry picking...
-> Hotfixing...
-> Applying CSMT-toggle.patch
-> Applying wine-staging patches using staging/patchinstall.py...
Staging overrides used, if any:
-> Applying ffxiv-launcher-workaround.patch
-> Applying childwindow-proton.patch
==> ERROR: Patch application has failed. The error was logged to /home/al/rep/wine-tkg-git/wine-tkg-git/prepare.log for your convenience.
==> ERROR: A failure occurred in prepare().
Aborting...
-> Removed BIG_UGLY_FROGMINER - Ribbit
-> Removed Proton-tkg token - Valve Ribbit
-> exit cleanup done
Hi, Thanks in advance for your help.
childwindow-proton.patch is not being applied during compile. Even if i choose that patch "false" at customization, it is still giving same error.