As this can stop the whole mission without the player knowing why, I set it to severity Major.

Please, BI, we need a fix for this, thanks!

Hi, do I understand it correctly that this comes with the next update? Or is it not sure yet? (sorry, no feedback tracker pro)

Any news on this subject to share (apart from that the ticket author just flattened everything)?

Hello BI, since 1.17 unfortunately it's no longer possible to dismantle a (modded) code lock and also the vanilla locks in 1.17 on a modded server.

Fun fact: The hotfix was supposed to fix base building problems.

This annoying and partially mission breaking bug isn't necessarily related to the "SAFE" behaviour (rather to "COMBAT") but definitely to the unitpos "UP" stance.

Thanks for your reply, BW. I hope you can find a solution.

For me the bug was in the World parameter. I unticked it and the tasks were there when resuming mission or campaign.

This is a PITA. Destroys a lot of atmosphere...
Please fix it soon, BIS. Thanks.

1.53 beta

Sorry, just a small question not related to the issue itself: What does "reviewed" mean here in the bugtracker?

I now deinstalled Steam completely, reinstalled and redownloaded the Tools.

When I opened Publisher, well, the storage space seemed to be the right one (it wasn't 799 MB at least).

Full of hope I tried to update AND...... :( nothing. The progress bar quickly jumped to "Update successful" and nothing changed.

I mean... It doesn't even upload anything! Earlier the progress bar at least stopped at the middle for a while, indicating that an upload was in progress, but now it finishes after 3 seconds, either to "Successful" or "Failed" (I tested it renaming the file again, and it failed).

And after these fails, when I opened Publisher again, the storage space was at 799 MB again.

Hi Wizard, does that mean that there's no way to update my entry? What else can you do or suggest?

Thanks!

It still doesn't work in the last update... :(

Either the statusbar in Publisher quickly gets to "Failed" or "Successful". The file itself remains the same (18 MB)

I added the .rpt's for both cases above. I don't see a difference in them, but ok, I'm sure you will. :D

But I think I know now how to make it fail and succeed:
If I name the addon file und_dyingember.pbo, it will succeed, if I name it differently, it will fail.
Interestingly I think that the actual version (the 18 MB one) also has the name und_dyingember.

I also added two pictures above:
One, if you launch Publisher via Steam (in Steam, start the Tools and from the menu, which tool you want to start, chose Publisher).
And the other pictures shows Publisher, when started from the Arma 3 Tools menu.

If I launch Publisher from the Arma 3 Tools menu, my project appears in the list (Dying Ember (SP resistance campaign). However, my Steam could storage space is wrong. I ONLY have the 18 MB campaign on Steam (check the picture from the Arma 3 Tools Properties above), so 799 MB are definitely not the case. The thing is just that this space doesn't change anymore, no matter if the "update" succeeded or not. This was different earlier: When I began this update odyssey, it still changed - with every update try it got less and less, but at one point it stayed at 799 MB and didn't change anymore.

If I launch Publisher from the Steam menu, the tool seems to get the right a storage space which is closer to reality. However, 935 MB are still too less (considering that we have 1000 MB and the only file I have online is 18 MB). Maybe the storage got "pumped up" with the updates tries, I don't know...

Apart from that, if I launch Publisher from the Steam menu, my project won't appear in the list.

So all in all: Why is there such a difference in Publisher, starting from the Steam menu or from the Arma 3 tools?

I don't know if these observations help you, but I'm quite desperate here, facing the deadline of the MANW contest and not being able to promote my project via the workshop.

Hi Wizard, I uploaded the logs above.

Just a small addition:
This time it didn't fail to update. But as many times before, it also didn't update the file itself. It still is the same on the Steam Workshop: 18 MB, instead of 33 MB.
Logs uploaded above -> logs.zip

Then I renamed the file and tried it again - now it failed.
Uploaded the log dumps (logs_FAILED.zip).

Hi Wizard, the name of the addon (resp. SP campaign in addon form) is Dying Ember.

Here's the Steam Workshop page (still with the old version, which has only 18 MB, instead of 33 MB (new version)):
http://steamcommunity.com/sharedfiles/filedetails/?id=303626919

The new file (addon) is downloadable here:
http://www.mediafire.com/?2irvpyy2jc65rh9

Other than that I refer to kibot's post in this thread - he has the same problem and describes it very well too (including the feelings :D ):
http://forums.bistudio.com/showthread.php?183861-ARMA-3-TOOLS-Publisher-fails-to-upload-the-file-to-SW&p=2790872&viewfull=1#post2790872

I tried reinstalling the tools, I tried checking the file integrity, I tried to rename the .PBO, I tried it with bruteforce (repeated update). No luck.

I'm sorry, guys... :( I noticed that I had a trigger on the mission area which removes all items from cargos...

The putWeaponPool command seems to work just fine.

SORRY!

I think that this one can be closed, as after the last Publisher updates it didn't crash anymore. It has different issues, but this is another story.

It should be added that addItem is not sufficient, as the radio will just be put in the uniform of the unit. You have to link the radio to him so that it gets in the radio slot.

unit linkItem "itemRadio";

It absolutely worked, yes! :) I have a cutscene, where an unarmed unit stood up - I still can see it clearly in front of me. And I still remember the pain, when this bug was introduced in 1.12 and he didn't stand up anymore. ;)

The bad thing is that even changing the AI's animation with switchMove doesn't work...

A fix would be much appreciated. Thanks a lot.

Still present in v. 1.20.
Please fix this, BIS - it was once ok and then introduced in a STABLE patch... :(

Thanks!

I can only partly agree with Pops!

It surely got better, but they still get stuck too often on rocks / stone walls. A definite fix of this bug really is needed, as it has the potential to pretty much mess up every mission with tanks going offroad (which is what they were built for too).

(Version 1.22)

Sorry, just a small question not related to the issue itself: What does "reviewed" mean here in the bugtracker?

Please, BIS, hear us and add this! It's just so frustrating seeing the AI die because they don't JUST DO it when they're in combat behaviour...