Dynamic Medevac Script

[ArturDCS]

Sorry guys- I think I've confused you with what the problem is...

Thanks for explaining this, it was all new to me!

[ArturDCS]

 

00022.788 INFO    SCRIPTING: Mist version 3.3.22 loaded.
00026.040 INFO    SCRIPTING: Medevac event handler added
00027.725 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.725 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.725 INFO    SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH
00027.735 INFO    SCRIPTING: Moving spawn position for helicopter survivors! Type is UH-1H
00027.735 INFO    SCRIPTING: Helicopter is TRUE!
00027.735 INFO    SCRIPTING: _
00027.735 INFO    SCRIPTING: C6MOD Will spawn 1 survivors from helicopter Huey Flight helicopter crew #1. Crew member count is 4
00027.735 INFO    SCRIPTING: _
00027.735 INFO    SCRIPTING: C6MOD Spawning survivor 1 of 1 with name Huey Flight helicopter crew #1 crew #1
00027.738 INFO    SCRIPTING: _isHelicopter = FALSE
00027.738 ERROR   SCRIPTING: Error while handling event

[string "C:\Users\User\AppData\Local\Temp\DCS\/~mi..."]:1247: attempt to index a nil value
00027.740 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.740 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.745 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.745 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.749 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.749 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.749 INFO    SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH
00027.749 INFO    SCRIPTING: Moving spawn position for helicopter survivors! Type is UH-1H
00027.749 INFO    SCRIPTING: Helicopter is TRUE!
00027.749 ERROR   SCRIPTING: Error while handling event

[string "C:\Users\User\AppData\Local\Temp\DCS\/~mi..."]:1238: attempt to index a nil value
00027.752 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.752 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.754 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.754 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.754 INFO    SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH
00027.755 INFO    SCRIPTING: Moving spawn position for helicopter survivors! Type is UH-1H
00027.755 INFO    SCRIPTING: Helicopter is TRUE!
00027.755 INFO    SCRIPTING: _
00027.755 INFO    SCRIPTING: C6MOD Will spawn 2 survivors from helicopter Huey Flight helicopter crew #3. Crew member count is 4
00027.755 INFO    SCRIPTING: _
00027.755 INFO    SCRIPTING: C6MOD Spawning survivor 1 of 2 with name Huey Flight helicopter crew #3 crew #1
00027.755 INFO    SCRIPTING: C6MOD Spawning survivor 2 of 2 with name Huey Flight helicopter crew #3 crew #2
00027.757 INFO    SCRIPTING: _isHelicopter = FALSE
00027.758 WARNING LOG: 1 duplicate message(s) skipped.
00027.758 ERROR   SCRIPTING: Error while handling event

[string "C:\Users\User\AppData\Local\Temp\DCS\/~mi..."]:1247: attempt to index a nil value
00027.760 INFO    SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4
00027.760 INFO    SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H
00027.809 INFO    SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\User\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed
00029.644 INFO    SCRIPTING: _isHelicopter = FALSE
00029.644 INFO    SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH
00029.745 INFO    SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\User\AppData\Local\Temp\DCS\/~mi..."]:4241: Object doesn't exist
00082.327 WARNING LOG: 26 duplicate message(s) skipped.
00082.327 INFO    SCRIPTING: _isHelicopter = FALSE
00083.733 WARNING LOG: 8 duplicate message(s) skipped.
00083.733 INFO    SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\User\AppData\Local\Temp\DCS\/~mi..."]:4241: Object doesn't exist
00115.034 WARNING LOG: 13 duplicate message(s) skipped.
00115.034 INFO    SCRIPTING: _isHelicopter = FALSE
00115.066 INFO    Config: netview stopped

 

 

OK, so I need help. By giving each spawned survivors an unique name the script does not create (or execute) the "SAR REQUESTED" message. I cannot find the reason for this. I have pasted my dcs.log here. Attached the modified script.

Working without a good integrated development environment makes this quite difficult.

Medevac_SAR v4_2_C6_MODDED_V1.0.lua

[ArturDCS]

Some progress. Attaching log, mission I flew. Worked OK.

 

Still error messages in the log.

