shelt

Thanks, that seemed to fix that error. The other issue seemed to be with the Medevac script and setting the medevac.clonenewgroups to true. Turned it to false and it no longer seemed to be no problems with the joining units error.

Any idea on why this error would pop up? ERROR Trigger: can't execute trigger, err:"[string "?"]:1: bad argument #1 to 'loadstring' (string expected, got function)" I had a MP server last night would crash each time until I renamed the BlueMash without the "#1" then no crash. I ran the script with single player with mash named BlueMASH #1 and seemed to work OK. Just MP an issue? **EDIT** Just a note to say I set "medevac.clonenewgroups" to false and seemed the error went away

Something to look at. I have been getting an error (in MP mission) 786: attempt to index local 'leader' (a nil value) The game will hang, I suppose it is the error message, but I have to hit escape for my view of the game to unhang. I do have a flag "counting" the number of troops who have been spawned in a zone, and the counter is to stop the respawn when a certain number of troops spawn. Not sure if this is the issue or not. I have also noticed over time, some of the P51's or choppers cannot be chosen to fly. The message I get is "Shelt is joining Blue in ." and no unit name appears. In the log it shows I am trying to join a ground unit. Here is the DCS log output. 1172.391 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "UH-1H"(229) 01175.910 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "UH-1H"(228 01177.337 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(230) 01178.992 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(231) 01180.548 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Soldier M4"(225) 01184.945 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Soldier M4"(226) 01186.260 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Soldier M4"(227) 01189.241 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "UH-1H"(228 01189.927 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "UH-1H"(229) 01190.945 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(230) 01192.117 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(231) 01194.791 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Soldier M4"(225) 01195.783 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(231) 01196.359 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(230) 01197.424 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Paratrooper AKS-74"(231) 01198.346 INFO NET: Lua: Client [1] "sheltssd" joined Blue in "Soldier M4"(225) Each one was trying to select a different UH-1H or a P-51 I also have the Medevac script insalled, so may have to remove it to see if that is the issue

My oh my...very nice addition to the script. Thanks much for the work !

I have put at least 8 units in as medevac, haven't tried to put multiple MASH units in, but don't see why it would be an issue. I also set the MASH units to transmit an ogg file (use radio chatter for immersion effect, or music to fly by) set to a specified FM channel. You can then use the FM>Home feature to navigate to the MASH unit. Good thing is that you can use the same ogg file for different aircraft radio, say for P51 on channel 124 AM.

Another fantastic idea to the scripts available. I will give this a try, looks like it will be very helpful in some missions. Thanks, Mbot

:megalol: I almost passed out when I read this, but I guess you have to reenforce it!

Sounds like a good solution. Also was thinking of adding a Radio Item that will allow the user to display at will and a switched condition. I do like the idea that time displays the message rather than a user interface.

I was able to output the flag with the trigger do script and the following local msg = {} msg[#msg + 1]='Enemy troops in zone = ' msg[#msg + 1]=trigger.misc.getUserFlag('201') msg[#msg + 1]='. \n' trigger.action.outText(table.concat(msg), 20) I could expand on this to show the value of the 200 flag as well, and would like to have it repeated at intervals during the mission. Any better ideas on how to display the flag values?

I just noticed the new features and have tried them out in a mission. Great work on theis script geloxo. Much appreciated! So the groupcount can be displayed as a text message? Was thinking of asking if this was possible while working on a mission this week.

Love the G930 and the wireless trackir. No better way to fly!

Some pics can be found here on "How to". got to agree wireless is best for the trackir http://sdsquad.com/index.php?topic=2403.0

I have enjoyed the KA50, but the HD and Blue Pit really makes a difference in the sim. Thanks to those who have taken the time to enhance everyone flying experience.

Nice work Devrim, many thanks.

Thanks for the configuration program. Didn't know it existed until I read this post! **EDIT** WOW, after using the stick a few times after doing the calibration, it is truely amazing on the difference! I figured a stick like this really wouldn't need it, but it does make a huge difference!

Thanks for the tip on the units required. Sure makes it easier to allow rearming. I always assumed any unit was enough to allow resupply (like at an airbase) but guess this isn't the condition at a FARP

Did a quick test and seems to work fine now! Thanks for fulfilling the request, the work is very much appreciated. Will be running the server tonight and will let you know if there are issues. Thanks again!

Thanks for taking a look at this. I tried the script and got the following error. AppData\Local\Temp\DCS\/~mis00005921"]:33: ')' expected near '!'

Any chance on getting green smoke on Blue units, and red on red units? Actually not picky on the colors, just able to choose which color for each side would help. Is there a way this can be changed in the script? I'm working on a close quarters city invasion with lots of ground units, and it is hard to tell which units are which sometimes :)

Thanks for the work on this, geloxo. Guess the coding is sometimes like building a mission, you have to refine it until it is polished. The changes you have made since the original are amking it very easy to understand how to configure. Have you been able to determine why using additional pickup points the colors have to be alternated to get all to show? or have you tried that yet?

You need to delete any pickup zones you are not using in the script. I tried it as a test with your attached mission and it worked as it should. I have also noticed in a mission I am building, which has multiple pick-up zones, if you use the same color in sequence, like blue, only the first smoke will appear. Not only that, no other smoke markers will appear. The mission is a Red vs Blue type mission. I am wanting to use blue smoke for blue side and red smoke for the red side. With orange and white for the drop zones. If I did the code as this: "USPickupa", "blue", "USMZPU", "blue", "RUPickupa", "red", "RUPickupb", "red", only the very first blue pick up zone would produce smoke and the smoke dissappeared when I entered the zone. If I did the code as this: "USPickupa", "blue", "RUPickupa", "red", "USMZPU", "blue", "RUPickupb", "red", all the smoke markers will appear and would stay. That was the problem I was having with the first post I made about having issues with the script.

Nice script geloxo, and thanks for taking the time to do this. I have used this in a mission and it works great. How would one tweak the code to include additional pick-up points. I have tried to copy and change the [1] and [2] code line with additional values of [3] and [4], but only the first smoke marker will show. I am able to land in the added zone and load troops, but the smoke marker will only show for the first pick up point. PickupZones = { [1] = { ZoneName = "Bluepickup", SmokeColor = trigger.smokeColor.Blue, }, [2] = { ZoneName = "Bluepickup2", SmokeColor = trigger.smokeColor.Blue, }, [3] = { ZoneName = "Redpickup", SmokeColor = trigger.smokeColor.Red, }, [4] = { ZoneName = "Redpickup2", SmokeColor = trigger.smokeColor.Red, }, } **EDIT** Not sure why but got it working now

You are correct, the pick-ups still do work for the units specified for MEDEVAC in the script. The problem I have seen is not being able to tell if there is still an EVAC mission available, have seen some of the spawned survivors be killed by enemy forces before getting there and no way to tell which units still are alive and require EVAC. Great stuff, though. I can easily overlook it :thumbup:

I have meshed this script with a mission I have been working on, one thing that I have found is the Huey must be ALIVE on mission start for it to work properly. I have 8 Hueys in the mission set as clients, and if all are not occupied, the F10 SAR message will not be displayed to any of those who were not occupying a Huey at mission start. You will see all the request for evac, but are unable to pick up the wounded. Am I correct on this? Even though the F10 function doesn't work, will they still be able to perform Medevac? I found the work around was to add a trigger and load the script on "unit alive" but this has to be done for each unit. Now when I switch between Hueys after the mission start I will get the F10 function. Is there a better way to get the late joiners "active"? I also have to admit I like the fact you can pick up pilots who have ejected! Great stuff!!!

Figuring about 200 pound average per troop would be 998 kg