Search the Community
Showing results for tags 'actions'.
-
Currently, the Unit selection (which is the airfield selection) is in some unknown order. It would be much easier to select one if this could be in alphabetical order. Furthermore, there is the selection of dozens of "H" helipads which is pretty useless, since there is no indication which "H" is which. The picture is an example of the Syria map.
-
- 1
-
-
- mission editor
- trigger
-
(and 3 more)
Tagged with:
-
Hi, here is my long list of ME wishes: TRIGGERS and ACTIONS activate group after a random time activate/spawn group in random zone activate random group go to random waypoint set random ROE set random 'reaction to threat' trigger random flag number organize each trigger category under a folder (or expand section) flag number validator - if flag number is already in use show a message respawn unit/group if destroyed General stuff random time random weather add possibility to draw sketch and write notes on an overlayer add possibility to make snapshots (like in CombatFlite, for ex.) and to export them like image (png, jpg, etc) SAM circles on/off check, so we can declutter the map if you set an unit as "Uncontrolled" add a checkbox to create "Start" task for that unit add back the GAI task, so we can have uncontrolled AI take-off and intercept when enemies are detected by EWR network. show moon phase and sun position Dreaming on random civil air traffic BLUE side EWR units units/groups organized/grouped on Regiments, Brigades, etc. Thanks!
-
Using a continuous statement that is running "group stop" on a SA-6 site to prevent the site from being moved in multiplayer. The statement fires continuously(using a signal flare as visual indication) but the waypoints given by a tac commander are followed, the group will not halt. This does not quite seem like intended behaviour by the action. could someone clarify the method and possibly a solution for the desired result of making unit controllable but immovable? EDIT: achieved goal using the AI SET TASK option and adding a task for "halt". Intended behaviour still seems off
-
- actions
- mission editor
-
(and 1 more)
Tagged with:
-
Hi everyone, I'm trying to replicate the tanker tracks as found in this document (unrestricted distribution, pages 88-90) on the Marianas map. In order to set up the orbit, I'm using the switch waypoint command, where upon completion of the current racetrack, they'll switch back to the first waypoint of the racetrack. Once on station, I want the tankers to keep performing the racetrack for 2 hours before returning to base. The set-up is fairly simple: Tankers will takeoff and fly their route Upon reaching their respective ARIP waypoints a flag is enabled (*TANKER NAME*_ANCHOR) This first flag is used as a condition for a 'switch waypoint' command at the last waypoint of the racetrack, which will switch their waypoint back to the first waypoint of racetrack. After 7200 seconds have passed since *TANKER NAME*_ANCHOR turned on, the flag turns off and a *TANKER_NAME*_RTB flag turns on. The *TANKER NAME*_RTB flags are used to trigger a separate switch waypoint command, which will switch their waypoint to the follow the proper exit route (typically back to the ARIP waypoint and then to the AREX waypoint, and then follow their initial route backwards). Everything works perfectly, up to stage 4, because instead of returning to base after 7200 seconds, they return to base after completing 2 racetracks, as if they decide to not obey the switch waypoint action. I've double and triple checked the flags for each action (waypoint actions are given unique names and it's absolutely brilliant now that we can give flags custom names). I've tried disabling the 'RTB on bingo fuel' option - no effect. I've tried making a separate trigger zone at each anchor point and using a triggered switch waypoint (using AI SET TASK/PUSH TASK) - no effect. Any ideas? tanker_tracks.trk New Mission (Tankers) #01 (30-07-2005, 09-00-00, Hist. Weather).miz
- 4 replies
-
- racetrack
- switch waypoint
-
(and 3 more)
Tagged with:
-
My idea would be that a 3rd party, like all of us scripters / mission creatives here, would be able to write a 'plug-in' that would add a new CONDITION or ACTION to DCS. These would be bundled with DCS in each update as new ones are submitted and vetted by ED. That way, new mission editor features would be available to all players and would no longer require the general user to learn lua. All that work will have been done by the plug-in author. They could have a different colour or an asterisks in front of them, telling users they are from a 3rd party not ED in case they only want to use vanilla CONDITIONS/ACTIONS. However if the 'plug-in' api and submission process was rigid and thorough enough then there could be no distinction between any of them. What this would allow is that rather than waiting decades for a new CONDITION i.e. Group's Altitude AGL above Limit, a scripter could write, using the DCS Scripting Engine code alone, the code for that, and then everyone can take advantage of it. It would negate the need and complexity of 3rd party super-scripts like MOOSE and MIST and the problems that come with them, because at the end of the day, everything any script can do, will be done via the DCS Scripting Language code. These 3rd party script libraries just obfuscate and work as facades for the DCS SL and add additional features by doing all the legwork for the end user's benefit. Having M.E. Trigger plug-ins would give EVERYONE the power of these scripts, in bite-size atomic CONDITIONS or ACTIONS and thusly relieving some of the pressure from the M.E. devs to add this stuff as they work on more larger and general improvements to DCS. What do you think? @Flappie Is there any way you could make sure the M.E. devs or people who do planning could see this please? I know it's a big ask, but this would radically expand the Mission Editor and mission capabilities for all players, without having to learn lua or scripting or use 3rd party libraries. Thanks.
- 2 replies
-
- 1
-
-
- actions
- conditions
-
(and 3 more)
Tagged with:
-
This doesn't (thankfully) happen when changing the CONDITION -> 'FLAG IS FALSE' to 'FLAG IS TRUE' and vice versa. Seems to be localised to the ACTION only.
-
Hi, guys. I tried that setting up the route with Waypoint 4, through cockpit trigger action.. but i couldn't. Like the picture, Only '4' is showing me on KU. What did I make a mistake?