Stuka

Are you using the correct keys to change the LASER code? When I change it, it is shown on the kneeboard.

Correct. So if it's even easier on moving targets, why would one work with multiple markpoints on stationary targets.

I actually always use autolase when I'm self lasing the gbu's. 'Latch on' is indeed a good method to make sure that the LASER is on during the whole weapons delivery. But when buddy lasing or marking with the LASER, I prefer latch off. It makes you more aware of the fact that it's on (keeping the button pressed), and prevents unnecessary LASER usage.

Now, try that on an advancing armored platoon:smilewink:

Duh, I for got to include that. An updated version is available on our site, that includes the targets list.

Post removed. Info outdated. All info in post #1

Thanks Dart ! 1 question: The setting ignore_radar_name = "lotatc_ignore_", Does that apply to group names, or individual unit names?

The 70's targets are still being worked on.

Reported

Like Eddie said: it's a more preferred setup of the systems that we use in the 476. I left it in the mission on purpose. Removing those sub folders from the mission like you did is perfectly possible and will not damage the mission.

That's the whole idea buddy :) Enjoy !

Post removed. Info outdated. All info in post #1

Thanks Maverick and 104th !

Not a bug. "Switch Waypoint" action is only implemented for aircraft.

was reported

Taken care of

reported

reported

Yes. Will be part of the template mission. By using simple AI on/of triggers, you will be able to have each individual threat present or not.

Yup, I took the Thunderbirds skin files out of that one, and made it into a livery for DCS. As you can see, looks still splendid :)

The 476 NTTR mission reflects the actual Nevada Test and Traning Range (NTTR) and is now available -->HERE<-- The mission represents the NTTR as existing in real life, modeled to the best as possible in DCS. There are 129 individual target complexes, with over 2000 individual desired points of impact (DPI) To make the mission also usable on lower spec systems, there are 3 versions of the mission included in the download: 476 NTTR P5.93-All_Ranges.miz : This is the enire NTTR 476 NTTR P5.93-Only 60s.miz : Only contains the 60's (South) ranges 476 NTTR P5.93-Only 70s.miz : Only contains the 70's (North) ranges Depending on your plans you can run the one that fits you best. Air Weapons Range Objects For correct functionality of the mission, you need to have our Air Weapons Range Objects MOD installed. You can find this on our site in the downloads. Range & Target Intel For information about each individual target, you can visit our website. On there the NTTR Ranges and Targets pages are available for those who have an account and are logged on. These pages don't only give you information about the ranges, targets and what they represent, but also the exact location in different formats, ROE's, intel pictures, and plenty more. This is part of our mission planning and training tools, and are continuous updated with additional information. Navigation points All points included in the GE overlay (see below) are available in the editor and as such also in the CDU of the A-10C. JTAC On FAC locations there are a couple of Humvees that can be used to take a JTAC role and help your buddies out with target spotting/marking/LASING. Coalitions Red: USAF Aggressors, Russia & insurgents Blue: Everything else. Clients At Nellis, most non-WW2 aircraft are available as client. Feel free to adjust for your own needs. Tankers and AWACS The mission has Tankers and AWACS available. Information is in the briefing of the mission. Adjust as you see fit. Some target images to give you an idea. Google Earth overlay To get to know the NTTR and find your way around , we have the Google Earth plugin to make things more visual In this plugin, you'll find the base grid, different airspaces, targets, tanker and HVA orbits, navaids, navigation points,... and lots more. To get access to this data, you'll need Google Earth. I've build everything into a network based Google Earth plugin. This allows you to point your Google Earth to a central managed file, ensuring you will always have the latest version. To get access to the data, all you have to do is to add a network link in Google Earth. The URL you need to point it to is: https://goo.gl/f7phhc After doing so, a new folder with multiple layers will be present in your "My Places". The initial layer selection will be always the same when opening the overlay. This initial view shows you the most used data. Nothing holds you to select/unselect layers and/or items to make the view like you want it for mission planning or creating mission briefing materials. The other cool thing about using Google Earth for this, is the fact that we can add other overlays that are available on the internet. What I found to be very to extremely useful are following: The URLs are what you enter in the network link. Earth Point Topographical Maps: http://www.earthpoint.us/Default.ash...kaXwRGx6W9f3g& MGRS GridLines by Nearby.org.uk: http://www.nearby.org.uk/google/grid_mgrs.kmz.php? Sectional Charts: http://www.chartbundle.com/charts/kml/sec.kml World Aeronautical Charts: http://www.chartbundle.com/charts/kml/wac.kml Terminal Area Charts: http://www.chartbundle.com/charts/kml/tac.kml IFR Enroute Low Charts: http://www.chartbundle.com/charts/kml/enrl.kml IFR Enroute High Charts: http://www.chartbundle.com/charts/kml/enrh.kml IFR Area Charts: http://www.chartbundle.com/charts/kml/enra.kml CONUS SAR Grids: http://www.chartbundle.com/charts/kml/grids.kml

A json file that can be loaded in LotATC to display the NTTR ranges grid to the controllers. Download here Currently, There's no terrain yet in LotATC for the Nevada map, so it will look still pretty empty until DArt is able to add it.

I created an add-on for Tacview that will add the NTTR grid to your Tacview installation. Download https://www.476vfightergroup.com/downloads.php?do=download&downloadid=488 Installation is as simple as placing the xml file in the folder "..\Saved Games\Tacview\Data\Static Objects"

This is reported to the devs.