HI, so if I understand it correctly you have subscribed MP mission. But you're not able to host the mission because it's not visible among other scenarios in MP screen? Or?

We're still unable to reproduce the issue. Could you please send us the logs (c:\Users\<username>\AppData\Local\Arma 3\*.rpt)? If possible please include also mission file your're trying to publish. Thank you.

hi, could you please upload arma log files (c:\Users\<username>\AppData\Local\Arma 3\*.rpt)? Where does the message appears? Directly in editor after you click publish mission button?

Cool it worked:) And yes, please let us know about any issue:)

Ok, seems your missing a launcher dll. Could you please do verification of local data of arma 3? (via Steam->library->arma3->RB click->properties->local files tab->verify integrity of game cache). Thank you

Could you please upload Launcher log files?http://arma.jiripolasek.com/howtos.html
THX

Thank you. Will get back to you after investigation;)

"This is the same with mods, you cannot launch any mods from steam workshop when not connected to the internet..."
You means it's not possible to play with mods (after they are downloaded) when there's no internet connection? Should be totally possible. What is the game error?

Just to keep you updated: I believe we've finally found the issue. Our QA is currently testing the solution. Should be out in dev soon:)

The issue should be fixed in today dev update. Could you please report back if it's working for you? thx

Found the issue. Fix is on it's way;)

Hi, thx.

I've attached new version of The Publisher. It has all logs enabled. Could you please try with it and upload new log files? BTW what mod are you trying to update?

Thank you.

ohh, yes. forgot about that. sorry for confusion.

Hi, could you please upload log file for the publisher (c:\Users\<username>\AppData\Local\Arma 3 Publisher\Logs\)? What mod are you trying to update? thx for reporting

hi, please include also binarize.mdmp and if possible the source data. Thank you.

Hi, I see you're using pretty old version of binarize. Could you please try it with current version to see if the issue is still there?

ok, but still I need mission files to do the update...

hi, other users are experiencing this too sometimes. Unfortunately seems related to their connection and steam servers. Is it possible for you to try publish from different PC/connection?

If you don't mind to upload mission files I could try it (it wont't be visible in steam and I'll delete it after publish of course).

hi, should be fixed. Currently under QA tests.

seems it's directly related to win10 version reported

hi, thanks for super info. Sorry for the delay- vacation. We'll find out the issue;)

Unfortunately we're not able to reproduce the issue. Although I've tested on win10 build 10162. have tried this build?

hi,

sorry for a long silence. Unfortuantely we're unable to reproduce the issue. Does this happen also for the Launcher? Do you have any custom dll's installed? Could you please try version in the attachement and send the logs again?

Thx,

Cooper

you're welcome.
implementation done, submitted to QA for testing;)
thx for good idea:)
Cooper

will do, thx

released in dev branch

Steam bug - publishing fails sometime

Great it worked even that you had to create a new item.
Those are great questions and we think it's exactly how you describe it but only Valve has answers.
It's hard for us to find the exact reason since we're not able to reproduce the issue. What we see from the logs is that many queries made by the publisher are failing for some reason. It happens time to time to random users.
What we'll definitely do is to add functionality so that prev images will be shrinked/compressed so that it's size is under the 1MB limit.
Anyway thx for great collaboration:)

Feel free to remove it;)

hi, thx for the logs. It seems you are publishing preview image with size greater than 1MB. This is the limit. Could you please try to publish the item with smaller preview image? Thx

I've just sent a PM to your email...

hi, thx for reporting. could you please upload publisher logs? could be found in c:\Users\[username]\AppData\Local\Arma 3 Publisher\Logs\arma3publisher.rpt

hi,
the temp folder should be deleted for sure. Could you plesae upload the log file? Will take a look and fix the issue. The log could be found in c:\Users\[USER]\AppData\Local\Arma 3 Publisher\Logs\
Thx

version 1.40.130473

Found it and fixed it. You could expect it in dev branch very soon (after QA testing). Also found and fixed another annoying bug where saved games were lost if the mission was updated.

Did you choose to restart the mission after the update? If there is a save for previous version and one click "continue" the game will use pbo for which the save was made. So until one chooses to restart the mission the game keeps the old version (compatible with the save). Once you choose to restart the mission gets updated. Could this be the case?

no longer valid (steam issiue anyway)

So does the deletion solved the issue for you? Seems like Steam Client issue. There's also issue on Steam DB that some items cannot be updated, but actual update fails in this case. Could you please also upload Steam workshop log? Could be found in usually here: c:\Program Files (x86)\Steam\logs\. PLease upload "workshop.log" and "cloud.log" files. Thx

Hi,
looking into the issue right now. Thx for reporting and for crash files. It helps a lot.
Will keep in touch;)

Could you please upload AddonBuilder log file (AddonBuilder.rpt)? It's located in Arma3Tools root dir under Logs folder usually c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\AddonBuilder.rpt

