FRL Airforce Addons release thread

[pre-Vet]

- Click on the map
- Click Mark
- Exit
- Lock onto the new GPS/INS target, TAB usually
- Fire.

Is there a way to get it locked immediatly after closing the gps window? at this time I need to fly over the target to lock and than be able to fire.

[Derbysieger]

If the target is within visual range you should be able to lock on immediatly. Works fine for me.

[[FRL]Myke]

Is there a way to get it locked immediatly after closing the gps window? at this time I need to fly over the target to lock and than be able to fire.

Make sure you fly high enough (1000m+) and from an angle where no topology blocks the sight of line to the target area.

As already said, it uses the BIS lasertargeting simulation, therefor it shares it's limitations, which one is that you got to have line of sight to the target.


@Derbysieger
if the irScanRangeMax of the planes config is big enough, also BVR locking works as long the target is not blocked behind topology or other objects.

Also if targeting objects, better place the marker at the buildings edge, not in the middle of it. The building could hide the laserobject created and therefor making lock impossible or only from certain angles/distances.

The systems has it flaws so if you could do a better, go ahead.


:EDITH:


Uploaded with ImageShack.us

[.kju [PvPscene]]

The glt_missilebox_config.pbo causes:

Updating base class ->A10, by ca\air_e\config.bin/CfgVehicles/A10_base/

Reason it lacks CAAir_E in requiredAddons. Thanks.


Edit: While you are at it also remove access = 1; and class PreloadBanks{}; from cfgAddons.

[[FRL]Myke]

The glt_missilebox_config.pbo causes:

Updating base class ->A10, by ca\air_e\config.bin/CfgVehicles/A10_base/

Reason it lacks CAAir_E in requiredAddons. Thanks.


Edit: While you are at it also remove access = 1; and class PreloadBanks{}; from cfgAddons.

Will add CAAir_E to requiredAddons, thanks.

About the other, what problems does it cause?

[Mandoble]

After installing the 3.2 I got BIS Su34s with the following weird weapons configuration instead of the BIS one: GLT_Ch29LauncherLaser + GLT_Ch29Launcher_IR

These weird weapons are not BIS and are not the correct GLT ones (GLT_CH29T_Launcher and GLT_CH29L_Launcher, which are already supported for the GLT Su34 variants).

So installing 3.2 is ATM rendering this missile box incompatible with MMA at least for the BIS Su34. Removing glt_missilebox_config.pbo fixes the problem, so I guess the problematic config is there.

[[FRL]Myke]

These are parts of the now included airweapons replacement pack. Sadly BIS planes aren't (visually) compatible with Missilebox weapons, therefor the special variants.

I can switch back the SU-34 to default BIS and make this variant separately, no biggie.

[mankyle]

Myke

One comment

THis news say that Raytheon is going to restart the production of the AG;-65 E /Laser Guided Maverick

http://www.defenseindustrydaily.com/...issiles-05397/

Do you plan to add a laser guided version of the Maverick?
It could be quite useful

Just a suggestion

Anyway

GOOD WORK!!!!

[Mandoble]

If there is no way to use missilebox variants with the BI Su34, then it would be definitively better to keep with the original BI config for it as we already have the other GLT Su34s fully compatible with the missile box weapons, or just create another version of the BI Su34 with that GLT_Ch29LauncherLaser + GLT_Ch29Launcher_IR configuration (same as you did for A10 and AV8)

Anyway, GLT Ch29T/L dont look that bad loaded in the BI Su34, and as soon as you get in your plane, how these missiles look doesnt matter anymore.

[[FRL]Myke]

....and as soon as you get in your plane, how these missiles look doesnt matter anymore.

Please speak for yourself.
For me this looks horrible, even more as it is unnecessary if BIS spent one minute more to think about proxy weapons.

However, already switched back default BIS planes to default loadout (model replacement remains but this doesn't affect magazine and/or weapon classnames) and added the other variant as additional planes.


@Mankyle

Good suggestion, expect AGM-65E in the next update available.