SpiritedMachine

On the "Launch Options" tab, find the dropdown box that is titled communications. You have teamspeak selected, or it wouldn't be giving you this error. You need to change it to None.

It can't find your Teamspeak executable.

LOL I love your brand of humor.

Seems to be just a problem of the order that the launcher writes the parameters. I may add a feature allowing you to reorder the parameters how you want. To do what you're talking about, using "-applaunch xxxxxx", don't you have to have steam as your "ArmA 2 Executable"? If so, the launcher was never really designed for this, so I can't guarantee anything.

"Allow Duplicates" means you can have the exact same mod in more than one group in the treeview. It has nothing to do with mods in different locations having the same folder name. As far as the launcher is concerned, they are completely different, because they have different folder paths. Hover over an addon in the list to see its full path. This lets you know which version you're dealing with. To hide addons in the "Available Addons" list, click on the Addon Options tab, and drag the mods you don't want from the Visible list into the Hidden list. Almost every setting is per profile, with the exception of window size/position, and Allow Duplicates. The checkmark on the root group turns mods on or off altogether. A checkmark on a group turns the mods in that group on or off, and of course you can turn individual mods on or off. Right-click on a node to see more options to allow you to check/uncheck entire groups, etc.

Uncheck "Autoskip", the checkbox that is seen in your screenshot. That is if you are trying to download ACE2 for OA. If not, don't overwrite what you have.

I've had enough people ask for this, I finally caved to the overwhelming demand. :) Version 1.2.9 is available now. With this update it is now possible to allow duplicate addons in the addon tree-structure.

This is a great addon. My only complaint is the "Initializing DSS..." in the middle of my screen for who knows how long. Maybe I just have a donkey computer, but it takes forever for this to initialize, and it really hinders my aiming... If you could have it display a hint, or something in chat, rather than in the middle of the screen, that's my only suggestion. http://dev-heaven.net/issues/12146

Version 1.2.8 is available now, which has "Reset Window Position" in the tray icon right-click menu. It will reset the window to the center of your screen.

Sometimes the window location saves incorrectly, resulting in the window forming off-screen. This usually happens if you move it to a second monitor that is to the left of the main monitor. Deleting anything inside of "C:\Users\YourAccount\AppData\Local\Spirited_Machine" will reset the application. I will look for a solution to this, or at the very least, include a way to reset the window position from the tray icon.

Due to the fact that Operation Arrowhead uses Steam copy protection, every time you go to start the game, whether you use steam or not, steam must start and display the "Preparing to launch ArmA 2: Operation Arrowhead". If you use several mods, or mods located outside of the OA main directory, it causes that dialog to hang, and the game never starts. If you use the beta version of OA, it works fine. ArmA 2 doesn't use this copy protection, so why does Operation Arrowhead? I'd like to see it removed in future releases if possible. It has caused nothing but headaches for me and many others wondering why our game doesn't start when we want to play with mods.

OA doesn't, unfortunately. That's what I'm hoping for sometime in the future.

Updated to 1.2.7 It now checks for duplicate paths rather than duplicate names, so you can have 2 addons with the same folder name, as long as they are in different locations. eg. ACE for ArmA 2 and ACE for OA Also, now when hovering over an addon in the "Available Addons" list, you can see its full path, so you know which version you're working with.

I'm glad it seems to be working well for everyone now. I'm going to be out on a motorcycle road-trip all of next week, so I won't be able to make any updates or fixes until at least a week from today if not later.

