Surrexen

As the title says, I cannot set the mission temperature lower than 9 degrees celcius.

P51-D-30NA seems to be missing a texture inside the cockpit towards the back of the cockpit behind the seat. It appeared that the P-51-25NA was fine though.

I have updated this with some script changes.

Had a couple of last minute things come up but it's looking good. Will probably leave it to test over the weekend. If nothing else comes up both this and the mission for Syria will release.

Bandar Abbas Intl parking positions J11 and J12: the roof is too low for an Su-27. Su-27's vertical stablisers are immediately damaged if they start in these hangars (possibly the other "J" hangars).

In multiplayer at least, flying at night in the MiG-15 the UV lights for the instruments will be on in a hot start, then after about 20-30 seconds they will switch themselves off and then cannot be turned back on.

v201 is up to address the A-20G's not bombing the mission target. Thanks KaptinKaos for reporting the issue.

They will attempt to bomb the current mission target only. That said, I have not had a chance to look at Jupiter for a while as I've been busy with other stuff. I will take a look at it when I get a chance and check it.

It appears to me that the smoke pod toggle button will only turn the smoke pod on. Once it is on, using the toggle button again does not switch it off. Using the individual buttons for smoke on and smoke off work fine though.

Nothing I can do about those issues. I believe the AWACS issue is something to do with dynamic spawns ... it used to work ... :music_whistling: Also waiting for the F-14A is nothing to do with client slots, but both missions are supposed to have it on the red side, so I'm waiting since it is supposed to be out this month. If it doesn't happen, then I'll rethink this plan. I also waited for the A-10C II to include it from the start. I plan to pretty much release both of these missions once only, so the extra testing time is also necessary.

+1 to this.

Just waiting for the F-14A to drop at this point.

That would be JustDude's server. The secondary server is running the pre-release test version of Operation Scarlet Dawn (Syria). The version of Snowfox Escalation is not the correct version though, it's a mish-mash and is soon to be replaced with the correct pre-release test version of Escalation. There is one final system I am currently working on which will plug into both maps. It's getting very close to being done.

You know the drill. Operation Crystal Sea is a persistent, open world PvE/PvP playground for the English Channel WW2 map. To allow the mission to provide persistency, it is necessary to de-sanitize 'lfs' and 'io' in MissionScripting.lua. The mission will still be able to run without this, but persistency won't happen. Download here: https://www.digitalcombatsimulator.com/en/files/3312257/ Please note the following: - It's a work in progress (just like the map ... ) - The Channel Map and WW2 Assets pack are required - Target report will just report "Grid XXXX" since we don't have any grid references in the map yet To Enable Persistency: Inside your DCS installation there is a folder called Scripts. Inside that there is a file called MissionScripting.lua, if you want persistency to work, edit this file (make a backup first if you like) and make the bit that looks like this: do sanitizeModule('os') sanitizeModule('io') sanitizeModule('lfs') require = nil loadlib = nil end Look like this instead: do sanitizeModule('os') --sanitizeModule('io') --sanitizeModule('lfs') require = nil loadlib = nil end Once you have done that, start DCS and launch the mission. The mission will then write out a list of dead units and statics to a pair of lua files inside the DCS root folder (it will update this list periodically, every 2.5 minutes at the moment). Once these files exist, the mission will load those files when it starts up and remove the units and statics that were previously destroyed so you can pick up where you left off

You've got nothing to lose. The MiG-15 and the Sabre are really fun planes. Massively underrated.

v200 is up Changelog v200 - Re-written to drop the Moose AI A2A Dispatcher - Too many other things to remember Enjoy

v200 is up Changelog v200 - Re-written to drop the Moose AI A2A Dispatcher code - Blue can radio for A-20G's to perform a pinpoint strike, Red can radio for bomb-laden MiG-15's to do the same - Other stuff you probably won't care about Enjoy

No I won't be using it.

Thank you for your interest. I have not wanted to post anything until I knew what I wanted to say or do but here we are, the time has come. I have had a pretty bad year personally (as many have), and as a result I am far behind in where I wanted my projects to be at. I have been chipping away at it though in the background and after many months of trying different things Operation Secret Squirrel and Operation Jupiter have received major overhauls and will soon be re-released like I originally had planned. Also a completely re-written Operation Snowfox (called Operation Snowfox Escalation) with entirely new mechanics is going to be released "soon". So what is different? Firstly, the major change, no more Moose AI A2A Dispatcher. This is the main reason it has taken so long to re-write everything and find a way to make it behave the way I wanted it to behave. Secondly, nearly all AI flights will depart from their airbases from the ground instead of the air spawns that I have used up until now. Operation Snowfox Escalation ...has an automated base capturing war going on in it alongside the usual stuff. The airbases are persistent between sessions in the same way the units and statics are. An AI general from both red and blue will dispatch transport planes and helicopters that will attempt to land at bases to take them over. As the mission goes deeper, the mission will escalate further, and the red AI general will dispatch strike planes to try to clear targets ahead of the transport. Al Dhafra and Al Minhad are the primary bases of operation so the flights will be somewhat longer, and the carrier will be on the Eastern side instead of the Western side of the peninsula (it is the supercarrier, not the Stennis incase you want to know). Operation Crystal Sea ...is the mission I am working on for the Channel map. It is at the same point right now as Operation Jupiter and Secret Squirrel, which is just fine tuning some of the recent changes I have made. Once I have finalised these changes, it will be released alongside Jupiter/Squirrel. Yes yes blah blah blah what about Syria? Operation Scarlet Dawn ...has been in the oven since the map released. It will use the same mechanics as Operation Snowfox Escalation. I am kind of hoping that the SA-5, and Mavericks/Harms for the Viper come out this month before I let it out the door, but we'll have to see what happens there. So there you go. :pilotfly:

Awesome :thumbup:

If an F-15 Spawns in parking spot 26 at Ramat David, it appears the roof is a fraction lower than the neighbouring hangars, and the vertical stabilisers get broken when it tries to taxi to runway.

I had an AI C-130 crash into the tree you are talking about when it was trying to land at runway 17 aswell.

MiG-23MLD AI will not taxi to runway from parking spot 21, it won't leave the hangar. Seems to be ok with a MiG-29A's or MiG-21Bis though.

Glad you like it :thumbup: You could edit the script functions to do that yes. The other option would be to make it do the missions sequentially instead of random, and order the mission list in the order you want everything to happen. I just made it random because that seemed like a good idea at the time.

Something caused the Moose AI A2A Dispatcher to stop running. As to the network status and airfield status radio menu commands ... no idea, it depends on what you actually changed in the scripts.