I think most players for Arma Reforger are actually on xbox, or maybe by now its 50/50.

In T182469#2636082, @dedmen wrote:

Furthermore, workbench publishing should do more for fragmenting the mod internally

This is also a major concern for me. Installing an update for me means waiting 10 seconds for the download. And then waiting 10 minutes for it to re-write the files to incorporate the patches.
In Arma 3 that would rewrite one or two small PBO's with a few hundred MB. With 3rd party launchers that can do smart patching, it can even do it without rewriting by just plugging new data onto the end.
In Reforger I wait for it to rewrite gigabytes data.
That's even more terrible on consoles that are more write speed limited.

192 byte update? Sure one sec, let me rewrite 17GB of data.

This is just a example of the game itself, but same thing happens to mods alike.

I second this point from RHS perspective. Splitting mods into multiple mods is NOT the right solution to the problem. Please up this limit accordingly. We are living in the 21st century, my browser eats 5 GB of RAM in a single session.

I would propose to consider adding possibility for non-cloth prefabs to have a "ground" item model. I understand that in most cases this might be useless but there are nontheless weapon attachments for example that might look weird on the ground using the same MeshObject model as they do when attached to the weapon.

This is really really not fixed. Or if this is not a bug and just a matter of tweaks to the vehicle configuration please someone post a guide on what needs to be taken into account to get rid of this.

Another Vanilla Apex model found affected:

This is unbelievable, how can this not get fixed before release?? :( all FFV work is now broken. Every vehicle that uses FFV and doesn't share exterior in interior lod is for nothing! Very disappointing :(

Easy fix: delete all mem points and replace them with BIS Sample soldier mem points. The long story: LeftLeg and LeftUpLed (same for right) selections were missing in old setup.

hmm then how would it binarise?

removing all the anim_f folders from P:\a3\ has solved this issue for me. Now packs fine.

Agreed, what has been going on with the registry values can only be described as a pub crawl. Always a party with a new update.

I have the same issue.

Yeah this is quite a misser. We also wonder why there has been 0 response.

That is good to hear, but will there be a hotfix soon? Or in some weeks?

2014-06-18 20:51:04,146 [INFO] - Copying PBO. [source]=C:\Users\Alex\AppData\Local\Temp\rhs_c_troops.pbo, [dest]=K:\Steam\steamapps\common\Arma 3\RHSAFRFDEV\addons\rhs_c_troops.pbo
2014-06-18 20:51:04,146 [INFO] - Done.

but alls it is is lies

Our work has been at a standstill for 3 weeks already :(

That is fantastic news :)! I hope the update will be soon!

Addendum:

I got it to pack now, problem was with using capitalized arguments: -CLEAR - PREFIX etc (in a way it was before with old tools and in a way they are put in the help description (not in the example but I didnt notice)

Anyway the problem now is that the prefix is not being registered at all

for example for that perticular file the prefix should be:

rhsafrf\addons\rhs_c_troops

but no matter what I put in the -prefix or -project argument it always gets reset to rhs_c_troops thus leading to never being found.

Thanks, will try it later. Didn't even consider based on old functionality.

Hi cooper,

unfortunately no go. I still keep getting the "There can only be one source_path and destination_path at the same time"

http://i.imgur.com/QwpJR35.png

ive looked and stared at it, added and removed quotes around the paths, dont know whats going on.

Something is wrong with the zeroing in any case. Looking through the configs it is clear that some of these scopes were indeed intended to be zeroable. Even more funky is that making a custom addon with zeroing enabled produces weird random results:

1 - Either range is not shown but pageUp and PageDown works.
2 - Or range is shown but ranging doesnt work. In all cases code used is:

weaponInfoType = "RscWeaponZeroing";
discreteDistance[] = {100,200,300,400,500,600,700,800};

Also a bit confusing whether these things should be used in the fireMode classes like that shown in the UGL, the main rifle class definition or the scope definition.