00039.248 INFO    SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\user\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed

Added:

  --DO NOT ADD group to medevac.woundedgroups if there are no survivors to be spawned! (--> HELICOPTER!)
 if (_ispilot and _isHelicopter and numberOfSurvivors > 0) or (_ispilot and not _isHelicopter) or (not _ispilot) then

I changed the line

local _leadername = string.format("%s #1", _groupname)

to

local _leadername = "none"

which is declared before the spawning if statement and moved the assignment of this variable into the if statement for each type of survivors.

 

For Pilot:

local spawnUnitName = string.format("%s pilot", _groupname)
                       _leadername = spawnUnitName

For Helicopter(first crew member):

local spawnUnitName = string.format("%s crew member #", _groupname) .. i
if i == 1 then
  _leadername = spawnUnitName    
end

For Vehicle (first soldier):

local spawnUnitName1 = string.format("%s #1", _groupname)

I made the code after the spawning if statement conditional so that if there are 0 helicopter crew survivors it won't execute.

--Do not execute this is there are no _leadername. It can be "none" if the triggering unit (event handler) was a helicopter and there were no survivors
  if _leadername ~= "none" then

 

 

00024.327 INFO SCRIPTING: Mist version 3.3.22 loaded.

00027.412 INFO SCRIPTING: Medevac event handler added

00029.216 INFO SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4

00029.216 INFO SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H

00029.216 INFO SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH

00029.225 INFO SCRIPTING: Moving spawn position for helicopter survivors! Type is UH-1H

00029.225 INFO SCRIPTING: Adding wounded group to table medevac.woundedgroups. Group is Huey Flight helicopter crew #1

00029.225 INFO SCRIPTING: Helicopter is TRUE!

00029.225 INFO SCRIPTING: A

00029.225 INFO SCRIPTING: C

00029.225 INFO SCRIPTING: _

00029.225 INFO SCRIPTING: C6MOD Will spawn 3 survivors from helicopter Huey Flight helicopter crew #1. Crew member count is 4

00029.225 INFO SCRIPTING: _

00029.225 INFO SCRIPTING: C6MOD Spawning survivor 1 of 3 with name Huey Flight helicopter crew #1 crew member #1

00029.225 INFO SCRIPTING: C6MOD Spawning survivor 2 of 3 with name Huey Flight helicopter crew #1 crew member #2

00029.225 INFO SCRIPTING: C6MOD Spawning survivor 3 of 3 with name Huey Flight helicopter crew #1 crew member #3

00029.226 INFO SCRIPTING: D

00029.229 INFO SCRIPTING: _isHelicopter = FALSE

00029.230 WARNING LOG: 2 duplicate message(s) skipped.

00029.230 INFO SCRIPTING: E

00029.230 INFO SCRIPTING: G

00029.230 INFO SCRIPTING: H

00029.230 INFO SCRIPTING: H1

00029.230 INFO SCRIPTING: H2

00029.230 INFO SCRIPTING: Leadername is 'Huey Flight helicopter crew #1 crew member #1'

00029.230 INFO SCRIPTING: I

00029.230 INFO SCRIPTING: J

00029.230 INFO SCRIPTING: K

00029.230 INFO SCRIPTING: L

00029.230 INFO SCRIPTING: M

00029.230 INFO SCRIPTING: N

00029.230 INFO SCRIPTING: O

00029.230 INFO SCRIPTING: P

00029.230 INFO SCRIPTING: Q

00029.230 INFO SCRIPTING: R

00029.230 INFO SCRIPTING: S

00029.230 INFO SCRIPTING: T

00029.230 INFO SCRIPTING: U

00029.230 INFO SCRIPTING: V

00029.230 INFO SCRIPTING: T

00029.230 WARNING SCRIPTING: Medevac unit MEDEVAC #2 not active

00029.230 INFO SCRIPTING: V

00029.232 INFO SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4

00029.232 INFO SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H

00029.312 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\user\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed

00031.412 WARNING LOG: 1 duplicate message(s) skipped.

00031.412 INFO SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4

00031.412 INFO SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H

00031.412 INFO SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH

