Compact Foothold-style mission for helo ops

[01G8R]

I can't seem to get the F-16 slots to work properly.  When I select them it just spawns it as AI.  I even tried deleting the F16 and adding a new one.  Same behavior. 

[Floyd1212]

Ah, I think I know what's going on there.  My buddy asked me to throw some in there for him, and I used the wrong F-16 unit.

Try changing them out to F-16CM bl.50 and see if that works.

[01G8R]

Yep, that fixed it.  Thanks.

[Ettan5]

Hi, I get an error with this mission. pleas help.
 

This is the line in 161. bc = BattleCommander:new(lfs.writedir()..'/footholdCyprus_v1.lua', 10, 60)

Edited March 19, 2023 by Ettan5

[Floyd1212]

This looks like you haven't followed the steps to enable file system access to allow the persistence file to save.  Follow the instructions in the first post of this thread.

You have to repeat the process after each patch ED releases as the changes you make get overwritten again.

[markturner1960]

Hey Floyd, thanks for this, been flying it a few times and getting a bit frustrated! I am taking off from Pathos in my Apache, very carefully approaching WP2, as first time, I got a SAM in the face. Have managed 3 sneaky approaches at NOE and hiding between houses and trees etc to get within range of the pesky SA8 on the coast....but each time get taken out before I can get a shot in...........I have edted teh lua file to enable persistence so 2 questions....how do I effectively "save" the mission and re enter it at the saved point? And any tips in dealing with the SA8 without shot? As soon as you get above 30 feet it sees you and starts shooting, I cant get high enough for a clear LOS without getting shot.....

[Wizard1393]

If you've followed all instructions correctly, persistence (state saving) is done automatically every 5 minutes iirc.

[Floyd1212]

I actually just uploaded a new "v2" version of the mission to fix some crashed caused after the 2.9 update.  See the initial post for the new file.

I also added FCR radars to some of the Apache spawns in each of the airfields.

The persistence file is written to once a minute, and includes information about what zones have been captured by blue/red, and how many unit groups are left in each zone.  If you restart the server, or come back to it later and play it in SP, it will reload that info from the file and pick up where you left off with the zone captures.  If this isn't happening for you, it sounds like you don't have the missionScripting.lua file edited correctly.

As for attacking a zone with a SAM, you can use the FCR now to help.  You can also approach the zone from a different angle to maintain cover.  You don't have to attack the zones in any particular order.  You can also call in a JTAC drone to lase the threat for you, and you can engage from a safe position.

Also, each time the mission starts over and restores the groups from the persistence file, they spawn in at a new (semi-)random location within the zone, so the next time you fire up the mission, that SA-8 may be in a different location within the zone.

[markturner1960]

Thanks Floyd, so to clarify, it does not create a new version of mission as the "save", it actually alters the mission as you go, so EVERY time you start it, it will pick up where you last left off....yes? What about Airframes I get shot down in? Are these no longer available? And you dont get to re spawn in the position where you last were, you still have to start from one of the bases? 

Am I correct in assuming that all the persistence does is ensure that whatever units are alive or dead at the "save" point are carried over to the next start? 

I am fairly certain that I have done the required edits correctly, is there an easy way to check if the mission has been updated? 

Edit, update: So I finally managed to sneak up on the pesky SA8 and introduce him to a Hellfire, which was great and also then managed to destroy another 5 or so targets in the nearby area before running low on fuel, so I returned to Pathos for re arming and refueling. I actually had to go out for a few hours then, so left the mission running but paused. DCS then logged me out and I had to re start. When I did so, I find I cant spawn anywhere as Pathos is in enenmy hands? Does that mean that I will need to use a fresh copy of the mission and start again? 

Secondly, is there any way to prevent this happening? There did not seem to be any Blue side AI around to help and this seems a lot to do without any AI to help.....

Edit 2: After posting the above, I decided to add some AI help for myself at Pathos, so I made a copy of the original mission from my downloads folder and did this. When I tried to start it, I was unable to spawn, as Pathos was in enemy hands.......tried the original unaltered mission and the same....how does this happen when the original file was in my downloads folder....? I thought that DCS would only update the mission file in my saved games? It seems that it has found and update the original in my download folder as well....is this possible? So now, it seems I cannot use the mission again......cant be right.....? 

 

Thanks! 

Edited December 30, 2023 by markturner1960

[Floyd1212]

The "save" file is called "footholdCyprus_v1.lua" and is probably located in the parent directly above your "missions" folder.  You can delete this file to start the mission over again.

The actual .miz file is not modified when you run the mission.  If you made a change to the .miz and ran your new one, it would try to load the same save file as the previous mission created.

This is a tough mission to play solo, I will say that.  It was designed for a small group of us flying 2-3 Apaches and an occasional A-10A.