Jump to content

Kyridious

Members
  • Posts

    62
  • Joined

  • Last visited

Posts posted by Kyridious

  1. Hi Folks,

     

    I'm building a WWII mission and would like to add a target (vehicle or building) that is susceptible to HVAR but not guns (MG).

     

    Has anyone compiled a list of target types and what type of ordinance is required to damage / destroy?

     

    Cheers,

    Andrew

  2. Not there yet, but the following code allows a normal (late activation = false) group to follow a spawned leader:

     

    local Plane1       = SPAWN:New( "Plane1" )
    local Plane1_spawn = Plane1:Spawn()	
    local Plane1_group = Group.getByName(Plane1_spawn:GetName())
    
    local FollowDCSTask = {
    id = 'Follow',
    params = {
    	groupId = Plane1_group:getID(),
    	pos = POINT_VEC3:New( -100, 0, 100 ):GetVec3(),				
    	lastWptIndexFlag = false,
    }    
    }
    Group.getByName('Plane2'):getController():setTask(FollowDCSTask)
    

  3. Good Morning,

     

    I am trying to task one air unit to follow another using the default DCS "Follow" task behavior. This is trivial to accomplish in the mission editor without scripting. Simply select the A/C, add a "Follow" Task, select the target group from the drop down menu and provide the desired offset vector.

     

     

    My problem is applying this to spawned units, or any unit with Late Activation. Below is loosely what I want to do:

     

    Mission Editor: Plane1 and Plane2 groups exist in mission and are set to late activation

     

    Lua executed in response to an event:

     

    --Create Spawn Groups

    spawnPlane1 = SPAWN:NEW("Plane1")

    spawnPlane2 = SPAWN:NEW("Plane2")

     

    --Spawn Groups into world

    groupPlane1 = spawnPlane1:Spawn()

    groupPlane2 = spawnPlane2:Spawn()

     

    --Create Task for plane2 (follow groupPlane1 at Vec3 offset) (Note: I think I need to be using controllers here)

    --i.e. cntrlPlane1 = groupPlane1.getController(groupPlane1)

    followTask = groupPlane2:TaskFollow( groupPlane1, Vec3 )

     

    --Activate Task (Either PushTask/SetTask?)

    groupPlane2:pushTask(followTask)

     

    The furthest I've gotten is that old orders defined in the ME (I.e. an orbit task) get cleared. However, I see no indication that the new follow task is being applied.

     

    Any Thoughts?

  4. This was my fear, I really need a generic solution that isn't dependent on the mission.

     

    I have a proven mechanism for manipulating cursor location ("sticky cursor") based on viewport orientation, but its rather CPU intensive and sensitive to changes in FOV (and any display property that can not be exported). That said, I could use this as a fall back option.

     

    Thanks for your input.

  5. Does anyone know if it is possible to dynamically control Cockpit Highlights? These are the bounding boxes frequently used in the DCS training missions. I want to highlight the switch/button as it is being manipulated by the pilot.

     

    Is there is a LUA command to control this behavior in real time by a 3rd party application? Or do cockpit control highlights need to be built in to the mission itself?

     

    Cheers,

    Andrew

×
×
  • Create New...