No backwards compatible with OA to Arma 2 mods

[JoyRiderUSA 10]

So I went out bought the game, and moved alot of my favourite unit mods from arma 2 addons to OA Expansion/Addon folder. I went in game and went under U.S. [Faction] and looked for my mods and they were not under that class. So I selected the default U.S. rifleman Operation Arrowhead soldier and set him as player and then I went under the class "empty" and there was my unit mods sitting under empty and 1. I couldnt play as them 2. when I placed them on the editor map and went in game they werent even there. Also I downloaded a kiowa helicopter mod and it wouldnt let me use it because of some USMC_soldier error. So theres no backwards compatiability with mods for the new expansion?

[Murklor 10]

Yes there is, except when there isnt.

See the addon forum for working mods. Many mods rely on Arma2 content which obviously have to be changed if its supposed to work in OA.

[Kristian 47]

You may be able to use the kiowa this way:

Place yourself in the map as US Army Pilot

Doubleclick > emtpy > find the kiowa warrior.

That then hit preview, you should be able to see the kiowa and board it as pilot.

[sniper pilot 36]

Friend who has OA is telling me that your going to need AmA2 installed with OA to have A2 addons work in OA... And I assume that you will need to run OA with A2 too. (if that makes sense.)

[Laertes 10]

Any addon that uses an A2 specific classnames/resources (such as USMC_Soldier) won't work in OA if you don't have A2 installed.

Edited July 4, 2010 by Laertes
To clarify.

[eble 3]

Hi,

I'm aware of this error for OA users only (assumed everyone would have A2 :) )

Revised OA specific Kiowa now released.

Edited July 4, 2010 by Eble

[zenith777 0]

So I went out bought the game, and moved alot of my favourite unit mods from arma 2 addons to OA Expansion/Addon folder. I went in game and went under U.S. [Faction] and looked for my mods and they were not under that class. So I selected the default U.S. rifleman Operation Arrowhead soldier and set him as player and then I went under the class "empty" and there was my unit mods sitting under empty and 1. I couldnt play as them 2. when I placed them on the editor map and went in game they werent even there. Also I downloaded a kiowa helicopter mod and it wouldnt let me use it because of some USMC_soldier error. So theres no backwards compatiability with mods for the new expansion?

You should use modfolders instead, because the OA has expansion management and all the folders that have addons folder inside them on the ArmA 2 directory are listed as an expansion. Simply create a folder inside ArmA 2 directory and then create addons folder inside it and add your addons to there, that way you can disable the mods if you sometimes want and can't accidentally f**k up OA stuff.

[Fox '09 14]

I think BI or someone should release a patch/addon or something for this. It's only classes etc and weapons.. right? even if it was custom weapons, I'm sure people wouldn't download a 100mb pack or so to get all addons working.

[STALKERGB 6]

Yeah this is a problem with my units at the moment too, if you don't have ARMA2 installed the units who use "USMC_Soldier" as inheritence won't work. If I change it to "US_Soldier_EP1" then people with just ARMA2 wont be able to use my units.

Unfortunately unless I write my own base class I don't think there is any common classname for an infantry unit in both OA and A2. Will probably just need two configs...

[Laertes 10]

Yeah this is a problem with my units at the moment too, if you don't have ARMA2 installed the units who use "USMC_Soldier" as inheritence won't work. If I change it to "US_Soldier_EP1" then people with just ARMA2 wont be able to use my units.

Unfortunately unless I write my own base class I don't think there is any common classname for an infantry unit in both OA and A2. Will probably just need two configs...

Just out of curiosity, why not write your own base-class?

[STALKERGB 6]

Just out of curiosity, why not write your own base-class?

Becuase I'm very bad at writing configs,

From my understanding,

A base class would inherit "SoldierWB" which is present in both ARMA2 and OA (and ARMA1 IIRC). So all good there.

I'd then need to define a heck of alot of parameters that I've got no experience of doing so this would delay any new release of anything and could end up with wierd results due to my inexperience.

Classes within the base class would also need to be added (hitpoints, talktopics etc).

I did have a quick go but after what I though would work got an error on launch.

There would also be a number of parameters that use classnames of things only in OA so A2 users would (probably) get an error, as an example:

identityTypes[] = {"Language_EN_EP1","USMC_Glasses","Head_USMC"};

"Language_EN_EP1" AFAIK is only defined in OA so i guess this would cause an error in A2. And if I remove it from the config then you'd probably lose some of the functionality/features in OA.

[Laertes 10]

Becuase I'm very bad at writing configs,

From my understanding,

A base class would inherit "SoldierWB" which is present in both ARMA2 and OA (and ARMA1 IIRC). So all good there.

I'd then need to define a heck of alot of parameters that I've got no experience of doing so this would delay any new release of anything and could end up with wierd results due to my inexperience.

Classes within the base class would also need to be added (hitpoints, talktopics etc).

I did have a quick go but after what I though would work got an error on launch.

There would also be a number of parameters that use classnames of things only in OA so A2 users would (probably) get an error, as an example:

"Language_EN_EP1" AFAIK is only defined in OA so i guess this would cause an error in A2. And if I remove it from the config then you'd probably lose some of the functionality/features in OA.

Fair enough. That's a selection of very good reasons.

[STALKERGB 6]

I mean its certainly the better option for me to have my own base class, for a start I could have one config in for both games, and hopefully at some point I'll find a setup that works in both A2 and OA on their own, I guess initially I'll just have a seperate config for people only with ARMA2 and one for people who own OA, should work fine (i hope!).