The path problem may be a bit deeper here when you use linux launcher with “use custom wine” pointing to system wine installation:
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_evelocalization.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_geo2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_geo2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_pyfsd.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_pyfsd.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_spacemouse.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_spacemouse.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_audio2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_audio2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_videoplayer.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_videoplayer.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_destiny.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_destiny.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_eveplanetresources.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
As you may imagine, those files are not present in /usr/lib -
/wineenv/drive_c/tq/bin64/spacemouse.pyd
/wineenv/drive_c/tq/bin64/_spacemouse.dll
/wineenv/drive_c/sisi/bin64/spacemouse.pyd
/wineenv/drive_c/sisi/bin64/_spacemouse.dll
Fortunately, the patch by @Renard_DuGaulle should solve this as well since it all looks to be related to loading dlls from relative paths.