Xeno426

So, I liked this idea, but I don't like the idea of having all the different versions for different pods, so I went and made a workaround. Unfortunately, the best I could do was create a new weapon in the db_weapons_data.lua that rotated the AIM-7M missile and then assign that to the forward Sparrow wells. To get this to work, you need to add the following code under [CAT_AIR_TO_AIR] to your db_weapons_data.lua file. { CLSID = "AIM7M_F4", Picture = "aim7m.png", displayName = _("AIM-7M"), wsTypeOfWeapon = {4, 4, 7, 21}, attribute = {4, 4, 32, 112}, Count = 1, Cx_pil = 0.0006, Weight = 230, Elements = { [1] = { Position = {0, 0, 0}, ShapeName = "F4-PILON", }, [2] = { DrawArgs = { [1] = {1, 1}, [2] = {2, 1}, }, -- end of DrawArgs Position = {0, 0, 0}, ShapeName = "AIM-7", Rotation = {45,1.3,0.4}, }, }, -- end of Elements }, Then this lua of the F-4E will work fine, though old missions will still have wonky AIM-7M placement; to fix it every mission with an F-4E will need its loadout changed. Just assign the AIM-7M for pylons 3 and 7 again. F-4E.lua

If they truly want them removed, I can do that as well. [EDIT] Here's the versions with them removed. Works just as well. [EDIT2] Just to be clear, these differ from my previous ones in that my previous edits require that the LANTIRN be available on the F-16, while these ones do not. Details: F-16A.lua F-16A-2.lua F-16C.lua F-16C-2.lua

You'll probably need to clean out some of the extra weapons there, though. I added some extra munitions for personal use which may or may not be completely accurate. Incidentally, is there a command similar to attach_point_position that works on rotation?

I managed to get this to work for both the LANTIRN and LITENING pods without issue. I'm not including the F-16A.lua file because it doesn't have any pods in the first place. Keep in mind I've got some extra weapons added to these as well. F-16A-2.lua F-16C.lua F-16C-2.lua

*sigh* Well, I knew coming into this that the AA system wasn't nearly as robust as that in Falcon 4.0, where I can be ambushed by something like an S-125 site that turns on when you're within 20nm and almost instantly fires because it's been using data from a distant search radar for information. The fact we can't even hack a good facsimile of that awesome system is depressing.

Wouldn't it be possible to modify the position value of the pod itself in the db_weapons_data.lua file?

What's the difference between "OPEN_FIRE_WEAPON_FREE" and "WEAPON_FREE"?

Nice mission. I don't suppose you could add Mi-8MTV2 and Ka-50 support, could you?

Sadly I wouldn't know how to go about customizing that script to do what I want, which is one of the big reasons I'm trying to avoid an LUA solution. I'm surprise nobody has done this before. Sure thing, here's a version of the mission with all extraneous items removed. AA Trigger Test.miz

LUA scripting is the only way to do this? I don't want to suppress units, I just want my AA to not attack units that aren't in a trigger zone (forcibly reducing the engagement area of the AA).

I'm trying to set up an AA unit to toggle its ROE between weapons hold and weapons free based upon whether or not enemy units are within a trigger zone. I created two Switched Condition triggers; one turns on flag 51 when any part of the enemy coalition is in the zone, and the other turns off flag 51 when all of the enemy coalition have left the zone. I've tried using the Advanced Waypoint Actions to set the two different ROEs with a conditional modifier; for Weapons Free, I selected "Is User Flag" for 51 and selected the box after "Is". For the Weapons Hold option, I did the same thing except the box after "Is" was left unmarked. The end result was that the unit never fired. I then tried to put both options in the "Triggered Actions" section, with both "ROE = Weapons Hold" and "ROE = Weapons Free" being active. I then added to the Switch Condition trigger an AI Task Push to each condition; in the trigger for enemy in the zone, the Weapons Free is pushed, while in the trigger for enemy leaving the zone the "Weapon Hold" condition is pushed. This didn't work either. Any ideas on what I'm doing wrong?

Wasn't an Mi-24 module already announced? It was in one of the videos, though they didn't say what version it was going to be.

Agreed. Finding targets in a REDFOR aircraft is quite difficult, and it would be much easier if there was ground assistance.

The Su-35 is another version of the Su-27. :P And besides, the Su-27SM has a better chance of having information on its systems available than the Su-35, which is in service and likely still has a lot of classified systems.

The problem with the MiG-25 is that it's a one-trick pony. It can intercept, and that's it. No dogfighting (unless you dogfight with a bomber, maybe), only four missiles, no gun, and heavy reliance on GDI.

Wouldn't be as much of an issue of all the missiles didn't try to hit the same pinpoint location on the target ship.

Wasn't the Yak-9 more prolific and a generally better design?

I was thinking in terms of performance. There's going to be lots of those little babies on release, and reducing poly count on them would reduce overhead.

Might those bomblets be a little too high poly?

Quite a few nations tend to be very tight-lipped about actual capability of their military systems, even twenty years after the system has been removed from service. Denmark and the UK come to mind beyond just Russia.

Why is that?

I just want to fly some kind of proper PGM-capable Russian multi-role fighter.

How would you model an aircraft that never went into production, was integrated with weapons, and was just a technology demonstrator?

So I assume you're using an external script and not just the ingame triggers. How would I go about doing this? I'm just trying to get four different air groups to cycle through respawning.

Not quite mission editor specific, but I'd really like to be able to enforce specific label settings on a mission-by-mission basis. For example, if I put \Config\View\Labels.lua into my .miz file, I'd like that labels file to be enforced on all client machines.