00031.412 INFO SCRIPTING: Moving spawn position for helicopter survivors! Type is UH-1H

00031.412 INFO SCRIPTING: Adding wounded group to table medevac.woundedgroups. Group is Huey Flight helicopter crew #2

00031.413 INFO SCRIPTING: Helicopter is TRUE!

00031.413 INFO SCRIPTING: A

00031.413 INFO SCRIPTING: C

00031.413 INFO SCRIPTING: _

00031.413 INFO SCRIPTING: C6MOD Will spawn 4 survivors from helicopter Huey Flight helicopter crew #2. Crew member count is 4

00031.413 INFO SCRIPTING: _

00031.413 INFO SCRIPTING: C6MOD Spawning survivor 1 of 4 with name Huey Flight helicopter crew #2 crew member #1

00031.413 INFO SCRIPTING: C6MOD Spawning survivor 2 of 4 with name Huey Flight helicopter crew #2 crew member #2

00031.413 INFO SCRIPTING: C6MOD Spawning survivor 3 of 4 with name Huey Flight helicopter crew #2 crew member #3

00031.413 INFO SCRIPTING: C6MOD Spawning survivor 4 of 4 with name Huey Flight helicopter crew #2 crew member #4

00031.413 INFO SCRIPTING: D

00031.416 INFO SCRIPTING: _isHelicopter = FALSE

00031.417 WARNING LOG: 3 duplicate message(s) skipped.

00031.417 INFO SCRIPTING: E

00031.417 INFO SCRIPTING: G

00031.417 INFO SCRIPTING: H

00031.417 INFO SCRIPTING: H1

00031.417 INFO SCRIPTING: H2

00031.417 INFO SCRIPTING: Leadername is 'Huey Flight helicopter crew #2 crew member #1'

00031.417 INFO SCRIPTING: I

00031.417 INFO SCRIPTING: J

00031.417 INFO SCRIPTING: K

00031.417 INFO SCRIPTING: L

00031.417 INFO SCRIPTING: M

00031.417 INFO SCRIPTING: N

00031.417 INFO SCRIPTING: O

00031.417 INFO SCRIPTING: P

00031.417 INFO SCRIPTING: Q

00031.417 INFO SCRIPTING: R

00031.417 INFO SCRIPTING: S

00031.417 INFO SCRIPTING: T

00031.417 INFO SCRIPTING: U

00031.417 INFO SCRIPTING: V

00031.417 INFO SCRIPTING: T

00031.417 WARNING SCRIPTING: Medevac unit MEDEVAC #2 not active

00031.417 INFO SCRIPTING: V

00031.429 INFO SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4

00031.429 INFO SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H

00031.508 INFO SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4

00031.508 INFO SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H

00031.508 INFO SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH

00031.508 INFO SCRIPTING: Moving spawn position for helicopter survivors! Type is UH-1H

00031.508 INFO SCRIPTING: Adding wounded group to table medevac.woundedgroups. Group is Huey Flight helicopter crew #3

00031.508 INFO SCRIPTING: Helicopter is TRUE!

00031.508 INFO SCRIPTING: A

00031.508 INFO SCRIPTING: C

00031.508 INFO SCRIPTING: _

00031.508 INFO SCRIPTING: C6MOD Will spawn 3 survivors from helicopter Huey Flight helicopter crew #3. Crew member count is 4

00031.508 INFO SCRIPTING: _

00031.508 INFO SCRIPTING: C6MOD Spawning survivor 1 of 3 with name Huey Flight helicopter crew #3 crew member #1

00031.508 INFO SCRIPTING: C6MOD Spawning survivor 2 of 3 with name Huey Flight helicopter crew #3 crew member #2

00031.508 INFO SCRIPTING: C6MOD Spawning survivor 3 of 3 with name Huey Flight helicopter crew #3 crew member #3

00031.508 INFO SCRIPTING: D

00031.512 INFO SCRIPTING: _isHelicopter = FALSE

00031.513 WARNING LOG: 2 duplicate message(s) skipped.

00031.513 INFO SCRIPTING: E

00031.513 INFO SCRIPTING: G

