DaggerfallUnity.x86_64 will no longer launch

[striker]

Hi,

Specs:
Fedora 24
Haswell i7-4600U

Issue:
- I launched the game through DaggerfallUnity.x86_64 after downloading the stable Linux version (*linux_universal-40-DaggerfallUnity.zip) and the DaggerfallGameFiles.zip. The game ran fine, but was slow to respond to mouse movements. I exited the game and then re-launched it, hoping to get back to the settings dialog so that I could disable view distance, but the application simply crashes. I have removed the DaggerfallUnity files and re-extracted freshly from the .zip with no change. Here is what I see in terminal:

Code: Select all

$ ./DaggerfallUnity.x86_64 
Set current directory to /home/striker/NotBackedUp/DaggerfallWorkshop/Unity
Found path: /home/striker/NotBackedUp/DaggerfallWorkshop/Unity/DaggerfallUnity.x86_64
Mono path[0] = '/home/striker/NotBackedUp/DaggerfallWorkshop/Unity/DaggerfallUnity_Data/Managed'
Mono path[1] = '/home/striker/NotBackedUp/DaggerfallWorkshop/Unity/DaggerfallUnity_Data/Mono'
Mono config path = '/home/striker/NotBackedUp/DaggerfallWorkshop/Unity/DaggerfallUnity_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 4 screens
displaymanager screen (0)(eDP1): 1920 x 1080
displaymanager screen (1)(DP2-1): 1920 x 1080
displaymanager screen (2)(DP2-2): 1920 x 1080
Using libudev for joystick management


Importing game controller configs
$

Anyone have any ideas? Is there a separate location other than a subfolder of the Unity files where the config is stored that tells Unity where the Game files are?

Striker

[striker]

It's worth noting that I changed the game resolution to 1600x900 Windowed, which effectively did not make the game 1600x900, but instead simply gave it borders (around 1912x1076 resolution or so). This can be seen in part of the trace information:

Code: Select all

22488 13:40:04.896222 recvmsg(7, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1\0\31\0\3\0\0\0 \0\0\0\1\0\1\1\377\377\377\377\0\0\0\0\0\1\2\0\"\0\0\0003\300\372\0\0\0\0\0\0\0\0\0\1\30\32\0\0\0\0\0\332\0\0\0\0\0\0\0\200\0268\4\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 76 <0.000006>
22488 13:40:04.896247 recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000005>
22488 13:40:04.896262 recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000004>
22488 13:40:04.896275 recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000005>
22488 13:40:04.896290 write(6, "Desktop is 5760 x 1080 @ 60 Hz\n", 31) = 31 <0.000006>
22488 13:40:04.896306 write(6, "Invalid resolution: 1912 x 0\n", 29) = 29 <0.000005>
22488 13:40:04.896322 poll([{fd=7, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=7, revents=POLLOUT}]) <0.000005>
22488 13:40:04.896336 writev(7, [{iov_base="<\25\2\0\0\0\240\6+\0\1\0", iov_len=12}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 12 <0.000007>
22488 13:40:04.896355 poll([{fd=7, events=POLLIN}], 1, -1) = 1 ([{fd=7, revents=POLLIN}]) <0.000012>
22488 13:40:04.896383 recvmsg(7, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1\1\34\0\0\0\0\0\217\0\340\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32 <0.000005>
22488 13:40:04.896403 recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000005>
22488 13:40:04.896417 recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000004>
22488 13:40:04.896573 brk(NULL)         = 0x2795000 <0.000006>
22488 13:40:04.896587 brk(NULL)         = 0x2795000 <0.000005>
22488 13:40:04.896601 brk(0x267b000)    = 0x267b000 <0.000067>
22488 13:40:04.896678 brk(NULL)         = 0x267b000 <0.000005>
22488 13:40:04.896692 close(8)          = 0 <0.000015>
22488 13:40:04.896726 shutdown(7, SHUT_RDWR) = 0 <0.000007>
22488 13:40:04.896744 close(7)          = 0 <0.000009>
22488 13:40:04.896775 write(6, "Failed to initialize ScreenManager\n", 35) = 35 <0.000012>

So, I am confident that if I can find the location of the configuration that DF Unity stores its resolution information in and wipe that out that the game would then launch.

[Jay_H]

Have you gone to /home/USERNAME/.config/unity3d/Daggerfall Workshop/Daggerfall Unity to the file settings.ini?

[Interkarma]

Just further to Jay's comment above, if you delete settings.ini file from your persistent data path, it will be recreated from default settings and kick off setup helper again.

The included manual has these data paths on page 3 for each platform. The path itself is a Unity concept: Application.persistentDataPath.