Hi, I had a time to take a look at the issue finally.

Unfortunately from the logs everything seems fine. The "Syncing file ..." message is a result from "Whitelist" setting in Option window. This is set there: *.pac,*.paa,*.rtm,*.sqf,*.sqs,*.bikb,*.fsm,*.wss,*.ogg,*.wav,*.fxy,*.csv,*.html,*.lip,*.txt,*.bisurf,*.shp,*.dbf,*.shx,*.prj,*.cfg,*.rvmat
So those files needs to be copied to temporary folder before binarizing, packaging. With whitelist you are saying: please include those files in resulting pbo. It does not have anything to do with binarization exclude list. binarization exlude list is list of files/folder that should not be binarized. Still all files (binarized or not) will be "packed" into pbo file. If you empty your whitelist setting no sync will occur but the pbo will not work since no texture headers will be present for example.

Hi, will resolve this week. You can expect the fix in release next weeek. Thx for your patience.

Hi,
thx for the logs and your describtion. I see the issue. Will ping you when it's fixed (in a new year unfortunately).

Thx and Merry Christmas,

Jiri

hi,

thx for reporting. Could you please upload your Logs dir in Arma 3 Tools? typicaly c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\.

thx,

cooper

QA approved, reporter confirmed.

hi,
thx for reporting and sry for your troubles. The fix is under internal testing currently. Should be out in dev today.
Cooper

hi, thx for the logs and the video. it was really helpfull. Finally I've found the issue. There is a simple workaround for now. One needs to have "*.paa" in the whitelist option but it needs to be without a space - i.e. "*.paa" but not " *.paa". This is the reason why it's not working for you in the video. Just delete the leading space and texture headers should be created. The fix will search for paa files automaticaly (without the need of manually specified *.paa pattern) and spaces will be allowed of course. Thx again for your collaboration;)

I'm glad it's working for you. Fix is under internal testing now. Sorry for a stupid bug. Thx:)

Hi,

dev branch was updated. Please restest if the issue was solved. The version (could be find in the "About" window ) is 1.1.128499

Thx

Thx a lot, we currently uploading a new version with the fix:)
Will inform you when it's available;)

Hi,

thx for testing and your patience. Unfortunately I'm not able to find uploaded logs. Could you please reuload the log from dev build?

Thank you

Hi hero,

we've made an update on DEV branch yesterday. It should fix your problem. Could you please retest with DEV branch?

Thx,

cooper

Hi, thx for reporting. could you please upload AddonBuilder log file? Should be located in arma3tools/logs, typically c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\addonbuilder.rpt

thx

hi, sorry for confusion. the fix is under testing now. will be released very soon. thx fot your patience

fixed. new version will be released soon. thx for providing the pbo

hi, the issue should be fixed now. The fix will be included in next arma 3 tools update.

hi,

ok, you have your steam library elsewere. At least this part of the path should exists somewhere in you pc: SteamApps\common\Arma 3
Tools\Logs\Publisher.rpt. Location of the steam library dir could be found in Arma 3 Tools properties in Steam client. Run/open Steam -> library -> tools->arma 3 tools -> right click -> properties -> local files tab -> browse local files. explorer will open and you should be able to find Logs dir with Publisher.rpt file.

Thx

Hi,
could you please upload log file?
Should be located here: c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\Publisher.rpt

Thank you.

Hi, whats the name of the item you're trying to update. It's a inconsistency in Steam backend DB. Fortunately Valve is able to fix it per item.

hi, sorry for your troubles. unfortunately we're still unable to reproduce the issue. Our QA is testing this every day (using your pbo) but it's ok every try. it really seems there's an issue on steam releated directly to your specific conditions. we'll keep you updated if anything new arise

Fix for this will be released tomorow with stable version. It will work all three ways then. thx for workaround and sorry for troubles,

Jiri

Hi,

sorry for taking so long but it's fixed. it will be released tomorow with stable version.

thx,

Jiri

hi, thanks for the log.

From them it seems you are running stable version of publisher. Is this so?

There is a new version of the publisher if you switch to the developement branch (right click on Arma 3 tools->properties->betas->select developement from the first combo).
You need to start it directly via exe, not through arma 3 tool (will be fixed with upcoming stable update). Just navigate to install dir of arma 3 tools (typically c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Publisher) and launch Publisher.exe file.

Hope it helps;)

we've updated the builder around 14 so the fix is was already there when you're trying it I guess. Anyway I'm glad it works ok for you:) THX

Thanks for the log.
Issue is fixed. We'll update the developement branch today.
Will keep you up to date.

Weird. I'm not able to reproduce. Could you please upload log file (c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\AddonBuilder.rpt)?

Hi, update should be done today (it went wrong yesterday). Will update you once it's done. Thx

hi, updated. Fix is there (tested my self).
Thanks for your patience

