I've a new error in my server report since the arma 1.66 debacle and it's still there since the hotfix. This is on Tanoa:

23:01:47 Error in expression <thread_threadAdjust.sqf"

if (ExileSystemThreadDelays isEqualTo []) th>
23:01:47   Error position: <ExileSystemThreadDelays isEqualTo []) th>
23:01:47   Error Undefined variable in expression: exilesystemthreaddelays
23:01:47 File exile_client\code\ExileClient_system_thread_threadAdjust.sqf, line 12
23:01:47 Error in expression <hreadID = param [4, false];
_threadId = ExileSystemThreadID;
23:01:47   Error position: <ExileSystemThreadID;
23:01:47   Error Undefined variable in expression: exilesystemthreadid
23:01:47 File exile_client\code\ExileClient_system_thread_addTask.sqf, line 18

Is anyone else seeing this error?


Share this post

Link to post
Share on other sites

5 answers to this question

  • 1

I'm part of @Omen community. I've figured out the issue. In our init.sqf, I call ExecVM to a custom init.sqf. That custom init then calls another ExecVm, which executes code to setup a scheduled task in the Exile threading system. Like this:

[60, ExileServer_ZSTools_system_createZSToolsAccount, [], true] call ExileServer_system_thread_addTask;

It almost seems like a timing issue of some sort, because I know for sure that this worked before, but now this is failing, and the resulting scheduled task is not occurring.

I added this to my custom init to make sure the Exile server is ready and the errors stopped:

diag_log "ZSTools Core INIT Start";
waitUntil {!isNil {PublicServerIsLoaded}};
waitUntil {PublicServerIsLoaded};
diag_log "ZSTools Core INIT Continue";


Edited by ynpMOOSE
1 person likes this

Share this post

Link to post
Share on other sites
  • 0

Is nobody else seeing this in their server reports? It's happening on both my servers; altis and tanoa...

Share this post

Link to post
Share on other sites
  • 0

Finally, someone else and I thought it was just me... ☺ 

I have searched on the keywords in the error across both my missions files and addons files and it's not referred to at all so, I'm at a loss where this is coming from. 

Unless everyone has this error and it's just come to light from the vanilla exile code since the arma update... 

Would be great if others could check whether they're seeing this error too.. 

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.