gmangnall

I think we'd all like a completly new 3D editor....but whilst stuck with this could we have a trigger which detects if a given unit is killed by a certain unit, group or coalition...this would be great for detecting blue on blue incidents....also bomb/missile LANDS in zone is much needed...rather than the useless bomb IN zone which detects a bomb flying through a zone

There seems to be a bug with airfield capture. It works ok with vehicles, but it does not work with infantry. i.e. infantry cannot capture nor hold an airbase. You could fudge it with 2 triggers e.g. part of coalition present/not present but the "coalition has airodrome" does not work.

Hey Night Train.....thanks for your comments and I am glad you like the tool! Im afraid that Im unable to help though - I am not actually much of a scripter. Maybe try one of the face book groups....DCS Missino Editors maybe????

From TAC-000 1.12.6.4.5 Waypoint Datum. Datum selections can be made through the ODU/UFC (option 4). Datums are identified by numbers 1 through 47. See Figure 1-169. The datum name associated with each number should be listed by the pilot on an admin or brief card. Selecting a new datum changes the latitude, longitude, and UTM of the waypoint/offset, but does not move the waypoint/offset symbol on the display. Datum transformations take place in the MAGR in approximately 2 to 3 seconds. While the MAGR calculates the new coordinates, the waypoint/ offset symbol disappears. The waypoint/offset reappears when calculations are complete.

TERM no longer seems to be working

Good spot Mistermann That's my tutorial! - I am glad you liked it. Its not designed for what the OP wanted - but it will do it.

An IR marker would be a fantasic addition so firnely units can use IR to signal their own position to friently aircraft at night. Not sure if they flash at a strady rate/are solid or have a coded flash (like morse code) but irrspective it would be a nice addition.

Fingers crossed. It's great to see that's where we are heading...but I feel it was rolled out too soon.

It's nothing to do with normal flight....it's a bug. The aircraft flies fine in autopilot for a few hundred miles and then starts to yaw slowly and then quickly excalates until you need ot take manual control and roll the aircraft to maintain straight flight (which is where the recording starts) and within a few seconds it goes completely out of control..

Can we have some more fixed artillery...more modern and long range systems

I have a very odd issue which happens on long missions. Here I was trying to find the maximum range of the harrier, however after about 400 miles the aircraft starts to veer right as if some rudder is applied....this gets worse and worse and by 500 miles or so you lose complete control. This is the video for the final few seconds of the MIZ file and as you can see the aircraft is yawing right and I am having to roll left to try and counter is...within a few seconds the aircraft completely loses control and explodes.....I tried this test at Syria and Caucasus. Harrier loss of control.trk

The new FLIR system seem to be very broken. Here is a BDRM showing up nice and brightly and it's dust trail appears hot (and bright) meanwhile a T-90 is stone cold and kicks up cold dust. I would imagine that a tanks engine bay woulld be at least as bright as a BDRM but it's plausible that it's not....but hot vs cold dust trials that's just wrong. 3 images of what you would expect from an MBT....tracks and engine glowing

What? It's a map...you can fly an f15 over Argentina...it is allowed . Ps the harrier is the best attack aircraft in dcs by a mile

I am starting to use the harrier for dogfighting.....please delete this thread!!!!!!!!!

Yeah - lining 12 tanks up is just for demonstration purposes. Should have checked on the metres vs feet...but as I mentioned the numbers I used are again just demonstrating the principle and you should use your own. Ideally I would have used one of the in game functions like I do in part 2 (IsTargetDetected) but bizarrely thats limited to 3 miles for visual and optical. As for the triggers you can reduce that as I had triggers for messages and could have used "time since trigger"....but you are right...this should be part of the core functionality and not relying on fudges and triggers.

I have just done a video on how to STOP the SFW being so effective against static targets and tomorrow there will be a follow on to limit the effectiveness of the tactic of stopping a convoy with a maverick...and then using SFW.

It's better than the Hornets. The hornet seems to have cataracts

Here is what I used where EWR-1 is the radar. I amHarrier1-1and my 2 wingmen are Harrier1-2 and Harrier1-3 local DetectingUnit1 = Unit.getByName('EWR-1') local TargetUnit1 = Unit.getByName('Harrier1-2') local TargetUnit2 = Unit.getByName('Harrier1-2') local TargetUnit3 = Unit.getByName('Harrier1-3') if Unit.getByName('Player-1'):isExist() then if Controller.isTargetDetected(DetectingUnit1 , (TargetUnit1 or TargetUnit2 or TargetUnit3) , Radar) == true then trigger.action.setUserFlag( "1", false ) trigger.action.setUserFlag( "2", true ) end else end The mission starts by activating flag1 and the script runs continuosly until a detection which turns off flag1 and thus stops the script. Flag2 then lets you action "other stuff"

Thank you.

Yes.....but there are distance limits. You're best bet are systems with a C2 units like the SA11 and SA10. They can have a single C2 unit and launchers spread many miles apart. (I suspect 50).

To irritate even further. I had managed to get one site set up so it behaved as I wanted (SA11-2 setting up in situ) and on clicking on it accidentally moved the entire group.....and now it doesn't behave the same way (now travels without setting up).

I have noticed some very odd behaviour whenn setting up some SAM sites....I have only tested SA6 and SA11 but I suspect it applies to all units which are mobile and multi component. Attached is a mission with 4 SA11 sites. Each are copies of each other but I have slighhtly adjusted the positioning of some of the components. Each of the 4 sites exhibits different behavious on startup. I was looking specifically at the search radar (but it's probably thhe same for the C2 unit). The 4 behaviours are: 1) Seach Radar Sets up in situ 2) Search Radar Sets up whilst travelling toward the C2 unit (which is the leader) 3) Seach Radar travels towards the C2 unit witout setting up 4) The Search Radar neither moves nor sets up. I am assuming that there is some sort of logic behind this, however with no specific details as to the logic it seems random. Either way without understanding the logic it's making certain map editor functions unusable (I want a dispersed site to set up - without moving as per the group SA11-2) SA11 bug.miz

I use therm in combined arms and turn the radar off - and fire (and hit)* quite happily with the radar off....but that's not the point. You could easily turn them on once "obviously" in range.....it's not an option for the AI. As Kang says the Rapier is designed to use no radar and radar was only added for forign buyers (I think Saudi Arabia wanted it for all weather capability) *in fact I am just uploading a video where I shoot down 4 A-10s with the tunguska with no radar. Should be ready in a few hours

When using JTAC it does not appear to recognise that you are carrying Laser Mavericks (E2/L) so will ask that you use guns or someting else. This happens with the A-10C II and the HHarrier (presumably other modules) so seems to be linked to the weapon not the plane.

Here is my LMAV video