If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Viper, out of curiosity, how far are you in your investigative work on how to enable a data cartridge for the A-10? I know Noodle once tried it but faced some roadblocks due to how ED designed the sim, or at least the A-10 module.

I know of two ways at the moment. They are more of a work-around, rather than a genuine DTC capability though. One way is what Gliptal's Cartridger does (basically generating lua files and placing them to appropriate folders in the DCS\Mods\aircraft\A-10C\... folder structure). The other way is to generate (different) lua files and place them to appropriate folders within the .miz file structure, exactly as you guys have done in your downloadable NTTR mission, as I have noticed. Plus export all the nav points into the mission file, so they are accessible via CDU.

The only proper way would be having an independent external DTC file (lua, xml or whatever) that you could load your DTC from. That is, AFAIK, not yet supported by the module though.

The exported (and in-game loaded) cartridge includes a TOT (ETA-locked) waypoint, a normal waypoint, and of course landing bases. The kneeboard mission card page includes, among other nav data, calculated QFE settings for each waypoint based on an atmospheric model.

Are you planning to add the ability to compute optimum cruise (range/endurance) altitudes and speeds for the aircraft where the data is available as part of route planning? If not is it something that could be added.

Are you planning to add the ability to compute optimum cruise (range/endurance) altitudes and speeds for the aircraft where the data is available as part of route planning? If not is it something that could be added.

The plan is to include fuel flow calculations for the route (to have remaining fuel and minimum needed fuel data at each waypoint), and take-off & landing performance data (Vr, take-off run, accelerate stop distance, landing run) where available. Calculating the optimum range/endurance speed and altitude sounds like a good idea. Thanks for the input. The most time-consuming part is converting the charts into empiric formulas, or replacing them with a regression model. The implementation into the navigation/performance calculation engine itself is the easy part.

Development Update #3
LFE mission planning, Export to DCS, new features

Dear all,

First of all, let me wish you a great 2018! As work on CombatFlite continues, new features have been added, the core functionality has been improved, and several of the inputs received either via posts in this thread or via PM have been implemented.

Let me share with you an example of planning a mission from scratch using CombatFlite and exporting it to DCS, thus creating a mission file (.miz) that you can either further edit, or fly it right of the bat.

Several core features make the whole process very straight-forward and intuitive. You can easily setup AAR orbits, holding orbits, CAPs, SEAD CAPs, as well as push and exit points, IPs, target points and DMPIs. Having done so, you can add flights and create their routes by snapping the waypoints to these reference points, orbit anchors, airfields, beacons or navigation points, or just by placing them anywhere you like. Likewise, you can assign DMPIs to individual strike flights just by a few clicks.

When the routes are done, you can do the timing of your mission easily, thanks to the ETA and TOT-centered (as opposed to mission starttime-centered) planning and a very convenient 'Mission rehearsal' tool. That allows you to playback the mission and see where all the different flights are at any given time. Doing so, you can adjust your ETAs and TOTs, making all the flights coordinated to your liking.

Moving forward, using the 'Snapshot' tool, you can create snapshots of the newly created mission flow (with aircraft symbols pinpointing their location at any given time, using the 'Mission rehearsal' tool), of the target area, or of anything you like. You can then add these as briefing pictures for your mission.

Having done all that, it is the right time to export the mission using the 'Export to DCS' feature. It creates a .miz file, that you can either open in the DCS Mission Editor and further tweak, or just go ahead and fly. Also, you can have a mission card for your kneeboard automatically filled-in. Among other things, it provides you with nav information, package composition, timing and deconfliction, and comm frequencies. An example is shown below:

Below is a short video showing the result:

Several interesting features are in place to help you with the planning process. Among these are waypoint wind arrows showing the wind vector for the given altitude, as well as sun position showing the azimuth and elevation of the sun for individual waypoints, together with surface wind arrow for target and IP waypoints.

The 'Slope visualizer' is another new feature, which shows the slope of the terrain within a chosen area as shades of green and red. The green areas depict a slope of less or equal to 15 degrees, while the red ones represent a slope of more than 15 degrees. This is very useful for helicopter pilots in particular, helping them choose a good landing spot in a difficult terrain.

The Line-Of-Sight visibility plot tool has been improved, and now incorporates the options to turn on/off the Earth curvature effect as well as the atmospheric refraction. This is extremely useful for the planning of low level missions, which make use of terrain masking.

The 'doghouses' shown along the routes have been improved. The data fields are customizable, so you can choose which variables you want to have presented in them. They can also be dragged to have them placed exactly where you want them in relation to their waypoint, and you also have the option to turn them on/off for individual waypoints of the route as well as completely.

Please note that it is all a work in progress. As always, any feedback and inputs are welcome.