number3

I've come across this as well when trying to control when ground vehicles fire. I might be able to create a quick proof of concept mission to demo it. I've also had this problem with infantry. Figured that is only was supposed to work with aircrafts

What do you mean by turn off the script? If you mean to stop the MIST scheduled function, at the beginning of your function you can check the status of a flag number function trigger.misc.getUserFlag(string userFlagName) function trigger.action.setUserFlag(string userFlagName, boolean or number userFlagValue) Remember when setting a flag to put the flag name in quotes. And if you no longer require the MIST scheduled function use: http://wiki.hoggit.us/view/RemoveFunction

This issue happens to me as well. I can't figure out how to reproduce it consistently. But essentially I slew the shkval, I might make a cyclic adjustment then the shkval will go start to slew (it usually slews down and to the right, sometimes it will slew to the left). This will occur when I have ground stabilize the shkval but not locked on to a target. It doesn't matter if the laser is on or off. Doesn't matter if turn to target is on. Doesn't matter if moving target it on. Sometimes, I will have a lock on the target, make a adjustment to center the lock and the shkval will slew away automatically. I cannot flight the slew action, I can only neutralize it, but as soon as I let go, it continues to slew. The only thing that I've found that works (other than weapons reset), is if I press ground stabilize again. I will try and make a track of this happening.

Looks like you would use the mist.scheduleFunction to call SparkleLase at a set interval to get the new location of the unit. Though you may have some problems in situations where the ground elevation gets in the way and the laser points to the ground. I imagine you'll have to modify the SparkleLase method to check if the unit is within the line of site (land.isVisible), if false then cut off the laser.

Not sure what you mean exactly. But other people wouldn't need to download MIST to play your mission(s), because the MIST library is included in your mission archive (.miz). See the how to use it? section

Still waiting to hear about about deleting a destroyed unit from the map (if that's what you are asking) http://forums.eagle.ru/showthread.php?p=1930512 Yes, there are many ways to add a unit to the world

I'm building a mission where a convoy rolls into a city and get ambushed. I would like some insurgent fortifications (armed house) to be placed in the city and only fire when the unit is within the ambush zone. The engagement range of the armed house fortification is large enough to starting firing at the convoy before they enter the city area. Another problem is that the convoy sees the armed house well before it's in the ambush zone and starts to fire the house. Is it possible to script a unit fortification as well as a convoy to not fire and once the convoy reaches the zone to open fire? Ideally the convoy would not see or engage the armed house; and the armed house would not fire until the target is in the ambush zone. However I don't want to convoy to simply hold fire until it reaches the zone. My first through was to place a static structure in the city. When the unit enters the ambush zone, disable the static structure and enable the insurgent fortification in the exact same place. Wondering if there is a better way to achieve this.

You may want to play around with saving your kinetic energy from a dive, egress, stay low and pop countermeasures. The manpad engagement zone is pretty good, so the speed you carry well help with flying out of the zone. This may work best in areas where there isn't an opportunity to terrain mask you plane. The SU-25 flares dispense upwards, so they may be more effective, in that situation, to deploy them while staying low. Another trick I've seen people do is to invert their plane during a climb and dispense flares. :pilotfly:

Nice! Please make this code as modular as possible, so that other mission designers can easily incorporate it :beer:

To check the value of the flag via scripting you use http://wiki.hoggit.us/view/Part_1 number function trigger.misc.getUserFlag(string userFlagName) If you want to continuously check their status and act upon it, you may want to use this: http://wiki.hoggit.us/view/ScheduleFunction -- The following would schedule mist.groupToRandomZone to call and move 'myGroup' to a random point in zone every 900 seconds up till 3600 seconds after the function was first called. do mist.scheduleFunction(mist.groupToRandomZone, {'myGroup', 'myZone'}, timer.getTime() + 10, 900, timer.getTime() + 3600) end But all of this can be done in the Missions Editor. More information is required as to when do you want to check the status and what triggers it.

Going to try this tonight. The load times make my 'lua trial and error' mistakes costly :wallbash:

Thanks. I was hoping to avoid that solution, but whatever works. I'm guessing that you are using a continuous trigger to monitor the status of the flag and once triggered, you set the flag back to zero (or whatever value). In that case is there a performance hit adding many continuous triggers to the ME? Would it be better to call mist.scheduleFunction(), where you can control the period of function calls?

I'm also wondering if this is possible using scripts. Trying to figure out who (whether it be a unit or group, doesn't matter in my case) initiated the message. I want to add a menu item that reports on the current status of the attacking ground forces, but I don't want to push the status message to everyone in the coalition, because some people may have missed the message or didn't finish reading it in time and I want to give them the option to replay the message without bothering everyone else who is flying. Any ideas?

