Surrexen

They don't spawn immediately. The Blue CAP flights can take up to 10 minutes to spawn.

If you have it set to ground starts then bombing runways will still completely stuff up the AI like it always does, which will usually cause the air dispatcher to fail. With air starts ... I don't think it would make any real difference but anything is possible. Feel free to test and let me know how it turns out. This mechanism is purely so that when you have already killed a CAP flight and are hanging around over a target area, that the next CAP flight does not spawn right on top of you but instead spawns at a further away airfield.

v129 is up Changelog v129 - A new mechanic to avoid planes spawning on peoples heads in the operational area has been added. If a player aircraft is within 40nm of an airfield, that airfields CAP flight will spawn elsewhere until the area around that airfield is clear of player aircraft. - The planes will spawn at the alternate airfields as follows: 1. Bandar Lengeh -> Lar 2. Havadarya -> Lar 3. Bandar Abbas -> Jiroft 4. Bandar-e-Jask -> Jiroft You can check the status of the airspace via the F10 menu and get a status report if you want to see what's what. Feedback on the new mechanic would be appreciated as testing time has been limited to say the least. Enjoy!

v123 is up Changelog v123 - A new mechanic to avoid planes spawning on peoples heads in the operational area has been added. If a player aircraft is within 40nm of an airfield, that airfields CAP flight will spawn elsewhere until the area around that airfield is clear of player aircraft. - The planes will spawn at the alternate airfields as follows: 1. Gudauta -> Maykop 2. Sochi -> Maykop 3. Nalchik -> Mozdok 4. Beslan -> Mozdok 5. Kuznetsov -> Gelendzhik Feedback on the new mechanic would be appreciated as testing time has been limited to say the least. Enjoy!

v110 is up Changelog v110 - A new mechanic to avoid planes spawning on peoples heads in the operational area has been added. If a player aircraft is within 40nm of an airfield, that airfields CAP flight will spawn elsewhere until the area around that airfield is clear of player aircraft. In this mission, this mechanic has only been added to 'multiplayer mode' where the planes are starting in the air (this is due to a lack of airfields further North of the operational area). Since ground starts at Lincoln are 50/50 anyway, nobody will probably care about this. - The planes will spawn above Mina instead of Tonopah Test Range, or above a dead FARP object Called "Current Ranch" that is sort of North of Rachel instead of Pahute Mesa or Lincoln County. Feedback on the new mechanic would be appreciated as testing time has been limited to say the least. Enjoy!

In the next update, player aircraft within 40nm of an active enemy runway will prevent spawns from that particular airfield. They will instead spawn at a further away airfield. For example, if someone is within 40nm of Bandar Lengeh, the CAP flight that normally spawns there will instead spawn at Lar. When the airspace over Bandar Lengeh is then cleared, the spawns will return to normal. This is to alleviate an issue where players would clear enemy planes over an operational area, only to potentially have a replacement flight spawn right on top of them. I am still tweaking things for this change but will hopefully get something out for the weekend.

That is possible to do but not something I would add myself. Giving everyone the option in multiplayer to end the mission sounds like a bad overall plan. Meanwhile, I am working on something that will make everyone's lives somewhat easier in this mission, Clear Field, and Black Spire. More details to come later.

The fact you said it is every 30 seconds consistently makes me think it's being caused by either the air dispatcher code, or possibly the scheduled function that checks the status of the mission target. I suppose any momentary pause would be far more noticeable in VR. Sometimes I get a momentary pause when plane groups spawn but not all the time and certainly not consistently every 30 seconds.

Was not going to add the F-14B. Waiting on the F-14A for the Iranian side.

No idea, I don't get that happening and my machine is old as the hills. Are you using VR?

You can definitely run this in single player. But depending on your system in VR you may need to reduce some settings. Alternatively try it on a multiplayer dedicated server. I built the mission originally as a single player thing (hence all the AI support call in flights). It runs on my 7 year old potato PC. But I do not have VR, only TrackIR.

Try the multiplayer list and give it a go on someone else's dedicated server and see how it is.

Try running DCS as an admin and see if that helps.

The files will be in your DCS installation directory. This is not the same as your DCS Saved Games directory. The files will only be there if: 1. Persistence was enabled before running DCS World 2. The mission was loaded and run for at least 3 minutes or so (it doesn't create them immediately first time through) 3. It had enough permissions on the directory to create the file

v112 is up Changelog v112 - Moose updated for consistency

v109 is up Changelog v109 - Moose updated for consistency

v109 is up Changelog v109 - Moose updated to be compatible with ground starts for AI again.

v122 is up Changelog v122 - Moose updated to be compatible with ground starts for AI again

v128 is up Changelog v128 - Moose updated to be compatible with ground starts for AI again

Maybe wait on this as I will be putting out an update for all missions fairly soon that contains an updated customised Moose file. I'm just getting very limited time to do anything right now with the current mayhem going on.

Works on my end. Fire up the mission and give it a few minutes to attempt to write out the files etc, and then close the mission and check the log file to see what it is complaining about. It'll be permissions or something. Also don't forget to de-sanitize MissionScripting.lua post update. Meanwhile, I am putting together an updated Moose file now that the AirbaseID thing is fixed. Will have to be tested before I send it out though.

It seems that the USSR faction only gets the default livery, while Russia gets access to all of them. Can you please give access to all the liveries for the I-16 to the USSR :)

It's a good question. This was something I was experimenting with in terms of adding extra things into the detection groups etc. But so far I haven't seen it make any significant difference. This is mainly due to the air dispatcher doing it's own thing. In this latest release I had even backed it off a little bit after I started to notice a performance difference when adding the new blue SAM sites into the detection network, so I removed all blue SAM's from the network. No difference there either. From what I can work out the air dispatcher adds any squadron planes it spawns into the detection networks by itself. And since the AI is all knowing/all seeing ... it sort of negates the need for anything else to be in the network at all. So meanwhile ... I wasn't even planning on doing an update again, but since now ED have stated that the airbaseID issues are internally fixed, it looks like I will be forced into having to update the missions once more after this has been done. Therefore I am considering taking the SAM sites out of the red detection network purely for performance saving reasons, and perhaps only leave the EWR and Ships as part of the network but I am not 100% sure what I will do yet. When starting over it is always going to be best to start with eliminating SAM sites. In the future I want to re-write some things so that missions are semi-prioritised based on a category, or possibly prioritised by sector ... but haven't had time to even think about that properly yet. Let's just say that COVID-19 has entirely screwed up any semblance of a 'plan' for now.

If your mission starts in the day, and transitions into night, the runway lights do not come on. Using the radio to tell ATC you are inbound has no effect. However If you start your mission at night, the runway lights are all on correctly from the start.

Use fixed sights and get a feel for the range that both the 23mm and 37mm guns shell trajectory comes into play. Also keep in mind the 37mm shell is a lower velocity so it requires more time to arrive on target. Pick your shots as you don't have very much ammunition to play with.