This issue has been fixed (dev branch only for the moment).
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
May 10 2016
Could you, please, open a new ticket regarding this issue?
(I'm closing this one)
Have you started Arma 3 Tools from Steam? When ImageToPAA fails on every pictures, it usually means that the installation is incorrect.
Glad to read it, status changed :)
Thanks for the feedback.
It seems to be legit as TexView is less strict than ImageToPAA. Is it possible to get the given file or perhaps a similar file saved with Gimp?
Hello,
What are the dimensions of the JPG file? Also, what software did you used to save this JPG?
Ticket closed.
I see no issue here. Most likely an issue on your model because the sample of helicopter works fine, no error on the proxy.
Without additional information, I cannot tell you more.
From my side, everything works well (see attached screen). Are you using mods?
Could you, please, update your buldozer installation?
dev.bat -update
Is your issue solved?
Also, I invite you to consult the manual of Buldozer, it should provide you more information about its installation and update process: https://community.bistudio.com/wiki/Buldozer_Manual
Hello,
Glad you found an alternative. For what I was speaking about, DSTools has been released on the dev branch of the tools.
https://twitter.com/tom_48_97/status/613710150818492416
http://forums.bistudio.com/showthread.php?179347-Tools-Development-Branch-Changelog&p=2960368#post2960368
Ps: the command line will come later.
Hello,
This is already planned. The interface should be similar to the new ImageToPAA ;)
Hello,
I think you need to refresh your local unpacked data because the objects and the map must be binarized with the same version of binarize.
Hello,
The randomization system has been changed in the dev branch (version 131267).
It doesn't use any public variable and should be executed only from the machine where it's local to.
Feel free to provide feedback :)
As discussed with EricJ, it seems that the issue is caused by the internet connection because his logs contain a log of connection failures and disconnections. In addition, he succeeded to perform an upload from another internet connection, which reinforce the suspicion.
Therefore, I assume this ticket can be marked as "resolved" and later on, closed.
Like we discussed, a test on a config entry shouldn't be case sensitive, using toLower should be enough to bypass this issue.
Here we go! Thanks for the reminder, now closed :)
Hello,
This should be fixed soon :)
Status changed because the issue is still present (less but still) and being investigated.
If your version of Buldozer is prior (1.46 and previous) to the fix, yes.
For the records, Buldozer is a "sub program" of Arma 3:
https://community.bistudio.com/wiki/Buldozer_Manual#What.27s_Buldozer
Are you sure you use the development branch*? Fact is this fix is not yet in the main branch, only on the development branch.
- When the development branch is used, a blue ribbon with the label dev is displayed on the top left corner of the launcher.
Sorry, I meant the development branch of the game. This issue has been fixed on the game side, not the tools.
This issue has been fixed in the development branch (1.47.131055). Please, feel free to comment if you experience it again.
It's planned to release some sources as we did for the Helicopters DLC. Artists should work on that soon ;)
Thanks for the feedback :)
Hello, about the old exe, I must say no. But, what kind of problem, can you precise?
Regarding the tools used, I'm not sure to understand.
Hello,
Could you, please, try with the new version of Binarize?
P Drive has been reworked from scratch more than a year ago to bypass the UAC. If Arma 3 Tools is ran as a normal user, then, the drive P will be mounted for both, users and administrators.
Note: Regarding the drive P and how it works from the Arma 3 Tools Launcher, nothing has changed since almost a year.
Fixed, it should be in dev branch soon(TM) :)
The short thread was initially added because of the holding frame which is on the right side, therefore, as designed.
Hello,
The fix should be in the dev branch very soon ;)
Thanks for reporting.
Thanks for the ticket ;)
The new version of Terrain Builder has been released today (only on the dev branch) ;)
http://forums.bistudio.com/showthread.php?179347-Tools-Development-Branch-Changelog&p=2956525#post2956525
As I told you, FSMEditor and the requested config have been released in latest update of the tools :)
Like I wrote here (see link), the config you're asking for should be part of the first release of FSMEditor for Arma 3 tools, just a matter of time.
Then, ticket solved! Thanks for your feedback and tests.
Here a link to the updated GUI:
http://tom4897.info/depot/tools/bi/WAVToWSS.0.81.1.0.archive.zip
Just extract the content of the archive in Arma 3 tools\Audio
WAVToWSS update will be included in the next development update, soon™ ;)
Fixed in a previous update.
The icons have been changed.
Currently available in the dev branch ;)
Glad to read that, now switching to resolved :)
We made quite a lot of modifications, do you still experience this issue?
Regarding the solution you've mentioned, it's something like the 3rd :)
Hello, with the update 0.82, Arma3Tools.exe display should be better for you (even if it's not scaled), could you have a look? Thanks.
Brief explanation: When something is run from Steam, Steam will track and consider every sub-process as part of the launched application. This means that until every process are closed, Steam will still "think" the original app as "Running".
Ticket marked as resolved then ;)
Fixed in a previous update.
Fixed in development version (or will be fixed soon).
Indeed, it's not supposed to display digits after the comma, it will be fixed in the next version, thanks!
Fixed in a previous update.
Have you started Publisher from Steam? If yes, could you try to start it directly from the exe?
Thanks.
We have updated the tools, please, could you retry (whatever the branch, Development branch is now the same as main branch (both are equally up to date)) and tell us if your issue is solved ;)
The fact GU is not able to merge app manifests is normal because the copy maintained by GU must remain independent from Steam.
Regarding the delay, it's also normal, threads are asynchronous for optimization purposes.
Then, "gameUpdater_Files.zip" can be used to restore its initial content, instead of forcing Steam to re-download GU.
Can I close the ticket?
Closed - This is not a bug, Steam must be closed before process or restarted after the update process.
The fact you're not using two Steam sessions is questionable because Game Updater opens a session to verify that you own the game and download it ;)
Anyway, I will see if I can enhance the handling of connection loss during the update process.
Thanks for the feedback ;)
Note: To restore the initial state of Game Updater, you can use the archive "GameUpdater_files.zip" as described in its read me.
It looks like there isn't any "rule" regarding the fact of opening two Steam sessions from the same computer, I had the occasion to note the following behaviors on the beta client:
- Session break (but the client is working)
- No change on already opened sessions
Could give some details?
- Do you use Steam beta client?
- Is your OS up to date?
- Do you use an administrator session?
Step by step:
- Buldozer: I invite you to take a look at the manual, in most of cases, it's a matter of configuration. https://community.bistudio.com/wiki/Buldozer_Manual
- P Drive cannot disappear because of the tools (except if you click on Unmount P from arma3tools.exe). Be sure you have nothing else impacting on the subst.
Also, some users have, from time to time, all their substitute drives hidden. To be sure it's not only hidden, open a console and type "explorer p:", if the explorer shows up, it's ok. If not, there is something that unmounts P
Greetings,
We are aware of this issue, an experimental hot fix has been released here:
http://tom4897.info/?attachment_id=2574
Can you confirm me you're using Windows 8 and not Windows 7 and tell me if the hot fix works for you?
Thanks.
Edit: This fix has been added to the development branch
http://forums.bistudio.com/showthread.php?179347-Tools-Development-Branch-Changelog&p=2758109#post2758109
If you have this issue just after an update/install/cache check, you just need to regenerate your BinMakeRules:
1 - Run BinMake from Arma3Tools directory
2 - "Play" Tools from Steam
Then, check your rules (\Arma 3 Tools\BinMake\binMakeRules.txt), this file must be correct to get the tools working as expected.
@TakeHomeTheCup: Could you fill another ticket with details? (including logs)
Issue resolved a while ago, closing.
TexView is now part of Arma 3 Tools :)
http://dev.arma3.com/post/techrep-00018
The next version has a progress bar and the button "Convert" will be disabled while converting files.
The latest techrep is incomplete, here the changes for ImageToPAA:
Added: The UI now generates a log in \Logs\imageToPAA_<DATE>.rpt
Fixed: If there is no file of a given file type, no action will be taken
In consequence, you will find the output in Arma3ToolsDirectory\Logs\imageToPAA_<DATE>.rpt
Every "common" errors are handled, so, everything is logged. I'll add a status bar (like fontToTGA) for the next techrep.
Thanks for the report ;)
Yep, AddonBuilder uses FileBank in order to make the PBOs.
As for my question, I'm just asking with which application do you have this issue because it's not clear in your report. I think it's with FileBankGUI but I'm not sure ;)
My bad, sorry, I was confused because I found the same issue with FileBankGUI, and I don't why but when you wrote "it is", I read "Is it"… Maybe I need more coffee ^^
Is this about AddonBuilder, FileBank or FileBankGUI?
It works fine.
This should be fixed in the upcoming update.
DevP will delete P Drive before calling mapDisk and will support parameter "-mapDiskOnly"
It must be related to addons because the error does not occur with on a default installation.
Tested and it has been resolved a while ago. Closed.
This issue has been fixed in current dev branch (1.47+), from a more recent ticket.
For further information, please, use the following ticket:
http://feedback.arma3.com/view.php?id=23685