(steam)Maximum number of "@mod"s in target line, or in .cmd CO file?

[WingmanSR 10]

Hello,

I have combined operations plus BAF, all purchased from STEAM. I have about 40 mods, I am using Arma II launcher v1.4 and running on Windows 7 64bit.

I ran into a problem when I was adding "@mod"'s to the .cmd file that is used to run the steam version of combined operations, where it appears it cannot be more than a certain number of characters long. So my solution was to combine mods into broad mod category folders(ie @panthera. @Fallujah, @SAP_everon, etc all in an @Islands folder). Doing this allowed every mod I use to work together without issue. Enabling/Disabling mods via the in game UI does not function. Loaded mods via shortcut method are greyed out. Unloaded mods simply do not appear on the list. I believe this has to do with the .cmd file used to run Combined Operations.

My problem is, I want each mod in an individual folder, with the ability to run all or some or none of the mods. I have all the RH weapon mods, for example, and want the option to load these individually. The reason for this is mission editing mainly; I do not want a mission that has f16's require the f14 mod, simply because I have combined them into an @Air folder, although I can remove it from the mission.sqm, I still want them individual for simplicity and organization.

I thought that using a launcher would allow me to do so, but after taking 1.5hours to delete the combined mod folders and re-extract the .7z's, I am having the same issue when running all mods(steam window: "Preparing to launch ARMA 2: Operation Arrowhead..." it progresses no further than this when the -mod= line exceeds an unknown length.) It appears the launcher is just a visual manner of adding -mod=.

Is this an inherent limitation of windows 7 64, steam or arma 2 itself? Is running the mods in combined folders my only option? What exactly is the maximum number of @mods or characters I can add to the target/.cmd?

I'm sorry for writing an essay, but I like to be crystal clear and provide as much detail as possible. Any information regarding my questions in the paragraph above will be appreciated.

Regards

Edit: this is what my mods line looks like with each mod in a separate folder:

"-mod=C:\Program Files (x86)\Steam\steamapps\common\arma 2;Expansion;ca;baf;@cba;@jayarma2lib;@ace;@acex;@acex_ru;@acex_usnavy;@zeusai;@veglow;@fallujah;@fran_quesh_kibrul;@isla_duala;@sap_everon;@panthera;@vopsound_ao;@rksl;@f117a;@f14;@f15;@f16;@x02wyvern;@mi-26;@kuznetsov;@helos;@ffaa;@rh_hk416;@rh_m40_1.0;@rh_mk18;@rh_smg_1.02;@satcom"

Edited November 12, 2010 by WingmanSR
Added mods line

[kylania 568]

This is exactly why I bought Combined Operations on DVD and installed it to E:\CO :) No more mod line length problems! (And I get patches when they get release, not when Steam feels like it.)

Your best bet is to combine your addons into smaller folders. Since you use ACE you're pretty limited, but try something like:

-mod=c:\program files (x86)\steam... blah;Expansion;ca;baf;@cba;... ace stuff;p;i;u;w"

Create folders in your Arrowhead install called p, i, u and w, put AddOns folder under each and move all your PBOs into them: p for planes, i for islands, u for units and w for weapons.

If your line is still too long, dump them all into p :)

Or buy the CO DVD and never worry about this, or late patches, again.

[CarlGustaffa 4]

Or put your startup line to a .cmd file and point your shortcut to it. Works well for server at least. But yeah, create your own "modpack" instead of using a bunch of different folders.

[WingmanSR 10]

ahh, bummer, I was really hoping there was some mystical, arcane wizardry hidden amongst the bis forum denizens. I do now wish I had purchased CO on dvd, for this situation and the fact that I have to move my whole steam folder to SSD instead of just the Arma 2 directory.

thanks for the idea carl, I'll give it a go. Otherwise, it's back multi-mod folders.

[MulleDK19 21]

Maybe this'll help you?

http://www.sierrasoftworks.com/arma2ml

[TechnoTerrorist303 10]

If you know you're going to use the same mods each time why don't you just put all the .pbos in one grand unified mod folder and run the whole thing as one mod?

[oktane 0]

Use the symlink method.. this will make your game combined operations all the time.

Then you can use the in game manager. (because now you wont need to specify A2 on the mod line)

Is the symptom, that steam says Launching but it just hangs?

Btw, theres a space in your mod line.

Heres the script to do the symlink: http://506th-pir.org/scripts/oktane/combine_A2_and_OA_into_CO_v2.zip

Make sure you run it as administrator.

Now you don't need to tell steam to run as Combined Operations anymore.

You can also try Spirited's ArmA Launcher, but it will have the same issue if you have a long mod line and steam.

You can also get the beta, and then you wont be hassled by steam's issues like this. (the max modline issue is steam afaik)

Hope this helps some.

[Trracer 10]

