As mentioned by Geez, it looked like the "20 subscribed mods" which has been fixed with the last update. Thanks for the confirmation of the fix, closing.
Feb 4 2019
Jan 21 2019
Hello, please, try with the following, it will hold the reference to the object:
array<ref ClassType> arr = new array<ref ClassType>();
Is the code used within a single method? ct will hold the reference within the method but will be released when it leaves the method scope.
Jan 18 2019
We're unable to reproduce the issue, can you share the publisher logs? (common\DayZ Tools\Bin\Logs or from the tools launcher, view >> Tools Logs)
Jan 9 2019
The issue has been fixed, internally. It will be available with the next update of the main branch. (the related issue with Publisher has been fixed too)
Dec 21 2018
Thanks for the logs, and yes, here is fine ;)
Dec 19 2018
Hello, some adjustments have been made, can you, please, retest and let us know?
Dec 18 2018
The file limit has been fixed, it should appear in the game with the next update or the following one.
Thanks for the details. The file size limit should be 5MB and not 18kb. Can you share some logs?
Thanks for the report. Could you, please, share the PBO? (attach it or a link via PM works too)
Thanks! The update 1.0 introduced some limitations to the file writing capability of the scripts. The file count and individual file sizes are limited. While we could alter the file size limit (reasonably), it's very likely that the overall cap will remain the same.
The update 1.0 introduced some security measures to the file writing capability of the scripts and, as a result, creating directories is currently not allowed.
Dec 17 2018
Thanks for the report, it will be fixed today.
Dec 13 2018
Can you share the logs here? (attach them)
Dec 6 2018
Everything should be fixed on the next update, let me know if that's not the case.
Can you, please, try to run the game directly from the executable and check if there are logs? The game logs are in this folder: %userprofile%\AppData\Local\DayZ
Nov 29 2018
It will be fixed with the next update.
Can you, please, share the logs from the launcher? (they are located here: %userprofile%\AppData\Local\DayZ Launcher)
Nov 28 2018
Hello and thanks for the report.
Nov 22 2018
Hello, thanks for the report, we will take a look.
This is as designed, scrolling is only changing the row selection, the column selection is untouched unless clicked.
So I guess I can close this :)
We have fixed a number of issues over the past weeks, is your issue still happening? If so, please, describe the issue. (There are 20 pages of comments dealing with a variety of issues)
Nov 19 2018
The package was indeed updated, can you re-test and let me know?
Nov 27 2017
Oct 3 2017
Aug 23 2017
This was prior Work Drive, however, maybe the phrasing isn't ideal :)
Aug 16 2017
Jul 30 2017
Jun 28 2017
The tool isn't meant to extract mission files which are a little different, I will adjust the code to reflect this. Please, use BankRev.exe as described here for mission files:
Jun 23 2017
Could you, please, attach the following logs to the ticket?
...\steamapps\common\Arma 3 Tools\Logs\BankRev....rpt
...\steamapps\common\Arma 3 Tools\Logs\WorkDrive...rpt
May 12 2017
What branch did you try to download? Was it the RC or a password-free branch?
Mar 27 2017
I'm still unable to reproduce the issue. I've run several tests (with various setups on all the computers I have at my disposal) and no crash so far.
Mar 23 2017
I've tried to reproduce it but no luck so far. May I ask you for some data which could be used for an isolated repro?
Mar 19 2017
Thanks for the ping and confirmation :)
Nov 14 2016
Can you try the following version but this time by running it directly and upload the log somewhere?
Nov 7 2016
The following paths look weird, are they correct?
F:\_\proons\steam\steamapps\common\Arma 3 Tools\
Can you share the PBO or some converted texture files?
Nov 3 2016
Help has arrived :)
Sep 20 2016
It is now fixed :)
Sep 19 2016
Sep 8 2016
Hello, can you share the parameters you're using in Addon Builder?
Aug 11 2016
Aug 4 2016
Jul 28 2016
Jul 14 2016
This was solved with the update 0.984 of the tools :)
Jul 8 2016
Available here: http://tom4897.info/?attachment_id=3100
Jul 7 2016
Jul 1 2016
Sorry, I was sure I did communicate it here but I was wrong - So, I have this on my list since a tweet you sent ;)
Jun 29 2016
As mentioned in the documentation, cursorTarget and cursorObject don't really do the same job :)
Jun 28 2016
Jun 5 2016
This is already fixed and will be released soon, thanks for the report ;)
May 24 2016
Not really what is asked here but I will add a new startup script running in SQF which you could use as an entry point to define your function in SQF. Surely not as elegant as the CfgFunctions but I believe it's a decent solution.
May 10 2016
Good to read :)
The error of the diagnostic script is strange. However, for what I can see, it seems something went wrong at the installation level. Could you please try to verify the integrity of the local file and start it again from Steam?
Also, try to move/delete the file called settings.ini (in the root directory of the tools).
This has been fixed, thanks for the report.
This issue is usually provoked by conflict (or other issues) with run-time libraries, therefore, reinstalling (repairing) them could solve the issue.
Location: ...\steamapps\common\Arma 3 Tools\_CommonRedist\vcredist
Go in each folder and reinstall them.
We would need some more information and data. I would say the RPT from a kicked player and the server would be enough to serve as start point.
I assume you are using the main branch of the game but what's about the tools, development or main branch?
Edit: What software are you using to pack your PBOs?
Could you please, precise what branch of the game and the tools you are using?
I was almost sure I replied to your topic on the forum, now I did :)
Nice to read you solved your issue.
Regarding the fact that DevP doesn't generate the A3 dir and its content, it's perfectly normal because FuturaToP is responsible of that ;)
The provided link is restricted. Please add a comment marked as private containing the link to your files if you want to keep them secret.
It's because the logs are not in Publisher folder but in the Arma 3 Tools logs which can be found in the steamapps\common\Arma 3 Tools\Logs.
Please, join both logs, arma3publisher.rpt and arma3publisher.steam.rpt.
Closed as duplicate.
In this context, the strings should be part of the stringtable.xml which is used for such situation and the string localization.
The following page explains all you need about this process:
Could you please, provide the logs generated by Addon Builder? They are in Arma 3 Tools\Logs.
The problem is from Binarize which crashes during the process. Ideally, to be help you, we would need the data. Can you share them?
Could you please, provide the full path to the installation of Arma 3 Samples?
I already have seen this error years ago (~ 2008). If I recall correctly, there are two potential causes:
- The most common is the usage of the public key to sign an addon but in our case, you can only select a private key.
- A bit more tricky, 8009000b matches a Windows error, related to the account management which could corrupt the private key. What you could test would be to activate the Administrator Account, log into this account, create your signature and try to sign a file from this account and yours, to determine if its about the signature or the private key.
To enable the local administrator account, open a CMD as administrator and type:
net user administrator /active:yes
To disable it, replace yes by no.
Thanks for the feedback!
Hi, we were able to locate what caused the issue. The issue will be soon gone :)
Glad you've managed to resolve your issue, now closing :)
Note: When you create a new ticket, please, try to add as much information as possible, including the logs.
CPBO is an old non-maintained community tool. Can you do a test with PBO packed via Addon Builder?
We've tested the data contained into newpbosign.zip and for us both old and new worked as expected.
What are you using to pack your PBOs?
I see, fact is the signature tools which should be used for Arma 3 are in Arma 3 Tools.
The ones provided by BI Tools 2+ are not supposed to be compatible with Arma 3.
I've been unable to reproduce the issue. Something might be wrong with the authority.
Can you test with a new authority?
A copy of the given PBO is indeed needed to make some tests ;)
Have you tried the solution suggested by deanosbeano, did it help?
To be honest, I was not expecting the interface to be used with so many files. I will "try" (because such tests takes time) wider tests and prototypes.
The previous iteration of the UI didn't have the checklist this shouldn't impact (or very slightly).
I ran some tests between the current and the previous version of ImageToPAA and the results show a difference but not a big one.
53 TGA files (359MB) have been used for the tests. Group A is the current version whereas the group B is the previous. The results are expressed in elapsed milliseconds between the beginning and the end of the process (including UI updates etc...).
A - Pass 1, Milliseconds: 105 965
A - Pass 2, Milliseconds: 105 769
B - Pass 1, Milliseconds: 105 756
B - Pass 2, Milliseconds: 105 483
Can you precise the file size and dimensions of the source files?
Regarding the displayed time of the process, I'm very surprised because it's basic operation exitTime - startTime.
For the rest, I will make some tests and see if I can improve the current UI.
Unfortunately, the garage is not written as dynamically as the Arsenal, consequence is: it's not currently possible.
No news from the reporter, so I assume the issue is history :)
Feel free to open a new ticket if you experience this issue again.
Wizard has prepared a version that could fix your issue, could you give it a try?
It's the attached file (Arma3Tools.exe_5666.zip), extract its content in the install directory of Arma 3 Tools (...\steamapps\common\Arma 3 Tools)
Sorry, I should have update this ticket. We released another version with additional changes. It's currently in the development branch of the tools. I hope it should fix your issue.
Can you provide a screenshot of your entire screen when it happens?
In addition, what resolution are you using?
Thanks for the feedback :)