• Announcements

    • Flosstradamus

      Official Discord   03/15/17

      https://discord.gg/FMkqWpF Click the link above and join our Official Discord!  Chat with developers and get quicker support!
    • Vishpala

      New XM8 Discord Bot   05/15/17

      Our new XM8 Discord Bot will send you notifications about events happening in-game, even if you are not online!  Read about it on the Devblog:  
    • WolfkillArcadia

      1.0.4 "Pineapple" Release   03/08/18

      Inmates! We have launched 1.0.4 update for Exile. You can read about the release here:   
    • WolfkillArcadia

      Exile Server 1.0.4a hotfix out!   03/09/18

      Server owners! We pushed out 1.0.4a hotfix for Exile server. You will need to merge/replace the following files:
      ExileServer_object_lock_network_grindNotificationRequest.sqf
      ExileServer_object_construction_network_*.sqf

      Just download the server files from the downloads section. 

gnif

Member
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About gnif

  • Rank
    Bambi
  1. It seems there is a bug in the Linux build of `xm8.so` with locating the `ExileXM8Key.cfg` on the disk. Using `strace` it can be seen that `xm.so` is attempting to open the file using a relative path, which is incorrect as the current working directory is `/home/steam/arma3`. Clearly the file exists as `stat` succeeds. steam@arma:~$ strace ./start.sh 2>&1 | grep ExileXM8Key stat64("/home/steam/arma3/@ExileServer/ExileXM8Key.cfg", {st_mode=S_IFREG|0644, st_size=81, ...}) = 0 stat64("/home/steam/arma3/@ExileServer/ExileXM8Key.cfg", {st_mode=S_IFREG|0644, st_size=81, ...}) = 0 open("ExileXM8Key.cfg", O_RDONLY) = -1 ENOENT (No such file or directory) Please advise. Edit: I worked around this bug by sym-linking the file in the arma3 directory: ln -s \@ExileServer/ExileXM8Key.cfg ./ While I am at it, can I please request that xm.so be rebuilt against libcrypto 1.1 as 1.0 is quite old and most modern distributions have dropped support for it.
  2. You do not need to have access to their project to make changes, fork it.
  3. I had the same problem and just figured it out, it is Linux specific due to case sensitivity. The mod name doesn't matter, but the directory inside the mod needs to be renamed to lower case from "Addons" to "addons"
  4. I appreciate the efforts the developers here have put in to make ExAd 1.0.4 compatible, but what I do not understand is the following: Git is not in use anymore making it next to impossible for other devs to contribute fixes. You renamed all files to lower-case, this breaks this mod entirely under case sensitive operating systems (Linux). Please "fork" the original project on GitHub and apply your changes to it there, and please revert the rename of the files to make this operate again under Linux.