Nagilem

You will need - Persian Gulf Map; F-18. You can also fly F-15 and F-14 as CAP flights. Mission briefing covers the comms and waypoint descriptions. This mission is configured to help you setup a standard cadence for take off, A2A Refuel, A2G drop, A2A SA and carrier pattern with landing. You start the mission on the hot ramp awaiting takeoff behind 2 14 Tomcats leaving for CAP duties for Texaco and Overlord. You are tasked to take out an Armed barracks on Siri Island. Initial setup is with Mavericks for A2G on your jet. Colt 1-2 is setup with SEAD to address any ground based radar threats. Feel free to switch up ordinance as you see fit. I've run this mission with Mavs, conventional bombs (CCIP and auto) and rockets. Colt flight will start with less than 50% gas and no bags, so at least 1 A2A refuel required or you likely be taking a long swim back to the boat :). The mission is pretty open ended so it *should* work with Multiplayer for training. There are enough CAP patrols where you may get pinged by red AC, but won't have to engage to complete the mission. You can also switch up which flight is Pilot flown to get in some A2A if you have the F15 or F14 planes. **** THIS IS A TRAINING FLIGHT, NOT ADRENALIN ALLEY - It's not meant to do anything but give a cadence to mission operations and use of the jet. There are no triggers or surprises - just fly, fight, and above all have fun. I also attached a simple CAT I recovery with the boat 10-12NM off your nose, steaming north at 27kts. There are some other great trainers (Bankler's for example), but I found I kept reading how I was doing instead of flying the jet, so I made this one to let me focus. There are no ups or extras in the CAT I file. This file is set in the Caucasas map, so anyone can use it if you have the F-18 or other carrier based plane. Mission briefing has the info for the carrier. Hopefully these help someone out there... Nagilem Training Day.miz Case 1 Landing.miz

@Sobe - Thanks for that. Mine looks identical for the lines setting up helios and for Viacom pro. I have yet to setup a tacview or SRS, though they are coming once I get my HOTAS working the way I want. That looks to be a few more hours of messing with code :doh:. Ah well, its only time... and I guess I am learning *something*… :megalol:

Hi Sobe - Thanks. I went back and checked everything again. Right now I have the setup you described (second monitor low). I tried the touchscreen on the right at first, but now that I have a simpit, I have them vertically with no issues on 1.3. All buttons, gauges and other panel views working flawlessly. I made sure when I started that my big monitor was always seen as number 1. I also did all of the touch screen calibration, so no issues there. What I find interesting is with 1.4, I never was able to even get the panel views to work using the export.lua AS IS from the Captain. So if I fired up control center, start the profile, I got the requisite front panel view on my second monitor -:thumbup:. Then if I tried to access any other panel (about, freq, nav, aux, etc.), the button would get the green line under it showing that panel should be active, but no panel appeared. It works as advertised when I use 1.3. Some other points - I tried running the control center as Administrator - no change I also removed any other software from the export.lua - I have ViacommPro I can see all of the panels in Profile Editor, and I can also see the A10 inputs and outputs on bindings As I said before, I could not get a clean singular profile with the default F18 interface and export.lua to exchange data with DCS for any instruments I tried. Switches - yes. Instruments - no joy. I do have my documents on another drive than C:\users. My docs is on D: with Saved games on C: Again no issue with 1.3. This is a new box for me so Windows 10 hasn't been activated yet. I can't imagine this would cause this issue, but will test sometime later this week. Glad it works for you. I'll keep digging around after the next update. This is new for me so I want to spend more time flying and less time configuring :smilewink:

First let me say thank you to the devs for putting this out there. I am excited to see this work! As someone who works in IT, I wanted to share some thoughts on my experience and what did and didn't work. This isn't to be critical, but rather to provide some feedback. Hopefully it makes sense and helps. This is one of by first posts here, so please bare with me. I've been trying this for over a week now and cannot get the F/A-18 Capt Zeen profile to work. The issue for me is that none of the gauges, switches, or views work. Even the Freq, About, and Nav panels never pop up. I was able to get the viewports working perfectly, so I can see the right and left MFD, UFC, IFEI, RWR and AMPCD. After lots of reading :book:, hitting Youtube, and and a few late nights, I figured out generally how things work in Helios. I tried multiple configurations of export.lua files and have never gotten the data exchange between Helios and DCS to work in 1.4 for the F18. I finally decided (after reading post after post here about export.lua problems) to verify the rest of my configuration. I downloaded the previous version of Gadrocs Helios 1.3 from Capt Zeen's site. I verified the export.lua files were the latest versions from Capt Zeens site. I fired it up and EVERYTHING worked AS EXPECTED. For kicks I also went back to 1.4 and tried to just do some basics (remove Capt Zeen profile and setup one with some basic gauges and such). I started with a fresh Helios profile, setup new interfaces (using the included F18 interface) to what is included in Helios 1.4, updated the export.lua from Helios 1.4, and used the toolbox components inside Helios for the F-18. I re-verified everything! After some tinkering, I found *I could* get buttons and switches working (master arm on touch screen would switch, in game MA would switch, AND DCS would register the MA state change), but the export.lua would NOT exchange data with DCS for any of the flight instruments such as ADI, Altimeter, etc. So - to recap - Used 1.4 with Capt Zeen FA18 profile - viewports work, but no gauges, switches, or panel views work with touch or mouse - Used 1.3 with same configuration - Everything works as expected - Tried creating new profile with all 1.4 generated interfaces and export.lua - no data exchange using 1.4 F18 export.lua. I have: See below for Specs on computer 3440x1440 Primary Monitor 1920x1080 Secondary Monitor - touch screen Windows 10 Home Latest software from Gighub and Capt Zeen website for Helios and F18 pit. VIACOM Pro - disabled for testing If you are a new user trying this, I would try 1.3 FIRST. You can download it from Capt Zeen's site.

WOW! How great is this game that we can choose so many different, high quality aircraft that have been so expertly modeled! My vote - F/A-18c only until the viper is ready. Lots of seconds tho....