Jump to content

Making a script that runs on MP SP etc if player dead or player aircraft shot to stop telemetry or run file? How to?

trigen

By trigen
in Mission Editor

 Share

Recommended Posts

trigen

trigen

Posted
Posted

Hello

 

Im trying to figure out how i can make a if else condition so that i stop an export script or execute a autohotkey file when the player is dead, the aircraft damaged etc. This must execute regardless of mission MP SP and so on.  I find it really hard to find any proper information on the triggers and how to do it but i remember i ran a dofile autohotkey file 10 years back on server restart so it should be possible 

  

--[[

DCS LUA SCRIPT FOR FLYPT MOVER 2.9.8
====================================
Version from 18 04 2020
This file should be placed in the folder "C:\Users\YOUR USERNAME\Saved Games\DCS\Scripts\Hooks".
If the "Hooks" folder doen's exist, create it.

]]--

local FlyPT_Mover_Callbacks = {}

function FlyPT_Mover_Callbacks.onSimulationStart()

    log.write('FlyPT_Mover', log.INFO, "Starting data export")
    package.path = package.path..";.\\LuaSocket\\?.lua"
    package.cpath = package.cpath..";.\\LuaSocket\\?.dll"
    socket = require("socket")
    DCSClient = socket.udp()
    DCSClient:settimeout(0)
    DCSIP = "127.0.0.1"
    DCSPort = 4124 -- If changed, the source should match this value
    DCSClient:setpeername(DCSIP, DCSPort)
        
end

function FlyPT_Mover_Callbacks.onSimulationFrame()

    local acceleration = Export.LoGetAccelerationUnits()  
    local speed = Export.LoGetVectorVelocity()
    local pitch, roll, yaw = Export.LoGetADIPitchBankYaw()
    local rotationSpeed = Export.LoGetAngularVelocity()
    local altitude = Export.LoGetAltitudeAboveGroundLevel()
    local o = Export.LoGetSelfData()
    --[[
    LatLongAlt.Lat -- Latitude in degress
    LatLongAlt.Long -- Longitude in degress
    LatLongAlt.Alt -- Altitude in meters MSL
    Heading -- Heading in radians
    Pitch -- Pitch in radians
    Bank -- Bank in radians
    ]]--
    
    local mechInfo=Export.LoGetMechInfo()
    --[[
    gear          = {status,value,main = {left = {rod},right = {rod},nose =  {rod}}}
    flaps          = {status,value}  
    speedbrakes   = {status,value}
    refuelingboom = {status,value}
    airintake     = {status,value}
    noseflap      = {status,value}
    parachute     = {status,value}
    wheelbrakes   = {status,value}
    hook          = {status,value}
    wing          = {status,value}
    canopy        = {status,value}
    controlsurfaces = {elevator = {left,right},eleron = {left,right},rudder = {left,right}}
    ]]--
    
    local alarm = Export.LoGetMCPState()
    --[[
        returned table keys for LoGetMCPState():
        "LeftEngineFailure"
        "RightEngineFailure"
        "HydraulicsFailure"
        "ACSFailure"
        "AutopilotFailure"
        "AutopilotOn"
        "MasterWarning"
        "LeftTailPlaneFailure"
        "RightTailPlaneFailure"
        "LeftAileronFailure"
        "RightAileronFailure"
        "CanopyOpen"
        "CannonFailure"
        "StallSignalization"
        "LeftMainPumpFailure"
        "RightMainPumpFailure"
        "LeftWingPumpFailure"
        "RightWingPumpFailure"
        "RadarFailure"
        "EOSFailure"
        "MLWSFailure"
        "RWSFailure"
        "ECMFailure"
        "GearFailure"
        "MFDFailure"
        "HUDFailure"
        "HelmetFailure"
        "FuelTankDamage"
    ]]--


    local stall = 0
    for k,v in pairs(alarm) do
        if k == "StallSignalization" then 
            if v == true then
                stall = 1
            end
        end
    end

    -- local engine = LoGetEngineInfo()
    --[[
    RPM = {left, right},(%)
    Temperature = { left, right}, (Celcium degrees)
    HydraulicPressure = {left ,right},kg per square centimeter
    FuelConsumption   = {left ,right},kg per sec
    fuel_internal      -- fuel quantity internal tanks    kg
    fuel_external      -- fuel quantity external tanks    kg    
    ]]--

    -- The FlyPT Mover uses Z for vertical and Y to the front
    -- That's the opposite in DCS
    -- Values sent in one string, separated by spaces    
    socket.try(DCSClient:send(
    --               00   01   02   03   04   05   06   07   08   09   10   11   12   13   14   15   16   17   18   19   20   21   22   23
    string.format("%.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f", 
    acceleration.x,                             -- 00 = Lateral acceleration (G)
    acceleration.z,                             -- 01 = Lateral acceleration (G)
    acceleration.y,                             -- 02 = Vertical acceleration (G)
    speed.x,                                     -- 03 = Lateral speed (m/s)
    speed.z,                                     -- 04 = Longitudinal speed (m/s)
    speed.y,                                     -- 05 = Vertical speed (m/s)
    rotationSpeed.y,                             -- 06 = Rotation speed around y (yaw in rad/s)
    rotationSpeed.x,                             -- 07 = Rotation speed around x (roll in rad/s)
    rotationSpeed.z,                             -- 08 = Rotation speed around z (pitch in rad/s)
    o.Heading,                                     -- 09 = Yaw position (rad)
    o.Bank,                                     -- 10 = Roll position (rad)
    o.Pitch,                                     -- 11 = Pitch position (rad)
    Export.LoGetTrueAirSpeed(),                 -- 12 = Air speed (m/s)
    Export.LoGetAircraftDrawArgumentValue(1),     -- 13 = Front/Rear landing gear (0 to 1)?
    Export.LoGetAircraftDrawArgumentValue(2),     -- 14 = Turning landing gear (0 to 1)?
    Export.LoGetAircraftDrawArgumentValue(4),    -- 15 = Left landing gear (0 to 1)?
    Export.LoGetAircraftDrawArgumentValue(6),     -- 16 = Right landing gear (0 to 1)?
    Export.LoGetAltitudeAboveGroundLevel(),     -- 17 = Vertical position relative to ground (m)
    mechInfo.flaps.value,                         -- 18 = Flaps amount (%)
    mechInfo.gear.value,                         -- 19 = Delployed landing gear (%)
    mechInfo.speedbrakes.value,                 -- 20 = Speed brakes (%)
    mechInfo.canopy.value,                         -- 21 = Canopy open (%)
    stall,                                         -- 22 = Stall alarm (0 or 1)
    Export.LoGetModelTime()                     -- 23 = Time in seconds
    )))