The max modline issue is a limit in windows on the length of the arguments to an executable afaik.

[WingmanSR 10]

What is ArmA 2 Mod Launcher?

ArmA 2 Mod Launcher is a compact command line application designed to allow advanced ArmA 2 players to launch a predefined set of mods quickly and easily. Its main objective is to allow people with very large mod collections to start mods without worrying about the constraints of a windows shortcut's path length.

Great find, MulleDK19.

Is the symptom, that steam says Launching but it just hangs?

Btw, theres a space in your mod line.

Yeah, steam says it's launching but never gets to the "checkbox" window.

That mod line is from a launcher, I just clicked check all, and manually removed the mods I rarely use.

Just your good ole' fashioned ID-10T user error. Now, where IS that 'any' key...?:cool:

I'm pretty much already doing that, Techno. I really want the ability to cherry pick which mods I'm using.

I'll try the symlink method mentioned by oktane first. It seems like the simplest solution, but that mod launcher looks awesome. I'm definitely going to have to play around with that.

edit: thanks for making the NoBlur mod, oktane!

Edited November 12, 2010 by WingmanSR

[Dwarden 1125]

simply put

if the commandline the STEAM.exe has to to relay is beyond 255-260 characters , the steam itself gets stuck on 'preparing the launch'

will discuss with Valve if they can improve / fix it

[AnimalMother92 10]

Is there any simple way around the shortcut target limit? I've been fine with mod launchers but I wanted a one click shortcut solution but there's no way my mod line will fit. The above mentioned program doesn't work for me.

[CarlGustaffa 4]

The .cmd approach should work with non STEAM versions (or at least DVD versions). I use it on WinXP32 for my client, and on Win2007 Server 64bit for our server.

[AnimalMother92 10]

I have A2/OA/BAF all on Steam though. That, plus mods and the beta makes for a real party :)

"C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta\arma2oa.exe" "-mod=C:\Program Files (x86)\Steam\steamapps\common\arma 2;Expansion;ca;Expansion\beta;Expansion\beta\Expansion;baf;@ace;@acex;@acex_ru;@acex_usnavy;@cba;@jsrs;@maps;@misc;@rebl;@warfx;@zeusai" -nosplash -world=empty -cpuCount=4 -skipIntro

[killaalf 0]

How about moving Steam to C:\Steam? That alone will free up 38 characters.

[WingmanSR 10]

Thank you for the input, Dwarden.

Personally, I have used the link provided by oktane to merge the arma 2 files into the operation arrowhead directory,

and now I can skip using the modline method and activate/deactivate mods directly within the UI "expansions"

option on the main menu. It worked beautifully. I simply ran operation arrowhead vanilla, then activate arma 2

as a mod and presto, you now have combined ops.

Checking with valve on increasing their command line relay length would be awesome.

There are quite a few steam users who would benefit from this.

[Trracer 10]

As I said before... the limit of a windows shortcut target is ~260 chars.

So it's not an arma2 or steam issue. It's a windows "issue".

[kdjac 19]

I have DVD Arma, Steam OA/BAF

I use arma launcher and never once did anything to my steam CMD.

http://forums.bistudio.com/showthread.php?t=89731

And it runs whatever amount of mods/betas/CO as i want.

All my addons are on D:/Arma2 and my Arma is on C: and Steam is on E:/

Hope that helps.

[WingmanSR 10]

I use arma launcher and never once did anything to my steam CMD.

http://forums.bistudio.com/showthread.php?t=89731

And it runs whatever amount of mods/betas/CO as i want.

I have attempted to use that very same launcher, but I get the same problem.

As I said before... the limit of a windows shortcut target is ~260 chars.

So it's not an arma2 or steam issue. It's a windows "issue".

:confused: Interesting, I had taken Dwarden's post as confirmation that this was a steam limitation. So, from what you said about Windows itself being the limiting factor, I suppose the only issue with steam is that the file path to Arma2OA.exe is much longer than it would be with a dvd version installed in the base directory of the HDD, ie

"C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\Arma2OA.exe"

versus

"C:\arma 2\Arma2OA.exe".

and thus consumes more of the command line character limit.

Is there a technical reason why Windows cannot/will not allow more than aprox. 260 characters in the target? Is it simply a "design decision" as in Microsoft assumes no one could possibly need to add enough launch parameters to the target line to get to 260 characters?

I ask this more out of curiosity as I have already found a satisfactory solution in the form of oktane's symlink.

Edited November 19, 2010 by WingmanSR

[Dwarden 1125]

windows should not be factor

considering since w2k the commandline character limit is 2047 and since wXP it's 8191 ....

http://support.microsoft.com/kb/830473

anyway with upcoming OA patch this problem should be minimal from our side ...

p.s. i notified Valve about it but no ETA was given