Cloud22

[Done] ExtDb3 Compatibility with Exile

835 posts in this topic

On 5.3.2017 at 10:56 PM, Torndeco said:

 


9:UTC_TIME

 

works, thx! :)

next thing is for every territory while loading from DB:

20:18:57 Error in expression <riable ["ExileTerritoryMaintenanceDue", _maintenancePeriodDueDate select 1, true>
20:18:57   Error position: <_maintenancePeriodDueDate select 1, true>
20:18:57   Error Undefined variable in expression: _maintenanceperiodduedate
20:18:57 File exile_server\overrides_xdb3\ExileServer_system_territory_maintenance_recalculateDueDate.sqf, line 18
  
  
[20:18:57:207156 +01:00] [Thread 4068] extDB3: Input from Server: 0:SQL:loadTerritory:242
[20:18:57:207165 +01:00] [Thread 4068] extDB3: SQL_CUSTOM: Trace: UniqueID: 1 Input: loadTerritory:242
[20:18:57:207667 +01:00] [Thread 4068] extDB3: SQL_CUSTOM: Trace: Result: [1,[[242,"76561198065151581","Grabesruh",12542,643555,9481,555664,0,070038,75,000000,5,"exile_assets\texture\flag\flag_misc_nuclear_co.paa",0,"",[2017,6,27,18,33,40],["76561198065151581","76561198063660383","76561197971069962"],["76561198065151581","76561198063660383","76561197971069962"],"",103]]]
[20:18:57:207680 +01:00] [Thread 4068] extDB3: Output to Server: [1,[[242,"76561198065151581","Grabesruh",12542,643555,9481,555664,0,070038,75,000000,5,"exile_assets\texture\flag\flag_misc_nuclear_co.paa",0,"",[2017,6,27,18,33,40],["76561198065151581","76561198063660383","76561197971069962"],["76561198065151581","76561198063660383","76561197971069962"],"",103]]]
[20:18:57:207958 +01:00] [Thread 4068] extDB3: Input from Server: 9:LOCAL_TIME
[20:18:57:208101 +01:00] [Thread 4068] extDB3: Output to Server: [1,[2017,03,06,20,18,57]]
[20:18:57:208154 +01:00] [Thread 4068] extDB3: Input from Server: 9:DATEADD:5:[10,0,0,0]
[20:18:57:208165 +01:00] [Thread 4068] extDB3: Output to Server: 

:( i dont get it, it seems right so far. or is it perhaps because: "Note: Years/Months not supported yet "  with LOCAL_TIME?

its called through "_currentTimestamp = call ExileServer_util_time_currentTime;" in this script...

i really wanna get the stuff working without bothering you guys, but this is way above my knowledge yet... but i am learning! :)

---

good thing is, we found a bugfix for the corrupt hitpoints in db, so no stress with getting extdb3 working... we just disabled all the hitpoints with an empty array...

 

Edited by yesyesjo

Share this post


Link to post
Share on other sites
Advertisement

@yesyesjo 
Even if your hitpoints were getting sent to database as empty array.
It shouldn't be causing your script error, where it tries to call compile an incomplete array (note it wasn't a empty array).
Please PM the debug logs i suggested before....
That way i can see exactly what is happening / replicate + fix it if its a bug with extDB2/3. 

-------------------
Your other error is caused by the database returning 5 for your last maintance paid date, when it should been an arma date array.
Double check your [loadTerritory] in your exile.ini is correct.
Then check the data in your database the last maintance paid date for territory table is correct aswell. (Territory ID = 242)
Otherwise plz pm your exile.ini and snapshot of your territory table so i can try to replicate the issue thanks

-----------------
https://bitbucket.org/torndeco/extdb3/wiki/extDB3 - System
The note for LOCAL_TIME / UTC_TIME for years/months, is in regards adding / offset the time

For example

"extDB3" callExtension "9:LOCAL_TIME:[0,0,30,24,60,60]"

is
LOCAL_TIME + [0 weeks, 0 days, 30 hours, 60 minutes, 60 seconds]
To add month or year offset you need to manually work this out in SQF in weeks/days etc.


--------------
I also recommend people to fav that github repo. That way if there are any changes etc, you will get notified etc
 

  • Like 2

Share this post


Link to post
Share on other sites

Will we need to change the db over to this version after the Arma update or later down the line?  Not looking forward to doing it if we have too, it looks very complicated :(

Share this post


Link to post
Share on other sites
1 hour ago, Razor77 said:

Will we need to change the db over to this version after the Arma update or later down the line?  Not looking forward to doing it if we have too, it looks very complicated :(

Nope, this thread is for a 3rd party addon to be used as an alternative.

  • Like 1

Share this post


Link to post
Share on other sites

folks, we just startet our dev server in 64bit with 12gb RAM... and it unlocked... :D and thx to @Torndeco extdb3 is working great!

Type: Public
Build: Stable
Version: 1.68.140613

Allocator: C:\Users\Administrator\Desktop\Taunus_PVP_RC_DEV\taunus_pvp_dev\Dll\tbb4malloc_bi_x64.dll
PhysMem: 64 GiB, VirtMem : 131072 GiB, AvailPhys : 57 GiB, AvailVirt : 131072 GiB, AvailPage : 66 GiB

---

now the last thing (infistar):

20:27:59 Call extension 'ARMA_LOG' could not be found

20:10:42 Call extension 'ARMA_LOAD' could not be found

---

and we all got our 64bit exile server? hehe :D

i am so excited like a little boy...

---

edit: the ExileLootDrop DLL need an update too... :(

 

 

Edited by yesyesjo

Share this post


Link to post
Share on other sites

@Razor77 Its not as bad as it looks

1) You read the first post
2) ExileServer Overrides are at https://github.com/Cloudhax23/Exile (don't forget to fav repo or bm to get any updates/optimizations etc)
3) Updated sql_custom/exile.ini is at https://github.com/Cloudhax23/Exile/blob/master/exile.ini
4) Grab the latest version of @extDB3 at https://bitbucket.org/torndeco/extdb3/downloads/

The rest of the posts were just errors etc, that has been fixed now. (you can ignore them)
Anyway thanks to @yesyesjo for help debugging a locale issue with number formatting and few other minor bugs.

  • Like 5

Share this post


Link to post
Share on other sites
1 hour ago, Torndeco said:

@Razor77 Its not as bad as it looks

1) You read the first post
2) ExileServer Overrides are at https://github.com/Cloudhax23/Exile (don't forget to fav repo or bm to get any updates/optimizations etc)
3) Updated sql_custom/exile.ini is at https://github.com/Cloudhax23/Exile/blob/master/exile.ini
4) Grab the latest version of @extDB3 at https://bitbucket.org/torndeco/extdb3/downloads/

The rest of the posts were just errors etc, that has been fixed now. (you can ignore them)
Anyway thanks to @yesyesjo for help debugging a locale issue with number formatting and few other minor bugs.

Thanks, I will give it ago when the update arrives.  Thanks again

  • Like 2

Share this post


Link to post
Share on other sites
Advertisement

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.