Sedlo

Thanks, must have missed the previous thread. Admin, feel free to delete.

AMRAAMs too heavy? Just tested this out in a clean mission... Seems that the AIM-120C weighs about 2000lbs in game? With the load I started with, jet should weigh 29030lbs... Once in game it was about 4000lbs heavier. When I launch an AMRAAM, the weight of the aircraft (on the Checklist page) goes down 2000lbs. Track attached. Open Beta v2.5.5.34108 2000lb amraam.trk

Updated to version 2.0! I've totally reworked all 4 missions to update it to a more modern standard. Easy Comms are now disabled, you will have to tune your radios to the correct frequencies in order for the missions to progress (don't worry, you'll be prompted when to do this in game). I've updated a ton of triggers, added random threats, and generally made the campaign more realistic and enjoyable as well. I hope you like it! DOWNLOAD LINK: https://www.digitalcombatsimulator.com/en/files/3301137/

Good call, will try this!

Seems like it's fixed with today's open beta.

\I deleted one of those other poly groups, then changed the script so that {'[blue][plane]'} got captilized {'[bLUE][PLANE]'}. It's working now! Thanks to johnv2pt0!

Interesting! Thanks for the info! I've got two units on the map which define zones, but they are not touching each other at all.. It's strange!

mist.flagFunc.units_in_polygon help Hello all! Checking the examples on the hoggit wiki, it would seem the following code should fire flag 300 to true work whenever a BLUE aircraft enters the zone... do mist.flagFunc.units_in_polygon { units = {'[blue][plane]'}, --unit names zone = mist.getGroupPoints('poly'), flag = 300, } end However, it seems to be making the flag true at almost random times..... Anywhere from 10 seconds after the script is loaded, to a few minutes. The problem is, there are no BLUE aircraft anywhere near the Polygon I've defined (unit name is poly). Any suggestions?

Updated to version 1.56... Tweaked some triggers, updated labels. Labels will be dot only, and will all be monochrome. This will help with spotting aircraft, but won't automatically let you know if they're friendly or foe. DOWNLOAD VERSION 1.56: https://www.digitalcombatsimulator.com/en/files/3300770/

Updated to V 1.56 https://www.digitalcombatsimulator.com/en/files/3300770/

Scott, I'm really happy to hear you're enjoying it... Making these types of missions is something I really like to do, and when I hear that people are enjoying them, it really makes my day. Cheers! (PS, if you're a Hornet flyer, too, this mission is available for that jet as well. Plus, I've got something in production now.... :-)

Make sure your left side (Comm1) radio is on 295.4, otherwise it won't... They're also on TACAN 31X. Tanker is hidden on the map, it's something I can change later..

Wow.... Was in Mostar a few weeks ago, and it got up to 43 C. That was pretty darned hot. Stay hydrated! Back home now and a pleasant 27 degrees and sunny.. Perfect.

Awesome!

FWIW, I'm getting the same.. No : next to BALT, but the plane seems to hold altittude. I move the stick just a bit and then the : will often appear.

Red Flag - Harrier Edition NEW VERSION 1.55 by SEDLO OK, made a minor, but significant change to the mission... The labels are now all one colour, for both Red and Blue. This was done due some comments I've received, plus my own experiences in DCS. On my monitor, I find that spotting air targets is very, very difficult (more so than in real life). However, having labels on, even dots, makes it too easy, as you can easily tell a friend from an enemy from 10 miles away. I've modded the mission so that you will still see a dot for an aircraft at distance, BUT that dot will be a brown colour, for both red and for blue. If you keep good situational awareness from the AWACS calls (plus the brief), you should be ok. Let me know how it works out for you! DOWNLOAD LINK: https://www.digitalcombatsimulator.com/en/files/3215738/

Wingman Finder today.... Wingman Finder today....

Here's a test mission where you can see where the code goes. FIRING SCRIPTS.miz

Haven't tried it with group vs unit, but maybe... Put it in as a Do Script soon after mission start (or whenever you want).

They'll engage you, and fire, but their missiles will self destruct prior to impact.

This missile removal script still works pretty good: https://github.com/mrSkortch/DCS-miscScripts/blob/master/TrainingSams/trainingSams.lua

To reset the condition, do another one that says like, Time since Flag 200 is on 60 seconds > Flag 200 off.

Same thing for missiles, just change the event: Handler = {} function Handler:onEvent(event) if event.id == world.event.S_EVENT_SHOT and event.initiator == Unit.getByName('UZI 11') then trigger.action.setUserFlag('201', true) end end world.addEventHandler(Handler)

Add this script prior to your engagment will result in Flag 200 becoming true whenever the gun is fired: Handler = {} function Handler:onEvent(event) if event.id == world.event.S_EVENT_SHOOTING_START and event.initiator == Unit.getByName('UZI 11') then trigger.action.setUserFlag('200', true) end end world.addEventHandler(Handler) Make sure to change the UZI 11 above to whatever your UNIT Name is. So you could have whenever flag 200 is true, AND the player is within a zone, something will happen.

Editing Labels To Be the Same Colour My issue.... It's hard to spot aircraft in DCS with my setup, but using labels makes it too easy. My solution? Use the dot labels, but make it so that friendly and hostile units appear to be the SAME colour. Helps with the spotting, but you still have to get close to visually ID them. Thanks for everyone on the forums here that showed me how to do this, I thought I'd put it into one thread for reference. This also may not be the most efficient way to do it, but it does work for me for now. STEP 1: Find your Labels.lua file and make a copy of it. You'll find it at your: C:\Program Files\Eagle Dynamics\DCS World\Config\View STEP 2: Paste that copied file into a temporary directory, inside a file structure like this.... TempDirectory\Config\View (note the Config and View folders have capital C and V to start) STEP 3: Edit the Labels.lua file (the copy that you added to the temporary directory) with the following changes to change the type of labels that you'll see, and the colour of the labels you wish to see. (the RGB values I've put in above will result in a soft brown label colour. Change these to whatever you'd like. You can use this little tool to help: https://www.google.com/search?q=color+picker) Save this edited file. STEP 4: Copy your mission .miz file into your temporary directory like so.... STEP 5: Open your .miz file with WinRar... Now, copy your Config folder from your temp folder directly into the Winrar window.. STEP 6 You'll get a little warning dialogue that pops up asking how you want to save it... I've found I have to leave every thing the same, if I rename the file here it won't work for me (if you can help me get around this, please do) Anyway, just click save And you'll note the miz file size has grown by 2 bytes or so. STEP 7: Now, I rename this modified file, copy it back into where ever I keep my mission files. Now I've got labels, but they're all the same colour.