Oh boy... can't wait to catch up to those missions :)

This mission might not require you to eliminate the entire convoy. Similar to the first mission in the campaign, it might only require you to kill a target in order to succeed.

So the error only occurs when you click on one of your vehicle groups? Have you tried to comment out MIST functions were applicable? See if you can narrow it down to something that you're trying to do in MIST? Which version of MIST are you including?

Thanks for the reply Grimes.

Has anyone used the S_EVENT_BASE_CAPTURED event? If so, can someone provide an example of what must take place, in the mission, in order to trigger this event (script example would also be nice too!)? Also, a simulator event has the following structure (not for all events) Is there an area in the code where I can see what the returned structure of the Event is for a event fired? Thanks

I haven't tired that mission yet though when you start the mission load the maximum number of flares (unless you are getting a radar lock, then just keep a few chaffs). Like everyone says stay fast (that is key) Try to mask your ingress and/or egress points, if you can hide behind anything the better. Try continuous counter measure dispensing just before you enter the engagement zone. The continuous dispensing isn't frequent enough at times, but if you are proactive and remain fast it may be enough for your situation. Depending on the weather, try to egress out towards the sun, it may help to distract the IR lock. Maybe as a least ditch effort, try to dive bomb the artillery. Approach from the same angle of the sun, get some speed, flare and let it rip. Afterward keep your energy by staying low to the ground and fly out of their engagement zone. Repeat for the other units.

I was on there yesterday in the early evening. No problems. Only one other person there.

With respect to mission designing, from what I've seen via lua script methods, there is quite a lot that can be accomplished at a lower level of mission design. When it comes to designing a mission that encompasses many different aircraft and roles, the complexity of producing a random combat zone grows exponentially. There are quite a lot of impressive scripts out there that are of a more narrow scope, however the knowledge and the potential is definitely there. I'm not sure how other designers are finding the learning curve of lua scripting for more complex missions, but it's quite steep and could use more documentation and drills into more complex actions.

Does the actual process of re-arming take any time? Or will any vehicle within the re-arming radius instantly be fully re-armed and the truck can drive off into hiding?

This is great! I've been looking for some good references to script different things for missions. Learning through a lot of mistakes (and errors), but all of the documentation you provided is a huge help for newbies.

Sounds good. I might try to hop in on Friday. I'll be away the entire weekend though. Also spending my free time leaning how to script a mission. :book:

Congrats! I still use an x45. Had the itch to upgrade to the x52 but hesitated when I found out they got rid of the rudder rocker switch under the throttle. I bought mine second hand a some time ago and the previous owner removed the pinky switch. See: http://img06.tablica.pl/images_tablicapl/47382407_4_644x461_saitek-x45-profesjonalny-kontroler-lotu-elektronika.jpg So now there is an indent where the orange pinky switch used to be, if I want to use it I just move my pinky down into the indentation and pull. The mode switch basically acts as a shift key. When you download the programming software you'll see what I mean. Personally I almost never remember which mode I'm in. You can override and program your own shift keys in the program utility (I usually use the mouse fire button). One thing that I've never been able to get working are the rotary switches. Tried to program them for zooming in and out but in game nothing happens. And it may only be me, but the Auxiliary switch is a bit flaky. If you ever need help with the programming, let me know.