Search the Community

I flew the Apache in the Battle of Saipan mission. I started up on the ground, entered in 5 waypoints into the TSD, saved the mission, exited, loaded the mission and suddenly the Apache was 50 feet in the air and I crashed. I loaded and started again (the mission I'd saved with the Apache sitting on the ground), went full throttle, started the game, and flew away. All my waypoints had gone. I had also lost my wingmen, and the option to communicate with them on the radio - it was now blank. Some of my systems that had been on when I saved the mission, were now set off. Does the save mission option not work for helicopters?

Mission State Save Guide Mission State Save is a new feature that will be particularly enjoyed by those of you with basic mission-editing skills that want to play scenarios you have created and play over several sessions whilst preserving and carrying forward mission progress, without complex scripting. Mission Save works by generating a new mission file at any point during the flight. The generated save mission carries over different parameters of missions such as date/time, all units state and location and other mission state relevant parameters. We’ve also added some support for this feature on a dedicated server level. We are releasing this feature in an early Work-in-Progress state to gather actual community usage feedback, which will help us refine and prioritise future improvements. We will also be looking at requests from script creators. Let’s take a look at some details about this feature. Operation basics As was mentioned before mission state save result is just a new .miz file which is just new mission file that you can open in the mission editor for adjustments or just play right away. This concept was used by some of our amazing community content creators, and it is our variation of this approach. Mission State Save is available in multiplayer and single player. It does not work with protected paid single player campaigns, for these, a separate solution is needed. There is a new special format of mission file .sav made specifically for dedicated server just to accommodate some automation, we will see its details below. What is being saved? Making full identical save is quite hard task if done in environment of sophisticated detailed simulation so to make something usable faster we have opted for approach of saving certain parameters that matter for mission theatre. Here is the list of saved parameters with its nuances: Time and date Dead units/groups and statics removed in save Position, speed and waypoints state of groups/units saved (they will start at the same position where they were at the moment of save, save cannot include waypoint advanced parameters for now) Units/groups and statics that were activated or created with the script during mission also will be present in state save Spawn points and internal fuel state of player/client units/groups saved and move to air if you save mission while enroute. In saved mission your spawn will be at the position where you left it in the air or on another airfield. Save process will place aircraft at the minimum altitude of 150 meters if they were flying lower at the moment of save. Player/Client and AI controlled aircraft weapons state is saved (Nuance here is that for now multiple point racks like triple mavericks etc. will be considered used and spent and will be removed from plane loadout in save even if at least one weapon on them is used). Partially used fuel tanks are not accounted for in save as we don’t have partially filled fuel tanks options for aircraft loadout currently. Aircraft malfunctions are applied at the start of saved mission if there were any at the moment of save. (For this aircraft need to have on demand failures modelled and best example will be A-10C) Warehouses state is saved All scripts and triggers are saved as they were in the start of original mission. Saving process does not touch them (there can be many scenarios variations for processing these in the save but as of now there is no clear best process logic for it for us yet. For API scripts authors can take it into account and for triggers you can remove not needed triggers manually in mission editor if you think you won’t need them in next session). We will be looking at feedback to potentially adjust this in future. How to use save mission state? In single player you can find “Save Mission” button in ESC menu: It will open dialogue window where you can name and choose where to save generated save .miz Additionally same button is available in the mission debriefing screen (save time will be moment when you have quit the mission): For Multiplayer Mission State Save will be available only on server side. If you host mission not from dedicated server then as host you will have same “Save Mission” button in ESC menu. For Dedicated Server there is new button in its web GUI interface “save mission as..” which you can use at any time during mission to save current state. We have added new mission format for dedicated server: .sav. It serves only one purpose - automation for running mission autosave. .sav is essentially same as .miz, you can even rename it to be .miz and treat it as such. But dedicated server treats .sav differently and difference being “.sav” mission can be autosaved into same file when you stop server or restart mission if dedicated server option “Autosave .sav files on mission stop” is activated. That way you just need to launch same mission in list to continue from the saved state. The server has a mission list and if you are rotating through missions in list, you may have missions that you want to save automatically and some missions that should not be saved, new “.sav” format helps to differentiate between those. Later we want to add ability to save mission state while mission is running into same file and do not create new one on save for .sav files. New Scripting API: world.getPersistenceData(name) Read persistence data identified by name. Returns Lua-value stored in this miz/sav by a given name or nil if no value found. Name MUST ONLY consist of the following characters: [a-zA-Z0-9_ -], that is Latin alphabet, numbers, space, underscore and dash. This API is to be used in the initialization part of the script. During mission it will always return data stored in the original miz/sav, data is updated ONLY after simulation finishes. See world.setPersistenceHandler(name, handler) for further details. world.setPersistenceHandler(name, handler) Registers a handler for generating persistent data when saving simulation state. Name MUST conform to the same restriction described above. Handler MUST be a Lua-function which takes no arguments and returns persistent data as a Lua-value (boolean, number, string, table). The returned value must be JSON-serializable. The handler will be called every time the simulation state is being saved. Note, that saving a state during mission run-time DOES NOT update the values returned by world.getPersistenceData(name) - these will continue to return persistence data as it was on the start of this simulation. This is done in order to avoid state saving to influence the simulation. Important note about the API: the use of names as keys for persistent data allows scripts to read data from any name they know. This is intentional to support cases where some scripts and frameworks might support data saved by other scripts and frameworks. Defining common names and data formats left up to framework authors. Storage format: Inside .miz/.sav the persistence data is stored as persistence/<name>.json files. Source: https://www.digitalcombatsimulator.com/en/support/faq/scripting_engine/

I'm liking the new mission generator. However, for some reason, if I try to save the mission after the enemy units are not included. With no enemy units the script ends the mission immediately. If I open the mission file with the mission editor, same issue, no enemy units.

So here is the problem --i have saved all my aircraft input folders -- bought a new computer win 11 --reinstalled DCS -- as expected all input bindings are back to stock ... so now no mater where i replace my saved input folders , either in the saved game folders or the ED core folders . still have stock binding .. saved files did not change anything ---so it looks like spendings hours and hours re-doing the bindings == PLEASE SAY IT AINT SO ? Have i done it all wrong or ?? === Not looking forward to re-binding Everything ===any ideas or Help --Thank you ...

Only yesterday I started testing the new Save Mission options, but, so far, it has been no joy. If I land the plane, leave it running at the end of the runway and save the mission, then, when I load it again, the plane ALWAYS appears cold and dark parked in one of the parking spots, usually the first one. Saved Mission - 02.miz Saved Mission - 01.miz

Hello, I found at last time to fly your great campaign and so went to mission 02 (for which I had some pain to start some triggers due to my lack of mastery of the F4, but this is why your campaign is so great, it makes us progress). I saw there are 6 missions 02a to 02f, so I took my time and relax when in the 02b, and even did not finish the full 02 missions. I was thinking the next time I'll launch the campaign I'll have the capacity to refly the part of 02a I'll have finished. But finally there is only "02a Departure" and then 03a departure...No "02b - Pure Pursuit" and so on... I copied the missions into my mission folder because the ramp start and go to fly is boring to redo a lot, so I hope I'll be able to refly them. But is this situation normal ?

So this issue happened to me now a couple of times. 1st issue : When pressing the 'save' button in the mission editor, it saves the mission as it should. However, when one presses 'fly mission' or presses the 'exit' button to exit the ME, it says there are unsaved edits and opens the option window once again to 'save' or 'exit without saving' or 'cancel' , when one has just saved it. 2nd issue : I have the auto save option enabled in the ME, and after a while the ME gets stuck trying to save the mission file, and the save button stays enabled in the editors column on the left, but not saving the mission file. At this point, you can no longer save all the editing done since the last auto-save/ save. This causes the created mission file to get corrupted and one has to 'exit without saving' and rendering the mission file unusable...... so all the work done will be lost at this point. This is a horrible experiance !!! All the work done for nothing. Now i found a way around and having fortunatly the autosave files still intact, but the mission file is at this point no longer accessable ! So i restarted DCS, opened a new mission file ( at this point the mission file can no longer be accessed, and then opened the backup file saved from the auto save option from the last save, and then load it. Then save it once again as for example mission 1. But then all the work done after this last save is gone ! If i did not have this auto save enabled, all the created work would be lost forever ! * image showing the save button stuck and not saving anything. Also showing the autobackup timer on the top left non responsive. Please have a look in to this matter, DCS - Team. Kind regards, RWCnull

The Save Game feature is finally here. It's a great step in the right direction, and I'm sure it will be improved down the line and make DCS a more user friendly experience. BUT You need to remember that I have the same access to DCS as you: the mission editor. I can guarantee that my missions work, but I cannot guarantee that the save game feature does. Based on official communication this first iteration is currently aimed more at simple missions, not extremely complex ones like my campaigns, where all sorts of triggers and scripts are firing all the time. So please do not post any bug reports that happened AFTER you saved and loaded a mission, because I'll have no way of figuring it out. I'm sure ED will keep improving the feature based on user feedback and one day you'll be able to save the most complex missions at any time. And that will be a real game changer. Thanks!

So I created a F16 DTC profile in the mission editor. When I went to multiplayer and selected the DTC, that profile was not in the dropdown (dropdown empty). Are saved profiles suppose to be available in MP missions ?

I'm trying to change the FOV setting for a few aircraft. But, when I click my button to set zoom back to normal, its setting the FOV back to the default for that module. i.e. I'm trying to fix the FOV for the Phantom and when I zoom in and out then click to reset zoom, it defaults to 105 deg. After I have changed it to 80 deg in the UI. Is there a way to save or lock the FOV to a custom setting?

Hello everyone, First of all, thank you very much for the new Save Mission function. It's a great innovation. It brings so many new possibilities to everyday DCS use. My suggestions for expanding this great feature would be to save the status of static map objects, for example, to display a destroyed power plant as destroyed even after loading the saved mission. I would also like to see the status of your own aircraft, or rather the cockpit, saved. I also noticed that helicopters that are parked uncontrolled on the ground are parked in the surrounding airfields after loading the saved mission. That's all my feedback for now. Thanks again for this great feature. Best whishes Mario

Encountered major 2 problems when trying to use the save feature with dynamic spawns 1) Dynamic spawned clients get saved as Rookie NPC Expected: don't save dynamic clients at all, they should dynamic spawn again in the saved mission. Cause: currently all alive units get saved Proposed fix: do not save units with ID >= 1000000 (in me_exportToMiz.lua, parseDebriefing) 2) NPC spawned via coalition.addGroup lose their unit and group names Expected: unit and group names are retained (needed for scripting, and to not have "vehicle1" for a soldier) Cause: the miz export combines debriefing.lua with the mission file, as units are not present in mission, and names missing in debriefing.lua, generic names are used Proposed fix: add unit and group names to the debriefing.lua

It's probably somewhere already on the Forum, but I was having a problem saving my TrackIR profile changes - specifically the Motion Control slider, as well as linking the profile to DCS in the games pulldown window. Searching online I found the solution was to just run TrackIR as Program Administrator (right click when starting it), then make the changes and save.

Hello Eagle Dynamics, I want to report the following Bug: Thank you for your time and support. I appreciate your efforts in improving DCS very much. Best regards Harry

Hello Eagle Dynamics, I want to report the following Bug: Thank you for your time and support. I appreciate your efforts in improving DCS very much. Best regards Harry

I’m not sure if what I’m asking is possible or not. With the new update that allows saving progress in the middle of a mission, will this feature be available in this campaign? It would be very interesting to save progress at certain points to later practice specific aspects of the flight or even to complete a mission over several days if it's not possible to finish it in one go (especially for missions that last around 1 hour and 30 minutes). Best regards.

TL;DR: In its current incarnation, DCS's 'save state' is IMHO unusable and will mostly serve to annoy players who believed that they can save and continue a mission like in most other games, only to find out that they were severely mistaken. While there might be the odd instance where a re-loaded mission behaves almost as expected, the vast majority don't. IMHO, ED would be better served if they did not advertise this feature, it will cause people to become frustrated with DCS. WHAT TO EXPECT? When ED announced that DCS now supports mission state save, they left open what this "state save" actually means. Without guidance nor explanations, people will assume that "DCS Mission State Save" means what they individually hope that it means: a save feature that allows them to save a mission in progress (say two hours into a three-hour mission). A few days later they then try to resume where they left off. The results are ugly. IMHO, DCS state save is in its infancy, unsuitable even for trivial use. If DCS were a word processor, it's "save" ability would be akin to being able to save most upper case letters, and some numbers, but nothing else. Formatting, punctuation, blanks, images, most numbers and all lower-case letters can't yet be saved. You decide if that means 'usable save' in a word processor. In a nutshell: Technically, DCS missions can save some state. Usually, it's not what you need. IMHO, in it's current form, "DCS Mission State Save" is a first experimental step that has no tangible use for players. It barely works, and in a too limited way. Even trivial use cases can fail spectacularly. HERE'S WHAT I TRIED; In a super-simplistic mission with player-controlled hornets (one ground, one air), one blue ground unit and 4 red ground units. I started the mission, performed some simple settings and saved it after a few seconds. I then started the saved mission, comparing what I saw last in the original mission with what I saw first in the restored mission. I also opened the saved mission in ME (and a text editor) to verify what the changes consisted of in-file, how these changes are reflected in Mission Editor. So what are DCS's current save abilities? AI GROUND FORCES (placed with Mission Editor) Units that were destroyed are removed from the mission, there is (sadly) no debris left in the places where a unit was killed. A bit disappointing, but OK. Paths are modified so that if a units was halfway between WP 2 and 3, that point now becomes the new initial points, and waypoints are moved up. Yes, the original path is modified, probably screwing with any WP actions. But that becomes irrelevant, because: Waypoint actions are scrubbed. So if you placed units with ROE HOLD, they are now all ROE WEAPONS FREE. Kiss goodbye any training mission that you saved in progress, it's now become hot. Expended munitions are not saved, so all units return with full health and full stock. Paths can receive a mysterious 'span' tag depicts a completed path Player Planes (used an FA-18 for tests) NO COCKPIT STATE is SAVED. Worse, a hot plane (engines running on an airfield) is turned to a cold one. Radio, Radar, Light, or any other settings are gone, as are weapons programming. If your IND was aligned, it no longer is, etc. This means that using state saving to create training missions that require exact cockpit setup (like setting up your glide bombs) is straight out. Analyzing the .miz shows that on saving the player aircraft, DCS saved the player aircraft as "start from ramp", which was not where the plane was, and means that it will be cold, all settings forgotten. NO PLANE NOR AVIONICS STATE SAVED I then entered the cockpit of a flying Hornet, entered a gentle bank turn, enables AP, BALT, and started a circle, switched the left MFD to HUD and then turned off the left MFD. After 1 minute, I saved, while heading 050 at 6200 AGL. After loading the saved mission, I entered the cockpit with the hornet wings level, AP off, BALT off, left MFD turned on in default configuration. SCRIPTS A script's state (the value of all variables) isn't saved. Scripts start with the mission and do not know what has changed. They assume that the mission has just started since timer.getTime() will falsely return 0 at the mission's beginning. No scripting API for save state exists. Flags All flags are reset to 0, no flag state is saved mission time Mission "time of day" is advanced to the point where the mission was saved. WARNING: timer.getTime() is reset to 0, so if you have any trigger that uses "Time before" of "Time later" you now must use the new "Absolute time" and perform some silly time conversion realtive to 00:00:00 local time, and can no longer rely on time relative to mission start. That means that if you move the mission's start time by just a second forward or back, you must re-calculate from hand all your triggers. This incredibly bad design is hopefully just a stop gap until ED can come up with a better method. Mission.miz There is now a lot of spurious information added to the miz: 15k lines of failure information, and vehicle group's 'unwound' paths are put into "span" records. So, IMHO Mission Save State is unusable in it's current form for for anything but the most trivial missions. ED should be aware that people expect a lot more, and many will be frustrated. This first step IMHO does not reflect the abilities of ED's talent, and should not have been on public display, it opens them up for ridicule. I'm hoping that upcoming releases dramatically improve upon this state. state test 0.miz

Inconsistent codeword for SAM destruction on the Kneeboard. The correct one The wrong one at the 4th row

When saving a mission objects that were not there before would appear; when reloading a save there was a stinger in a place where it never originally appears; this was also the instant action medium

After take off CAJUN starts flying to waypoint 1 but at every time he just looses all thrust and starts losing height, eventualy it drops to the water. Anyone else happends the same? I tried fly near him but no luck.

Great missions, but the briefing is hard to use. it’s long-form and mixes taxi/departure, ROE, kill-boxes, codewords, and divert steps, so the essentials (frequencies, waypoints, fuel gates) get buried. A single kneeboard “Quick Flow” — bulletized by phase (Ramp → Taxi → Takeoff → Push CHAINSAW → CAP → RTB/Divert) — plus one radio table and waypoint list would make it flyable without pausing. Please keep it straight to the point.

After updating to both the first 2.9.15 and 2.9.15.9509 hotfix, wav files located in the saved games folder no longer override the default sounds. Going back to 2.9.14 restores this functionality.

I attempted to save a mission using the Cold War Germany map, and while in the past I've had issues where DCS would crash, this was the first time I got a blue screen which caused a reboot. Interestingly, the last thing noted in the log (attached) was "not enough memory" issues: 2025-05-08 16:05:36.263 INFO APP (Main): try to write track file 2025-05-08 16:05:36.280 ERROR EDCORE (Main): More out of memory in ed_malloc for 2852520 bytes. 2025-05-08 16:05:36.280 ERROR EDCORE (Main): More out of memory in SharedBuffer for 2852488 bytes. 2025-05-08 16:05:36.280 ERROR EDCORE (Main): Not enough memory to decompress: mission This seems odd as I've got 64GB of RAM, and due to playability issues (i.e. huge reduction of FPS) on CWG map, my paging/swap file is also 64GB (a large swap file seems to be needed for playability on this map, for now). dcs.log

I've tested DTC and it seems like options SAVE / SAVE AS just create a temporary session file for as long as we stay in the editor. It doesn't actually save any file. When you quit the editor, you will loose that files. The only way to save file to your disk is EXPORT option. Is it suppose to work that way? "Ghost" files saved only for editor session and "export" for actual save?