Here is a list of examples of the many ways I have tried to run this game, along with the result. Please explain to me what I am doing wrong. It seems to have something to do with the length of the startup parameters string. If I were to use ACE and ACEX, both in my ArmA 2 directory (using full paths), OA starts fine. If I use ACE, ACEX, ACEX_SM, and ACEX_PLA (all using full paths), the Steam dialog hangs. When using the beta version of OA, the game runs fine every time. That tells me that it is an issue with Steam/Steam protection, and not a problem with any BIS product. USING MODS OUTSIDE OF OA DIRECTORY (Full paths required, results in long parameter string) Operation Arrowhead: Target: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\ArmA2OA.exe" "-mod=Expansion;c:\program files (x86)\steam\steamapps\common\arma 2\@acex_pla;c:\program files (x86)\steam\steamapps\common\arma 2\@cba;c:\program files (x86)\steam\steamapps\common\arma 2\@ace;c:\program files (x86)\steam\steamapps\common\arma 2\@acex;c:\program files (x86)\steam\steamapps\common\arma 2\@acex_sm" Start In: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" Result - Hanging Steam Dialog: "Preparing to launch ArmA 2 Operation Arrowhead" Combined Operations: Target: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\ArmA2OA.exe" "-mod=C:\Program Files (x86)\Steam\steamapps\common\arma 2;Expansion;ca;c:\program files (x86)\steam\steamapps\common\arma 2\@acex_pla;c:\program files (x86)\steam\steamapps\common\arma 2\@cba;c:\program files (x86)\steam\steamapps\common\arma 2\@ace;c:\program files (x86)\steam\steamapps\common\arma 2\@acex;c:\program files (x86)\steam\steamapps\common\arma 2\@acex_sm" Start In: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" Result - Hanging Steam Dialog: "Preparing to launch ArmA 2 Operation Arrowhead" USING MODS WITHIN OA DIRECTORY Operation Arrowhead: Target: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\ArmA2OA.exe" "-mod=Expansion;@cba;@ace;@acex;@acex_sm" Start In: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" Result - Game starts as expected. Combined Operations: Target: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\ArmA2OA.exe" "-mod=C:\Program Files (x86)\Steam\steamapps\common\arma 2;Expansion;ca;@cba;@ace;@acex;@acex_sm" Start In: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" Result - Hanging Steam Dialog: "Preparing to launch ArmA 2 Operation Arrowhead" USING NO MODS Operation Arrowhead: Target: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\ArmA2OA.exe" "-mod=Expansion" Start In: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" Result - Game starts as expected. Combined Operations: Target: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\ArmA2OA.exe" "-mod=C:\Program Files (x86)\Steam\steamapps\common\arma 2;Expansion;ca" Start In: "C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" Result - Game starts as expected.

Dwarden says we're all doing something wrong, there is apparently nothing to fix... Ticket was rejected.

http://dev-heaven.net/issues/11829

Thanks very much, both of you.

Hopefully it will be fixed sometime soon, but to fix this problem for now, you can use the OA beta: Download the beta here. Install it. Start the launcher, then go to the Launch Options tab. Browse for the ArmA II - OA Beta. It can be found in your OA main directory/expansions/beta. Check the "Run Beta" box on the Launch Options tab, then play the game. If anything it should improve the game. I have had good luck with it. Thanks, you're the second person to bring that up. I will have a new version released sometime today that will fix that issue.

Two posts above yours I already brought this up. It's not an issue with your computer or the launcher. It is apparently a Steam issue, this is confirmed by at least one member of BIS staff. You can solve the problem by using the beta version, which does not require steam to run.

while {not isnull Unit1} do {"mkr_unit1" setmarkerpos getpos Unit1; sleep .5;}; If I place this code in my init.sqf, it works fine, but nothing after this code works. I assume this is because it's a while loop, and it never exits the loop, tying up the game. How could I have this working, but still be able to process other code?

I have noticed, and it has been brought to my attention several times, that when you run Combined Operations mode with addons that are located in the ArmA II directory, the Steam dialog reading: "Preparing to launch ArmA II: Operation Arrowhead" hangs, and the game does not start. Is this a problem with Steam that is out of your control? If I use the beta version of OA instead, it takes care of the problem. Also, is there a reason why launching the OA executable directly (not using Steam) requires Steam to start before the game does, but ArmA 2 does not? Can this be changed?

Some of you may have noticed that if you run ArmA 2 + Operation Arrowhead (aka Combined Operations), as well as mods from your ArmA 2 directory, that the Steam dialog "Preparing to Launch ArmA 2: Operation Arrowhead" hangs there, and the game doesn't start. This is apparently an issue with Steam, not the launcher. Typing the same startup parameters into OA's "Launch Options" in Steam gives the same result. Because of this, I use the OA Beta. It seems to run better than the officially released EXE. To download the latest version, go to the first post.

Dwarden, Why is it that "ca" does not need a full path, but everything else does?

No, I can't figure that out either. It's not something that I am doing. I even asked about this yesterday in a forum post here.