Habu_69

Many threads on this issue have occurred in the past. Do a search. Testing reveals that the "random" features of the ME are biased, but alternatives have been proposed.

Markpoints ARE waypoints. I guess the pilot can record the coordinates, then create a new waypoint in the flight plan sequence. Unaware of any more convenient method.

I have read Chuck's Guide on the AG radar. Still don't quite get it all. Chuck says TGP can be slaved to AG radar, but does not show how. Does not seem to follow same procedure as TGP interaction with AA Radar. We badly need a tutorial on the AG radar, as well as its interaction with the TGP..

Try setting the SU-27 group main TASK to "nothing".

You can also use this timer function timer.scheduleFunction( NewBandit, {}, timer.getTime() + 5 ) -- NewBandit is some function. Delays action by 5 sec.

I am no Moose expert, but I think this is your problem: RED_CAP_1_SPAWN, When you spawn a new group object, you give it the same variable name, which confuses the API. Try using RED_CAP_1:Spawn() and RED_CAP_1:GetName(), if you need it.

I believe the radar "SET" function is one of those that can be pre-programmed by the pilot and entered into the MC by the data cartridge (which we do not currently have).

FYI the Moose Use Guide (https://github.com/FlightControl-Master/MOOSE_GUIDES) has much information about the the workings of the DCS scripting engine. Good reference even if you do not wish to use the Moose scripting environment.

Number of AG weapons to release per pickle. Refer to Chuck's Guide.

Interesting. My experience is consistent through many missions. Must be some differences in our procedures. I normally set 4 PP targets, then use TGP to designate for the 4 TOO's.

Here is another "issue". May be realistic, maybe not. I am not a real fighter pilot, but I play one on my computer. Sometimes I load 8 JDAMs/JSOWs and pre-plan targets for 4, on say STA 2 and 8. After releasing on PP targets, in order to use TOO for the remaining weapons, STA 3 and 7, one must deselect the weapon on STORES page OSB 6, reselect STORES, reselect the weapon OSB 6, set fuzing, set the stations for TOO mode, etc. Otherwise the STA 3 and 7 weapons will not release on a designated target.

Need a communications menu option to request repeat marshalling instructions.

TACAN faults in MP still persist. While in marshall stack astern supercarrier TACAN just stops working and no amount of fiddling restores its function. The HSI bearing pointer just starts spinning incessantly. ICLS is not affected. Makes marshalling impossible when you don't know DME. Can supply track file if needed.

A group with main TASK of SEAD will engage any AD units it detects, regardless of other waypoint target assignments. Any air group will also abort its mission under certain threat conditions. So try this: Set group's main TASK as NOTHING, PINPOINT STRIKE or maybe GROUND ATTACK. Load it only with the weapon you wish it to use Set REACTION TO THREAT to NO REACTION Set waypoint PERFORM TASK to ATTACK GROUP and set weapon parameters.

Your DCS log is your very great friend when troubleshooting scripts. Details in Moose User Guide.

@FubarBundy has it. This is the most common error by new Moose scripters. You define the spawn object, but never spawn it. Have you read the Moose User Guide that pretty well covers all the most common errors? You will find a link on the Moose Discord.

I assigned wing fold/unfold to a 2-position switch on the Warthog Throttle. Works well.

The current developers/caretakers of the Moose scripting environment have many of the answers you seek. Contact them on the Moose Discord.

And oc Moose has several similar methods for various DCS objects, so take your pick. for example: UNIT:IsInZone( zone)

I think Nick Grey acknowledged in a recent interview that AI improvement is critical ED's dynamic campaign development. As to timeframe.........???

If you wish to use scripting for creating DCS missions, I highly recommend using the Moose scripting environment, due to its powerful methods and ongoing development. Following is a Moose script to accomplish most of what you want: From_Grp = UNIT:FindByName( "B17" ) -- Instantiate units of interest To_Grp = UNIT:FindByName( "P51" ) -- GROUP instead of UNIT works also SCHEDULER:New( nil, function() To_GrpCoord = To_Grp:GetCoordinate() -- Get To_Grp group coordinate From_GrpCoord = From_Grp:GetCoordinate() To_GrpDist = From_GrpCoord:Get2DDistance( To_GrpCoord ) -- Returns distance in meters if To_GrpDist <= 14000 then -- Optional message conditions. 14000 m ~ 7.2 NM To_GrpBR = To_GrpCoord:ToStringBR( From_GrpCoord, _SETTINGS:SetImperial() ) WelcomeMsg = "Colt 1, Springfield 3. Visual, bearing ".. To_GrpBR MessageTo_Grp = MESSAGE:New( WelcomeMsg, 15, nil ):ToAll() Scheduler:Stop() end end, {}, 1, 1 -- Freq must be high to get accurate BR message ) You can easily add the altitude function and replace To_GrpDist <= 14000 with GroupInZone. This script stops the scheduler after the first message, but you may wish to make modifications to send subsequent messages when other groups enter the zone.

Experiment with the primary group tasking. That parameter has a major effect on AI attack behavior.

Hmmm. Tx for reply. Only happened once while JSOWs loaded. Will have to investigate further.

When will the alignment bars become functional?