Surrexen

The model for the Forrestal is brilliant! Well done Heatblur Hope you can add the Saratoga as well.

Hmm no particular reason really ... nobody ever asked for it before! I just put stuff in that you can drive and shoot with that I know about (which is very little since CA is well .... you know). That said, if you know of a particular artillery piece that is driveable and can be manually fired etc then let me know and I'll see what I can do about adding it in next week or whatever when the Forrestal is out. Also I found some of the weapon sounds are not working currently (magnum and rifle) because some weapon name prefixes changed somewhere along the line so that'll be working again too. Edit: I trust that Paladin's will suffice?

Well, I was going to remake Operation Jupiter so I could make use of the Mosquito, but alas the flak is kind of insane right now so there isn't much point. Also there is no AI Lancaster to go along with the Mosquito which is rather disappointing. For the modern missions, If the Forrestal ever comes out I will add it in as I've been wanting to do that. When the Apache comes out, I will add that as well. But really, I haven't had much time to fly for months so major changes are not likely to happen. I didn't know they added that scenery object trigger doodad either.

You can do this if you implement slot block into the mission and run it on dedicated server. Since I don't have a server I don't make it like this. I was led to believe that ED were moving away from the slot system entirely, so perhaps if that ever happens I'll be able to rework things to make it more logical like that.

To be on the safe side yes you should blow it up. There is some kind of magic ED algorithm that comes into play when opposing units are in the zone, I'm not entirely sure how it works but sometimes something like a tank will 'win' against a soldier or an ammo truck or whatever. I'd follow Ripley's suggestion and nuke it all from orbit, just to be sure.

The oil rigs are purely decorative, and were made red to avoid them being in the radio channels ATC list because I couldn't find a different way to stop that from happening. You could destroy them if you so wished, but there isn't much point, they are not part of the mission list per se. The default maximums for build totals are: Infantry groups: 8 Stinger groups: 4 Engineer groups: 4 Hawk sites: 3 Ammo trucks: 8 Rolands: 2 Abrams tanks: 4 Avengers: 3 Bradleys: 3 NASAMS: 2 Cargo containers: 24 An airfield is captured by dropping any infantry team into the zone (rifle/stingers/engineers) or moving any vehicle into the airfield zone and making sure there are no red units in the airfield zone. Hope that helps

I can't get them to work either, what exactly is the setup for them supposed to be?

Thank you for letting me know, I'll check it. I have most likely done something ridiculous when adding the NASAMS into it. Edit: Corrected versions have been uploaded for Scarlet Dawn/Snowfox Escalation/Clear Field Escalation.

Yes I agree it seems worse after the last patch and am seeing the same thing you are with 'export start'.

I have uploaded a new version for Scarlet Dawn to the user files section to swap over the SA-10's to SA-5's as originally intended, along with various other fixes. As always, I would advise starting new persistence files as names of units etc may have changed. I will be making a similar change to Snowfox Escalation to swap over the Bandar Abbas SA-10 to an SA-5 soon. Edit: Snowfox Escalation update has also been uploaded. Edit: Clear Field Escalation update also uploaded.

Indeed. Here I was going to update Jupiter and Crystal Sea to include the Mosquito but at the moment those missions are hosed. Likewise missions like Operation Jericho are also hosed.

Further to this, there also appears to be an issue when dynamically spawning WWII aircraft into a mission, there is a much bigger pause now when activating a plane (multiple seconds to activate instead of milliseconds). If you dynamically spawn in a modern jet there is no problem with it.

Yes I had just updated my response. I am noticing that dynamic spawns for WW2 content are taking much longer to spawn in than usual, and yes the maps are taking a lot longer to load. No issue with the modern jets on Syria etc.

You can just swap it over. Just don't delete the group and replace entirely as the scripts will not be happy with you.

I'm getting this issue both in Channel and Normandy, but I'm not sure that it's the Spit/P-51/P-47 that are the cause, I think it is something else but can't pin it down yet. Edit: If it is sitting at 'spawn objects' for a long time, give it some more time. Seems it just takes forever and a day to load now.

Put "silence" on them from the advanced waypoint commands. Alternatively, you can give them "no report waypoint pass" so they don't blab about every waypoint they hit.

Sanity has prevailed!

Looking really good!

I think there is a missing or broken entry in the enum attributes table for engage targets task, it appears if you set anti-ship planes to a search and engage task looking for "naval", the planes will ignore everything. But if you use "ships" it works fine. When setting an anti ship plane to a search and engage task "naval" is the default target setting. In the attached mission, Hornet 1 uses the default "naval" setting as targets, Hornet 2 uses "ships". Hornet 1 will ignore the target ship ahead of it, while Hornet 2 will immediately launch harpoons at the ship in front of it. Anti Shipping Search And Engage.miz

You can either do that, or grant the user you want to run it as the appropriate windows permissions to the DCS installation folder.

I updated all missions except for Scarlet Dawn for 2.7 a few days ago so make sure you get the latest version for 2.7 compatibility. If you have already done that, It is probably a user permission issue for write access to the folder. Try running DCS as an admin, run the mission for 6 minutes and then check your DCS World folder (the installation folder, not the saved games folder) for the generated lua's. If the lua's are not present, stop the mission and check the log to see what the error is. Operation Scarlet Dawn's 2.7 update is still in the manufactorum.

Oh dear. You're not going to like me very much in the next day or two.

Everything except for Operation Scarlet Dawn has been updated for 2.7 now. Hopefully it all works.

Unfortunately not, or I would have made the mission time persistent as well. The only way around it is to make multiple copies of the mission and set the weather/time etc differently on each one.

No idea about either of those problems, we don't get anything like that happen on the JDS servers.