end

function FlyPT_Mover_Callbacks.onSimulationStop()
    log.write('FlyPT_Mover', log.INFO, "Data export stopped")
    if DCSClient then
        DCSClient:close()
    end
end

DCS.setUserCallbacks(FlyPT_Mover_Callbacks)


 

1080 ti, i7700k 5ghz, 16gb 3600 cl14 ddr4 oc

  • 4 weeks later...
J-1775

J-1775

Posted
Posted

It probably answers only part of your question, but in case you overlooked it it may help: there's a hot key in FlyPT's option to start/stop all output. I trigger it with a Voice Attack command using the last words before I crash: «O my god»...🙃
flypt options.jpg

trigen

trigen

Posted
  • Author
Posted
On 8/26/2021 at 2:03 PM, J-1775 said:

It probably answers only part of your question, but in case you overlooked it it may help: there's a hot key in FlyPT's option to start/stop all output. I trigger it with a Voice Attack command using the last words before I crash: «O my god»...🙃
flypt options.jpg


Thank you I do use those functions. But its those pesky ones you dont see that gets you 😛  So its better to have a trigger in the script that detects it as soon as it hits and before the rig throws you out. 

1080 ti, i7700k 5ghz, 16gb 3600 cl14 ddr4 oc

  • 1 year later...
DerKlausi

DerKlausi

Posted
Posted
On 8/2/2021 at 12:29 PM, trigen said:

Hello

 

Im trying to figure out how i can make a if else condition so that i stop an export script or execute a autohotkey file when the player is dead, the aircraft damaged etc. This must execute regardless of mission MP SP and so on.  I find it really hard to find any proper information on the triggers and how to do it but i remember i ran a dofile autohotkey file 10 years back on server restart so it should be possible 

  

--[[

DCS LUA SCRIPT FOR FLYPT MOVER 2.9.8
====================================
Version from 18 04 2020
This file should be placed in the folder "C:\Users\YOUR USERNAME\Saved Games\DCS\Scripts\Hooks".
If the "Hooks" folder doen's exist, create it.

]]--

local FlyPT_Mover_Callbacks = {}

function FlyPT_Mover_Callbacks.onSimulationStart()

    log.write('FlyPT_Mover', log.INFO, "Starting data export")
    package.path = package.path..";.\\LuaSocket\\?.lua"
    package.cpath = package.cpath..";.\\LuaSocket\\?.dll"
    socket = require("socket")
    DCSClient = socket.udp()
    DCSClient:settimeout(0)
    DCSIP = "127.0.0.1"
    DCSPort = 4124 -- If changed, the source should match this value
    DCSClient:setpeername(DCSIP, DCSPort)
        
end

