Search the Community

This script can RANDOMLY generate CAS missions in a specific zone. "Random" means the location is randomly chosen, the 9-line is randomly generated and the target is also random.(However in finite choices actually...but you can customize it.) There is a demo mission with radio voice generated by AI in the attachment below. You can use those sound files in your own missions freely with the script(change 'miz' to 'zip' if you don't know how to see things inside a miz file). When you use the script in your own mission, you'll need to create zones and groups like what I did in the demo mission...So it's very important to check out the demo mission first if you want to customize the script. All of the interactions are through the F10 radio menu. You need to enter the mission zone first, and then use radio menu to get yourself assigned with a mission. Then follow the 9-line briefing, report IP inbound. After you have been cleared hot, kill the target and request BDA. The JTAC will tell you if the mission has been accomplished. If you want to try it in an online server, you can go to 36.150.108.238:10320. But the radio commands are in Chinese. Below are some screenshots (the 9-line is telling you that the target is marked by laser and red smoke, this is also randomly generated) null null null null null CAS-demo.miz InfiniteCAS_Release_v1.0.lua

Hi, I read this post: this link which talks about exporting the "Mouse Hover" Map Coords and i was able to implement a simple C# code, using OSC to get the map Coord however it does not work in VR. When not using VR, the Coords appear on teh top left and my code can pick them up after I take a snapshot. null When using VR the Coords may no be there at all like here: nullI also saw this post which also does not work in VR but will not help me since I need something to implement in my code. So, is there a way to export mouse Coords, perhaps via lua script or in any other way which will also work in VR?

Hi all I am trying to create a mission where a building has to be destroyed with a 2,000 lbs guided bomb, but where you'd first go "roof knocking" by detonating a Maverick over the building to warn off nearby civilians. Only problem is, this three storey building gets destroyed by the impact of the Maverick. And it has to be a Map Object, because there are no multi-storey residential or commercial buildings among the static objects. So I'm wondering... Would it be possible to make a script that increases the "life" points of a Map Object, or to make it "immortal" like you can do with units? Or would it somehow be possible to make a zone within which only certain weapons have effect? Any help with this would be so much appreciated - I've spent many hours fiddling with this already.

kinda like the CMDS for the F-16 I want to save time and have the MFDs preprogrammed

First-off this touches on a variety of combined arms and core game elements, so i opted to stick it here if it would be better in the CA section or elsewhere please move it or let me know and ill re-post there. Ok now that's out of the way, I have been working on some scripting to try and improve the Combined Arms experience, in doing so I have been looking at gameplay and general immersion, I have written two core scripts that improve these aspects (in my opinion) and I would like to ask for one of them to serve as a 'proof of concept' for what I would love to see added to Combined Arms specifically However in the shorter term there are some much simpler asks that are a mix of new functionality and bug fixes that will allow for my demo scripts to be greatly enhanced, and by extensions similar scripting options that can add a lot to a mission. So the two features are: CREW COMMANDS: This is a mix of immersion and better situational awareness, lets the player benefit from magic AI vision and just generally get help finding their targets. Inspired by GHPC (and my own armoured experience) this generates calls to targets instructing the player of the target type and guiding them to the target with traverse calls. The version in the attached demo miz is still what I would call indev, has some edgecase issues and target prioritization is very basic at the moment and could use a few more features (radio items to adjust priority of targets and shut it up etc), but its stable and I think quite a bit better than the current vanilla experience. Note a few vehicles (mostly modern ones) will call "Target Cease Fire" when you kill a target but i don't remember hearing any other commands/callouts VEHICLE ACCURACY: This topic has been done to death in discord etc but the other big script feature in the demo miz is my stormtrooper function, basically it aims enemies manually using fire at point, in the demo miz this unfortunately manifests as them mostly ignoring the player entirely until the player is the only one they can see, once you get too close it (currently) makes the player visible so they will engage naturally. The primary issues here stem from a few bugs that severely limit how much it can be used, when it does fully work its a good way to have decent volume of fire without the players being instantly killed. ALL THE WISHES: So what would I love to see added beyond a full crew command system ... Each title is hyperlinked to a related thread Unit Description Enhancements: This will allow both crew commands and things like stormtrooper to function better, having quick programmatic access to the rough max range a unit can shoot will generally simplify a lot of potential scripts well beyond what I have mentioned here Fire at Point Options: This would enable much finer control over the AI in DCS, being able to specify to any increased degree the weapons units should use when given fire at point (or attack unit/group), and being able to shortcut the aim delay would enable simulating a lot more tactical scenarios easily AI LOS Respect Trees: I'm linking a bug report on this issue, but basically would love to see AI detection factor in foliage and forests for obvious reasons Ground Unit Follow Command: Pretty simple, for some scripting due to the nature of things like ROEs, Alert State, and invis/immortal etc being group-wide its often necessary to use individual units (1 unit groups) for certain effects to be feasible, but them moving them around together is a nightmare, a simple follow command would help immensely. This would also be great in normal mission making, allowing 2 groups to move together easily before splitting up at some point Dead Vehicle Fire/Smoke Randomization: Would love to see just some randomness here so they dont all always spawn the exact-same size fire and smoke effect Ok so these next ones I have heard rumours are tracked internally already but im not sure.... LUA LOS Access: Allow us to check LOS between 2 points using whatever the back end method of doing so is (expose it through lua), somethign that factors in buildings etc instead of the current land.isVisible() which only considers the ground. Get Detected Targets/Is Target Detected: Change to Return detected units that are of the same or neutral coalition instead of just "enemies", same for is detected, allow us to query if a specific unit has detected another regardless of coalition. BUGS: Ok Final thing before I talk demo mission, there are a variety of bugs that are really directly hindering the ability to accomplish some really interesting effects (can tell you without these both my above-mentioned scripts would be a lot better) or generally hurting CA gameplay a lot, Some of these are fully reported, some not yet acknowledged but id like to highlight them: Restrict Target breaks Fire at Point: Cant stop units from shooting at the air or the ground whichever if I plan to use any fire at points Fire at Point vs ROEs: This one is a major pain and why I need to have the players be invis or neutral or have the enemies neutral to use stormtrooper scripts, as it stands if you give a fire at point, regardless of their ROEs they will immediately ignore the fire at point to engage any valid target they have detected and is in range Aiming in CA has some issues: Makes aiming at close range a nightmare at times Tank Engagement Range: Pretty obvious why this would impact CA stuff I think Infantry Chickens: Running like their heads cut off, makes them hard to include if the players will be looking at them for any amount of time Sherman FF HE shells: They dont explode, less important than the issues above but worth mentioning (the standard sherman's shells do explode) DEMO TIME: Ok Thanks for reading, ive been enjoying using LUA to force DCS to do interesting things, and used it a lot to enable experiences that cant exist without it, sometimes its to make something that should someday hopefully end up in the base-game, other times not so much but either way it can suck when a weird bug renders something impossible or overly complicated. Please check out the demo miz ive attached: DesertFox_demo_nomods.miz(its on Sinai and will require the WW2 asset pack) This has just a single blue JTAC/Operator slot, grab that, let the miz run atleast 2 seconds and then there are a handful of shermans called driveme that are in singleton groups with the rest of the shermans and drive (or feel free to advance time until the shermans are making contact with the enemy) Regardless play until you've faced off against the enemy tanks and please remember this meant to be a proof of concept, this is not meant to be a completed mission, feel free to reach out if you want more info on the scripts I am always happy to share.