00031.513 INFO SCRIPTING: H

00031.513 INFO SCRIPTING: H1

00031.513 INFO SCRIPTING: H2

00031.513 INFO SCRIPTING: Leadername is 'Huey Flight helicopter crew #3 crew member #1'

00031.513 INFO SCRIPTING: I

00031.513 INFO SCRIPTING: J

00031.513 INFO SCRIPTING: K

00031.513 INFO SCRIPTING: L

00031.513 INFO SCRIPTING: M

00031.513 INFO SCRIPTING: N

00031.513 INFO SCRIPTING: O

00031.513 INFO SCRIPTING: P

00031.513 INFO SCRIPTING: Q

00031.513 INFO SCRIPTING: R

00031.513 INFO SCRIPTING: S

00031.513 INFO SCRIPTING: T

00031.513 INFO SCRIPTING: U

00031.513 INFO SCRIPTING: V

00031.513 INFO SCRIPTING: T

00031.513 WARNING SCRIPTING: Medevac unit MEDEVAC #2 not active

00031.513 INFO SCRIPTING: V

00031.515 INFO SCRIPTING: C6MOD Unit is of type UH-1H. Crew number is 4

00031.515 INFO SCRIPTING: _isHelicopter = TRUE Crew count = 4 Type = UH-1H

00033.219 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\user\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed

00039.144 WARNING LOG: 2 duplicate message(s) skipped.

00039.144 INFO SCRIPTING: _isHelicopter = FALSE

00039.145 WARNING LOG: 1 duplicate message(s) skipped.

00039.145 INFO SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH

00039.145 INFO SCRIPTING: Adding wounded group to table medevac.woundedgroups. Group is A10 Flight downed pilot #1

00039.145 INFO SCRIPTING: Helicopter is FALSE!

00039.145 INFO SCRIPTING: A

00039.145 INFO SCRIPTING: B

00039.146 INFO SCRIPTING: _isHelicopter = FALSE

00039.146 INFO SCRIPTING: G

00039.147 INFO SCRIPTING: H

00039.147 INFO SCRIPTING: H1

00039.147 INFO SCRIPTING: H2

00039.147 INFO SCRIPTING: Leadername is 'A10 Flight downed pilot #1 pilot'

00039.147 INFO SCRIPTING: I

00039.147 INFO SCRIPTING: J

00039.147 INFO SCRIPTING: K

00039.147 INFO SCRIPTING: L

00039.147 INFO SCRIPTING: M

00039.147 INFO SCRIPTING: N

00039.147 INFO SCRIPTING: O

00039.147 INFO SCRIPTING: P

00039.147 INFO SCRIPTING: Q

00039.147 INFO SCRIPTING: R

00039.147 INFO SCRIPTING: S

00039.147 INFO SCRIPTING: T

00039.147 INFO SCRIPTING: U

00039.147 INFO SCRIPTING: V

00039.147 INFO SCRIPTING: T

00039.147 WARNING SCRIPTING: Medevac unit MEDEVAC #2 not active

00039.147 INFO SCRIPTING: V

00039.248 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\user\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed

00052.132 WARNING LOG: 6 duplicate message(s) skipped.

00052.132 INFO SCRIPTING: _isHelicopter = FALSE

00052.132 INFO SCRIPTING: Event is : S_EVENT_DEAD or S_EVENT_EJECTION or S_EVENT_CRASH

00052.132 WARNING SCRIPTING: Event already fired for this unit. Exiting.

00053.222 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\user\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed

00083.812 WARNING LOG: 15 duplicate message(s) skipped.

00083.812 INFO SCRIPTING: _isHelicopter = FALSE

00085.223 WARNING LOG: 8 duplicate message(s) skipped.

00085.223 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\user\AppData\Local\Temp\DCS\/~mi..."]:4254: Parameter #1 (unit name string) missed

00103.835 WARNING LOG: 8 duplicate message(s) skipped.

00103.835 INFO SCRIPTING: _isHelicopter = FALSE

00103.875 INFO Config: netview stopped

00103.949 INFO EDCORE: (dDispatcher)enterToState_:3