I'm really sorry for your troubles. Issue is fixed now. Should be released next week. Sorry once again for this stupid bug.

ok, please uploud the logs once again if present:
c:\Users\[username]\AppData\Local\Arma 3 Launcher\Logs\arma3launcher.rpt
and
c:\Users\[username]\AppData\Local\Arma 3 Launcher\Logs\SteamServiceHost.rpt

There could be also crash minidump file located in:c:\Users\cooper\AppData\Local\Arma 3 Launcher\arma3launcher_2014...mdmp
Please upload it too.

Thanks a lot

Thanks for the log. Unfortunately everything looks fine in it.
Could you please post a list of files under "[arma 3 install dir]\Launcher" dir? Steam client sometime fails to download all files.

Thanks a lot.

thanks for the shot. There was an update of stable release (you need to switch arma back to NONE in betas) of the launcher yesterday. Does it work for you?

hi,

could you please paste logs here?
It could be found in c:\Users\[username]\AppData\Local\Arma 3 Launcher\Logs\

Thx

Ok, now I have a repro. Thx. Will update you once I find out the reason for the issue.

Hi, I'm sorry, but i'm not able to reproduce it (wrong data). I've followed your steps but it's working fine for me. Could you please try to use it in your installation? Pbo is in the atachment. Maybe there is a difference. Let's see. Thx.

Thx a lot for detailed report. Have a working repro so I should find the answer;)

Could you please upload animation you are using along with model.cfg and logs (c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\AddonBuilder.rpt). Thx

Hi, sry it's still not working for you. We're trying to solve the issue. Unfortunately we're unable to reproduce it on our side. Could you please send us fresh logs using the latest version of the launcher? There will be big update of the launcher in dev branch next week. So hopefully it would fix the problem. Will let you know once it's out so you could retest. Thx for your patience and collaboration

Hi,

could you please try to subscribe this: http://steamcommunity.com/sharedfiles/filedetails/?id=333310405
and see if it's visible in the launcher?

Are you sure you are subscribing to addons? I.e. not scenarios/missions? Those items has addon or mod tag assigned instead of scenario tag. Only those are visible in the launcher.

Thx,

Jiri

seems there is process isolation problem between launcher and steam client. could you please try to launcher both (steam client and launcher) as admin? thx

hi, could you please try to switch Arma to the developement branch?

Hi, there was a major update recently. Does the issue still persist? Does it work in dev branch?

.NET 4.5.1 installer added

I'm really sorry for your troubles. Issue is fixed now. Should be released next week. Sorry once again for this stupid bug.

thanks for pointing this out. the parameter names need to be lower case now. sorry for confusion. I've already corrected help text.

Regarding the prefix and project, this is a know issue and it's fixed by now. will be part of next update

just a execution command needs to be changed and it should work properly

command needs to be in this form:

AddonBuilder.exe "p:\rhsafrf\.." "k:\Steam\..." -packonly -clear -prefix="rhsafrf\addons\..." -project="p:\rhsafrf" -sign="k:\developement\..." etc.

So basicaly equal sign must follow any parameter whitch is not switch param (i.e. it's a value parameter). There is a nice example in help(AddonBuilder.exe -help).

if you still have questions just ask:)

VS 2012 redist. will be installed during installation of the tools

Could you please try to install this if it solves the problem? http://www.microsoft.com/en-us/download/details.aspx?id=30679

fixed meanwhile

Hi, will close this issue. Are those problems mentioned above reported? If no could you please create new issue for them? Thx

Hi, is this still happenning to you? thx

could you please paste/upload the log? will be very useful. thanks

project path in options window to rescue. this defined dir used to search for includes in config files. so in your case it should point to arma 3 root

from the log I see you are gettring error during config convert. seems there is a bug in "C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\@FETT_Test\addons\FatTrack\config.cpp" file. Maybe wrong project dir? It needs to poinnt to the root of include files used in the config.cpp

hi,

could you please upload your log file (c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\AddonBuilder.rpt)?

Thx

The status is actually a log and it's configured in the same logger.xml file. Please make sure you have these lines there (present in original xml):

<?xml version="1.0"?>
<log4net>

...

<appender name="StatusAppender" type="AddonBuilder.StatusAppender">

<layout type="log4net.Layout.PatternLayout">
  <conversionPattern value="%message%newline" />
</layout>

</appender>

<logger name="user" additivity="false">

<level value="INFO" />
<appender-ref ref="UserConsole" />
<appender-ref ref="UserRollingFile" />
<appender-ref ref="StatusAppender" />

</logger>

...

</log4net>

@TomNedry: thanks for the log. the issue is fixed. we're gonna test it internally before update.

@deanosbeano: this line "<file value="AddonBuilder.log" />" specifies log locatation. so in your case it should look like this: <file value="LOGS\AddonBuilder.log" />
or this: <file value="P:\LOGS\AddonBuilder.log" />

Fixed. Submitted for internal testing