Hi All, I found the g_suit paramotor under the crew members is deferent in each plan. Some have value 0f 0.75 and some have of 5 I read some post from 2019-2020 that say the value need to be from 0-1 some examples from the "aircraft module".lua F-15E g_suit = 2.0, MB-339 g_suit = 1, Mig-15 g_suit = 0.35, F-16C No sech value

Hey Guys I added 2 things to the script for the F14 VID and HSD. It's just that the screens from the F14 are too dark, everything is great on the F18 (brightness in the cockpit at the highest level)

I swear to Zeus this is killing me.. I have tried setting up an event handler to take certain actions when a unit dies, but is constantly running in to bugs. I have tried DEAD, KILL, UNIT_LOST and BDA with similar issues of initiator and target randomly not having any values (returning nil even though it should be there). In testing it seems BDA is the least likely one to throw errors. My suspicion is that since it is evaluated faster than DEAD and UNIT_LOST, it may get in and grab the values before they are removed from the table in memory.. Below is an example of what I am trying to do at the moment: local unitReport = {} local _mrkID = 1000 function unitReport:onEvent(event) if (world.event.S_EVENT_BDA == event.id) then local _objectSide = event.target:getCoalition() local _deadUnitName = event.target:getName() local enmyPt = event.initiator:getPoint() --buggy line local _enmyType = event.initiator:getTypeName() local _enmyWPN = event.weapon:getTypeName() if _objectSide == 2 then trigger.action.outText(_deadUnitName..' is hit!', 2) _spottingChance = math.random(1,10) if _spottingChance > 6 then trigger.action.markToCoalition(_mrkID,'enemy contact: '.._enmyType,enmyPt,2,false) _mrkID = _mrkID + 1 end end end end and attached is the error I'm getting. I have also experienced similar nil value issues when trying to access the killed unit, as if the program already forgot it was there.. Any help would be hot!