The turret/path thing for helo weapons

[Nixer6]

I am trying to rearm a uh60mg when it lands with a trigger and little script.

Does anybody have a clue on how to do the 2nd minigun? I can only rearm the first one.

I've looked everywhere for info on turret/path with no luck.

[Planck]

The first Uh60 gun has the class M134 with the magazine name of "2000Rnd_762x51_M134", the second gun has the name M134_2 and uses the same magazines.

Hopefully this is what you needed to know.


Planck

[Nixer6]

Thanks

I had found that. But it seems that when you try to "addMagazine" to the helo, it only reloads the first gun.

I'll test it again and give an example script. Kinda in the weeds with work right now.


Edit:

Another thing....has anybody figured out how to have an AI man the second gun? What position is it? It's not Commander, tried that.

[Nixer6]

Ok found this at the Biki.

moveInTurret in the ArmA ComRef

here 2 examples : Boat1 is an "RHIB 2 Turrets"

Soldier MoveInTurret [Boat1,[0]]

result : Soldier will mount into the front turret of the boat

Soldier MoveInTurret [Boat1,[1]]

result : Soldier will mount into the Back turret of the boat

So I guess maybe that the 2nd gun of UH60 would be Soldier MoveInTurret [heli1,[1]] or something like that. Still doesn't solve the 2nd gun's ammo problem though.

Is there a decompressed config around anywhere?

[hoz]

You can use eliteness to unpbo and unrAP the config.

[Nixer6]

Thanks Hoz.

Been wanting to take a peek at it. I'll probably get more confused, lol.

[Nixer6]

Well I can de PBO the pbo but I still have a config.bin which is what I think I need to look at.

What takes apart .bin files??

[Planck]

Eliteness will do that for you as well.........just double click on the config.bin in the eliteness window and it will display the file in readable form for you in the main display window.

You can save it from there.


Planck

[Nixer6]

I cannot get Eliteness to work on my machine...two different downloads from different places.

I get a Windoze error with both. "Windows has encountered a problem and has to close Eliteness" or some such stuff.

WinXP SP2 here. First line hardware.

Arma unPBO works fine on PBO's but no luck on the .bin

[Planck]

Which version of Eliteness are you using, the latest, AFAIK, is 2.12.

Anyway, when extracted and put...wherever you like......the folder should have at least Eliteness.exe, DePBO.dll and the readme inside it.


Planck

[Nixer6]

I've got 2.08.

I just tried the one here...also 2.08

Eliteness MFC Application has encountered a problem and needs to close.  We are sorry for the inconvenience.

Same error?

[JasonO]

The original question.. was it answered?

Have you tried adding the magazine to the weapon, selecting the next weapon with selectweapon and then add the magazines again?

[Nixer6]

No...I haven't tried that. It makes sense and it might work. Thanks

Will get back when I try it. Busy with hardware for the next day or two.


#EDIT-removed the unnecessary quote  h-

[h-]

Nixer6, don't quote the entire previous post you're replying to..

[Nixer6]

I had forgotten this for awhile.

I solved the problem. I actually was able to get two AI gunners to man the guns in a UH60 mg. 

Code: [Select]

heliGunner0 assignAsGunner heli;
heliGunner1 assignAsGunner heli;

heliGunner0 moveInTurret [heli, [0]];
heliGunner1 moveInTurret [heli, [1]];

But now I had a new problem. 

One of the gunners kept jumping out! I decided to look at the air.pbo, to see if the config had any hints.

Code: [Select]

class Turrets : Turrets {
class MainTurret : MainTurret {
body = "mainTurret";
gun = "mainGun";
<snip>
weapons[] = {M134};
magazines[] = {"2000Rnd_762x51_M134"};
gunnerName = $STR_POSITION_CREWCHIEF;
<snip>
gunnerAction = "UH60_Gunner";
gunnerInAction = "UH60_Gunner";
primaryGunner = 1;


class RightDoorGun : MainTurret {
body = "Turret_2";
gun = "Gun_2";
<snip>
                                           weapons[] = {M134_2};
gunBeg = "muzzle_2"; // endpoint of the gun
gunEnd = "chamber_2"; // chamber of the gun
primaryGunner = 0;



Now that tells me that the primary gunner is the first turret....I think. Bottom Line...

I swapped turret positions for the gunners and now it works fine. 

Code: [Select]

heliGunner0 moveInTurret [heli, [1]];
heliGunner1 moveInTurret [heli, [0]];
So I guess turret 0 is the secondary gun position. I had tried all sorts of combinations, moveInCommander, assignAsCommander blah, blah.

Still investigating.

[Spooner]

The "gunner" (as far as moveInGunner, gunner, assignAsGunner are concerned) always lives in the primary turret. On the blackhawk, this is the crew chief position. There can only ever be one gunner, as such, regardless of the number of turrets (blame BIS for not thinking that secondary turrets might be useful until ArmA). The secondary turret position actually has nothing to do with being a gunner so I think you'd need to assignAsCargo (or not assign) to get someone into that position. Anyway, I think that explains why your were having problems based on the order you assigned people as gunner: the second guy being made the gunner will have unassigned the first guy.

[Nixer6]

AssignAsCargo worked...but was unpredictable.

Sometimes the 2nd gunner would again just jump out when anyone else got on board.

that explains why your were having problems based on the order you assigned people as gunner - the second guy being made the gunner will have unassigned the first guy.

Yep. That's what reading the config helped me to figure out. I believe I also tried not assigning the 2nd gunner...the chopper would just sit there and not move.

I was just happy to make it work. The ComRef here and on the Biki are a little confusing regarding MoveInTurret.