HOME It won't shoot even if I hovered right in front of it. However, the T80 in MFCTI shoots AH64 so I guess I could use that unit but is there another way?
It won't shoot even if I hovered right in front of it. However, the T80 in MFCTI shoots AH64 so I guess I could use that unit but is there another way?
OFP's standard tanks are configured to not target aircraft at all. I'm guessing that MFCTI has a modified addon version or configuration that changes this.
Without modifying the addon itself or running a mod that globally changes this, I don't think it's possible to change the vehicle's attribute by an external script in the mission.
But it shoots certain choppers like AH1 and OH-58, but not CH-47, UH60 and AH-64.Originally Posted by [b
You're right. Just tested this out.But it shoots certain choppers like AH1 and OH-58, but not CH-47, UH60 and AH-64.
Again, my assumption is that something in the config of choppers not being targeted was left out. Hence the inconsistency. But it shouldn't be that way.
I'm also assuming the T-80 is not at fault here but the config of the aircraft in question.
But I'll let the experts come in here to tell you.
Interesting, i tried several things and now after first suspecting the model itself, i noticed that the weapon used makes the difference.
I copy/pasted the entire content of the AH1 Cobra class definition (even the weapon/magazine) in the place of the content of the UH60 class definition, leaving only the displayname and namesound lines intact (so i can make the difference in the mission editor).
This UH60 use the 3D model of the AH1 too
A quick test show me that the T80 engage this UH60
Now, leaving always the AH1 values in the UH60 class definition, this time i put back the line model="uh_60"; , to get the UH60 to use again the 3D model of the UH60 instead of the AH1 one.
A quick test show me that the T80 does not engage this UH60
So in the case of the UH60, i can only suspect the model itself
To confirm this guess, i edit this time the AH1 cobra definition, only replacing the line model="ah1_cobra"; by the line model="uh-60";
And, a quick test show me that the T80 does not engage this AH1 cobra that is shaped by the UH60 3D model anymore.
So it seems there is a value specific to the 3D model of the UH60 included in the model itself (as i read several values are included in the model themselves) that makes the T80 machinegun not caring about the UH60, or some hardcoded function recognizing the UH60 and making it not important for the T80 machinegun.
But we certainly can override this with some weapon definition change, as we know there is a East weapon that will engage everything flying : the Shilka weapon.
So to see if the weapon can override this model thing , let's do the experiment :
If i replace , in the T80 class definition those lines
weapons[]={"Gun120","MachineGun12_7"};
magazines[]={"Heat120","Shell120","MachineGun12_7"};
by those ones
weapons[]={"Gun120","ZsuCannon"};
magazines[]={"Heat120","Shell120","ZsuCannon"};
A quick test will show me that T80 -engage- the UH60 using a UH60 model.
Yeah, that is a success.
the ZsuCannon is the Shilka weapon, so if you modifiy the MachineGun12_7 class definition used by the T80 to +/- match the ZsuCannon class definition values, maybe you should finally have a T80 firing its MachineGun12_7 to anything that fly.
That is certainly what the MFCTI T80 do, it will certainly use a modified MachineGun12_7 to hit everything that is flying.
OFP rocket scientists!
You gotta love 'em!
Posting Permissions
Reply With Quote