00103.952 INFO EDCORE: (dDispatcher)enterToState_:6

00104.003 INFO SOUND: detaching sdef path ".\mods\aircrafts\uh-1h\sounds\sdef\"

00104.003 INFO SOUND: detaching sdef path ".\scripts\database\coremodules\wwii units\sounds\sdef\"

00104.003 INFO SOUND: detaching sdef path "c:\users\user\saved games\dcs\sounds\sdef\"

00104.003 INFO SOUND: detaching sdef path "sounds\sdef\"

00104.016 INFO TERRAIN: lSystem::Exit()

00104.016 INFO TERRAIN: lSystem::CleanScenes()

=== Log closed.

 

 

Medevac_SAR v4_2_C6_MODDED_V1.0.lua

=OUTLAW= C6 MODDED MEDEVAC.miz

Edited February 19, 2014 by ArturDCS

[ArturDCS]

Has anyone tested my latest version of the script? Very quiet here. :)

[Winfield_Gold]

Nope, I only just seen this thread......i've been using old mates script in past missions. Infantry and fuel drums script is about it. I'll download yours and give it a crack....cheers

[ArturDCS]

Nope, I only just seen this thread......i've been using old mates script in past missions. Infantry and fuel drums script is about it. I'll download yours and give it a crack....cheers

Thanks!

[joker62]

... omissis ...

WHAT DO I WANT IN RETURN?

I've spent a few days developing this script. What I need now is feedback! Did it crash? Did it suck? Did it rock? The script outputs data to the dcs.log - file so if you experience a crash or something else unwanted, please please please send the log-file to me so I can maybe fix the problem. If you make a mission with this script please tell me! Even if its a very simple mission I would really like to know how and if this script is used.

 

Dear Sir,

I tried the medevac script and it's really useful, and I'm deeply grateful for your work!

I use your scripts in autogenerated (and modified) missions, for SAR different pilots/soldiers at a time, along with "complete transport script" by Geloxo (and without any problem).

I've attached any my typical mission, via PM.

 

Feedback:

 

Please,

 

- Can you add the possibility to set "true / false" to see the messages that require to return soon to MASH? (personally I think their annoying);

 

- Can you add the possibility to stop the pilot when the SAR helicopter is within 500 meters, and then, when helicopter landed within 50 meter, to bring pilot to helicopter? (I think, better if the pilot "disappears " when very close to the helicopter);

 

- When the helicopter landed near the MASH, can you recreate the number of soldiers/pilots rescued? (they can appear out of helicopter and walk in one prearranged place close to MASH);

 

- Can you add the possibility to set the time to display the messages (for example, 20 seconds)? (the last message remains on the screen and personally I think annoying).

 

Thank You very much, ... and sorry for my english.

 

antonio.

[RagnarDa]

Thanks for your kind words and the input! I like your ideas, but I am tied up elsewhere at the moment...

[ENO]

Eh Ragnarda... one thing I have noticed is my dynamically added unit in your script doesn't hold fire... even though the "hold fire" in the script is set to true. Have you heard any such issues?

[RagnarDa]

@Eno Did you mean the V5 "beta" posted by DragonShadow a few posts up or which version did you test? I can atleast confirm that that specific version do work as for the survivors not firing (even though I think it looks kind of silly that they are just standing there aiming their guns, but to each their own I guess... :) ).

 

As for the issue you had a while back with not being able to pick up every other ejected pilot. I had a look in the logs and your settings and you had set the survival rate to 50% for blue side which means that every other pilot ejecting is "dead". I think it maybe shouldn't be like this but atleast it explains your issue. The actual pilot model in the parachute can't be picked up unfortunately.

[ENO]

This version was the original version... or the one Shag updated... I'll try with the latest version.

 

And your explanation for the 50% definitely explains it that other issue. I thought it was 50% of the personnel on the ground but that makes sense. I'll need to focus the script on aircraft only and leave it at 100%. Does the program distinguish between eject events and ground vehicle destruction events in a way that you can choose to have ejected pilots survive 100% of the time but 50% of ground vehicle survivors (as an example).

 

It also might explain why it is that my exploding aircraft (meant to start the mission off) sometimes doesn't have a chute no matter how big or small the explosion.

 

