However, sometimes it does work, specifically when I feed it a command option. I don't think it matters what I feed it, but for some reason, when I give the binary "--help", it starts up and runs just fine. But only sometimes. Typically this works the first 2 or 3 times, but then after that, it won't work until I've restarted my computer.
As you can see:
Code: Select all
$> ./DaggerfallUnity.x86_64 --help
Set current directory to /home/dyskos/Programs/DFUnity
Found path: /home/dyskos/Programs/DFUnity/DaggerfallUnity.x86_64 # works fine, I close the program
$> ./DaggerfallUnity.x86_64
Set current directory to /home/dyskos/Programs/DFUnity
Found path: /home/dyskos/Programs/DFUnity/DaggerfallUnity.x86_64
Aborted (core dumped) # DF Unity crashes
$> ./DaggerfallUnity.x86_64 --help
Set current directory to /home/dyskos/Programs/DFUnity
Found path: /home/dyskos/Programs/DFUnity/DaggerfallUnity.x86_64 # again, works fine, I close the program
$>
I was unsure what the issue could be; I wanted to know if there were some libraries that Unity games need that perhaps aren't installed?
Some more info about my machine:
Dell Optiplex 7010 DT (no modifications, except an additional wireless NIC)
https://www.hardware-corner.net/desktop ... x-7010-DT/
Endeavor OS (Arch-based) 64-bit Linux, 5.10 Kernel
The file system is Btrfs, if that matters. This is the first time I've used it so even that is a factor I would consider.
Using Budgie Desktop on top of X window system.
Logs attached.