function FlyPT_Mover_Callbacks.onSimulationFrame()

    local acceleration = Export.LoGetAccelerationUnits()  
    local speed = Export.LoGetVectorVelocity()
    local pitch, roll, yaw = Export.LoGetADIPitchBankYaw()
    local rotationSpeed = Export.LoGetAngularVelocity()
    local altitude = Export.LoGetAltitudeAboveGroundLevel()
    local o = Export.LoGetSelfData()
    --[[
    LatLongAlt.Lat -- Latitude in degress
    LatLongAlt.Long -- Longitude in degress
    LatLongAlt.Alt -- Altitude in meters MSL
    Heading -- Heading in radians
    Pitch -- Pitch in radians
    Bank -- Bank in radians
    ]]--
    
    local mechInfo=Export.LoGetMechInfo()
    --[[
    gear          = {status,value,main = {left = {rod},right = {rod},nose =  {rod}}}
    flaps          = {status,value}  
    speedbrakes   = {status,value}
    refuelingboom = {status,value}
    airintake     = {status,value}
    noseflap      = {status,value}
    parachute     = {status,value}
    wheelbrakes   = {status,value}
    hook          = {status,value}
    wing          = {status,value}
    canopy        = {status,value}
    controlsurfaces = {elevator = {left,right},eleron = {left,right},rudder = {left,right}}
    ]]--
    
    local alarm = Export.LoGetMCPState()
    --[[
        returned table keys for LoGetMCPState():
        "LeftEngineFailure"
        "RightEngineFailure"
        "HydraulicsFailure"
        "ACSFailure"
        "AutopilotFailure"
        "AutopilotOn"
        "MasterWarning"
        "LeftTailPlaneFailure"
        "RightTailPlaneFailure"
        "LeftAileronFailure"
        "RightAileronFailure"
        "CanopyOpen"
        "CannonFailure"
        "StallSignalization"
        "LeftMainPumpFailure"
        "RightMainPumpFailure"
        "LeftWingPumpFailure"
        "RightWingPumpFailure"
        "RadarFailure"
        "EOSFailure"
        "MLWSFailure"
        "RWSFailure"
        "ECMFailure"
        "GearFailure"
        "MFDFailure"
        "HUDFailure"
        "HelmetFailure"
        "FuelTankDamage"
    ]]--


    local stall = 0
    for k,v in pairs(alarm) do
        if k == "StallSignalization" then 
            if v == true then
                stall = 1
            end
        end
    end

    -- local engine = LoGetEngineInfo()
    --[[
    RPM = {left, right},(%)
    Temperature = { left, right}, (Celcium degrees)
    HydraulicPressure = {left ,right},kg per square centimeter
    FuelConsumption   = {left ,right},kg per sec
    fuel_internal      -- fuel quantity internal tanks    kg
    fuel_external      -- fuel quantity external tanks    kg    
    ]]--

    -- The FlyPT Mover uses Z for vertical and Y to the front
    -- That's the opposite in DCS
    -- Values sent in one string, separated by spaces    
    socket.try(DCSClient:send(
    --               00   01   02   03   04   05   06   07   08   09   10   11   12   13   14   15   16   17   18   19   20   21   22   23
    string.format("%.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f", 
    acceleration.x,                             -- 00 = Lateral acceleration (G)
    acceleration.z,                             -- 01 = Lateral acceleration (G)
    acceleration.y,                             -- 02 = Vertical acceleration (G)
    speed.x,                                     -- 03 = Lateral speed (m/s)
    speed.z,                                     -- 04 = Longitudinal speed (m/s)
    speed.y,                                     -- 05 = Vertical speed (m/s)
    rotationSpeed.y,                             -- 06 = Rotation speed around y (yaw in rad/s)
    rotationSpeed.x,                             -- 07 = Rotation speed around x (roll in rad/s)
    rotationSpeed.z,                             -- 08 = Rotation speed around z (pitch in rad/s)
    o.Heading,                                     -- 09 = Yaw position (rad)
    o.Bank,                                     -- 10 = Roll position (rad)
    o.Pitch,                                     -- 11 = Pitch position (rad)
    Export.LoGetTrueAirSpeed(),                 -- 12 = Air speed (m/s)
    Export.LoGetAircraftDrawArgumentValue(1),     -- 13 = Front/Rear landing gear (0 to 1)?
    Export.LoGetAircraftDrawArgumentValue(2),     -- 14 = Turning landing gear (0 to 1)?
    Export.LoGetAircraftDrawArgumentValue(4),    -- 15 = Left landing gear (0 to 1)?
    Export.LoGetAircraftDrawArgumentValue(6),     -- 16 = Right landing gear (0 to 1)?
    Export.LoGetAltitudeAboveGroundLevel(),     -- 17 = Vertical position relative to ground (m)
    mechInfo.flaps.value,                         -- 18 = Flaps amount (%)
    mechInfo.gear.value,                         -- 19 = Delployed landing gear (%)
    mechInfo.speedbrakes.value,                 -- 20 = Speed brakes (%)
    mechInfo.canopy.value,                         -- 21 = Canopy open (%)
    stall,                                         -- 22 = Stall alarm (0 or 1)
    Export.LoGetModelTime()                     -- 23 = Time in seconds
    )))
end

function FlyPT_Mover_Callbacks.onSimulationStop()
    log.write('FlyPT_Mover', log.INFO, "Data export stopped")
    if DCSClient then
        DCSClient:close()
    end
end

DCS.setUserCallbacks(FlyPT_Mover_Callbacks)


 

Late to the party, but I found your post yesterday and it inspired me to attempt my own solution. See here if you're still interested:
https://www.xsimulator.net/community/threads/flypt-mover.13464/page-161#post-238866

 

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...