Thanks Rag.

[shagrat]

This version was the original version... or the one Shag updated... I'll try with the latest version.

 

And your explanation for the 50% definitely explains it that other issue. I thought it was 50% of the personnel on the ground but that makes sense. I'll need to focus the script on aircraft only and leave it at 100%. Does the program distinguish between eject events and ground vehicle destruction events in a way that you can choose to have ejected pilots survive 100% of the time but 50% of ground vehicle survivors (as an example).

 

It also might explain why it is that my exploding aircraft (meant to start the mission off) sometimes doesn't have a chute no matter how big or small the explosion.

 

Thanks Rag.

 

Hi ENO,if you spawn units, check that the "hold fire" needs to be set in the spawned group actions! The variable is setting a true or false for the action in the group definition directly.

Hope this does make sense.

 

...or maybe you upload your current version and we have a look?

[fangav]

Just like to add to what jokers has said.

VERY good Script to add to existing mission, it adds so much randomness.

The problem I'm having is with the message box. With our missions we have missions update and changes to objective during the mission and when someone has picked up some injured soldiers the medevac message does not allow the other messages to get through.

Thanks to all who have had a hand in this script.

 

 

 

Dear Sir,

I tried the medevac script and it's really useful, and I'm deeply grateful for your work!

I use your scripts in autogenerated (and modified) missions, for SAR different pilots/soldiers at a time, along with "complete transport script" by Geloxo (and without any problem).

I've attached any my typical mission, via PM.

 

Feedback:

 

Please,

 

- Can you add the possibility to set "true / false" to see the messages that require to return soon to MASH? (personally I think their annoying);

 

- Can you add the possibility to stop the pilot when the SAR helicopter is within 500 meters, and then, when helicopter landed within 50 meter, to bring pilot to helicopter? (I think, better if the pilot "disappears " when very close to the helicopter);

 

- When the helicopter landed near the MASH, can you recreate the number of soldiers/pilots rescued? (they can appear out of helicopter and walk in one prearranged place close to MASH);

 

- Can you add the possibility to set the time to display the messages (for example, 20 seconds)? (the last message remains on the screen and personally I think annoying).

 

Thank You very much, ... and sorry for my english.

 

antonio.

[RagnarDa]

Dynamic Medevac Script

 

Thanks for reporting this! Not sure how to solve that except disable the updates as Joker suggested.

[shagrat]

Hi RagnarDa, I put the script into a MP mission where I currently add other tasks/missions.

I noticed one big problem. Whenever a Player gets killed and reenters the game, he is not able to pick up any survivors.

The triggers simply don't fire.

Interestingly, he can request the active MEDEVACs from the Menu etc.

 

It is just he gets no smoke, and can't pick anyone up.

 

When another unit gets killed, while the respawned player is in the game again, everything works for that particular unit and its survivors.

 

My best guess is, that you use the ObjectID to check the MEDEVAC Helis when checking for a pick up, but I'm not sure. The ObjectID would change when respawning, I guess?

 

If this is the root cause, is it possible to loop through the MEDEVAC units list (where all "possible" MEDEVAC units are in) and check if they are landed near a survivor?

 

I tried to find where you check through the currently existng units, but got lost in the code... :helpsmilie:

[RagnarDa]

Thanks for reporting! Will try to have a look once I have some time to spare.

[DSPALLASVI]

Just tried "Dynamic Medevac", and noticed mission starts off flying at altitude, instead of being located at an airfield or FARP.

Am not familiar with coordinates system being used. Can fly around and only by good luck find some smoke to land by and rescue crew. When using F10 and F1, have no idea how to interpret given data of where to pick up units.

Searched through this post, but can't find explanation for coordinates being given for units needing to be rescued.

Was wondering if someone could offer a link for some help with the coordinates system being used in this mission....

[ENO]

Which coordinates were given? Might be able to lead you to the right explanatory thread.

 

There is a way to change the system in the script- it's one of the options- but best to just learn the one you have and then change if desired.

[DSPALLASVI]

Sorry for the delay...

Here's a screen shot after picking up some crew of a crashed A-10, I happen to see crash while flying around at beginning of mission. Brought them back to M*A*S*H...

Then, 'F10' → 'F1' > to see "active Medevac/SAR' and get to see those messages in top right of screen:

 

Am puzzled by the directions like: "...*** at bullseye 068 for 13 at 2040..."

 

Is the "068" a bearing from the FARP to the unit in question?

"13" the distance to the unit? and

"2040" the time it happened? If so, in what time format? GMT? Georgia Local Time?

The mission itself starts of (in the air!?!) at 13:00 local time...

 

Note: only fly Huey module, and am familiar with navigation

(Bearing, Heading, distance, Deviation, Variation, LOP, etc. etc. etc.)

 

Thanks for your help....

[Silver_Dragon]

A old video, but can help your

[mwd2]

BRA: Bearing, Range & Altitude

[shagrat]

Sorry for the delay...

Here's a screen shot after picking up some crew of a crashed A-10, I happen to see crash while flying around at beginning of mission. Brought them back to M*A*S*H...

Then, 'F10' → 'F1' > to see "active Medevac/SAR' and get to see those messages in top right of screen:

 

Am puzzled by the directions like: "...*** at bullseye 068 for 13 at 2040..."

 

Is the "068" a bearing from the FARP to the unit in question?

"13" the distance to the unit? and

"2040" the time it happened? If so, in what time format? GMT? Georgia Local Time?

The mission itself starts of (in the air!?!) at 13:00 local time...

 

Note: only fly Huey module, and am familiar with navigation

(Bearing, Heading, distance, Deviation, Variation, LOP, etc. etc. etc.)

 

Thanks for your help....

 

Ok. I think you should change to MGRS coordinates. If you switch the F10 map to MGRS it is pretty easy to get a rough position from the Grid info alone. Google MGRS, or search for it on the forum. Ground units usuallty use MGRS.

What you received is a bullseye call (BRA) and requires to know where exactly the "bullseye" is. On the F10 map it is the blue/or red circles symbol. Measure the bearing and range from it and look for a matching elevation above MainSeaLevel.

 

The coordinates can be switched in the scripts header section. Look for MGRS...

[DSPALLASVI]

Thanks 'Silver Dragon', 'mwd2' & 'shagrat'... :thumbup:

 

@ 'Silver Dragon' → might be an old video, but it's new to me! :doh: Now that I know what the 'Bulls Eye' stands for, it all makes sense. Just needed to know what point of reference was being used when given 'BRA' directions.

 

@'mwd2' → with the knowledge of what the reference point is, finding the units needing 'pick-up / evacuation' are easy to find. Though I'd have to use 'F10' map to figure that out. Any other way, like using the knee-board, or is it only possible on the large map?

 

@ 'shagrat' → searched through the forum and came across the info that using keystrokes "L-Alt + Y" switches between LL & MSGR coordinates. Haven't tried that out yet.

Knowing what the the bull's eye location in the 'Dynamic Medevac Script' mission is, should give me enough info to figure out any BRA given.

"... The coordinates can be switched in the scripts header section. Look

for MGRS..."

Sorry, am not familiar with scripts and how to change them....

 

Thanks all for your help... much appreciated!!

Edited April 16, 2014 by DSPALLASVI
Added text...

[xcom]

Does this script use smoke and flare when you get closer as the CSAR script uses?

Smoke

trigger.action.smoke(Vec3 point, enum trigger.smokeColor color)}

 

Flare

trigger.action.signalFlare(Vec3 point, enum trigger.flareColor color, Azimuth azimuth)

 

Illumination bomb

trigger.action.illuminationBomb(Vec3 point)

 

Also, it would be awesome to use the FM radio to identify the area we need to get to instead of using the F10 map for Bullseye or BRA, there's a way with DCS scripting -

trigger.action.radioTransmission(string fileName, Vec3 point, enum radio.modulation modulation, boolean loop, number frequency, number power)

[shagrat]

May be for two or three CASEVACs, but I have a mission where it is dynamic and could be up to 30... groups to pick up use smoke at a range of 3.000m by default. Color can be changed in script header.