Surrexen

v122 is up Changelog v122 1. Has been increased to 130 missions 2. Has been given a radio option to smoke the current objective, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 3. Persistency script changed to not explode statics, just cleanly remove them 4. An Anti-Shipping strike has been added to Sector Seerik via radio to go along with one of the new missions

v116 is up Changelog v116 1. Has been increased to 125 missions 2. Has been given a radio option to smoke the current objective, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 3. Persistency script changed to not explode statics, just cleanly remove them 4. Targets at the Gudauta airfield relocated just North of the airfield perimeter to try to avoid blowing up the runway by accident and screwing up the AI. Because of this the Tu-160 has been swapped for an Mi-24V Helicopter. The group name has been left the same so progress will not be affected. 5. The Black Sea Fleet has had the cruiser swapped over to the Moskva instead of whatever the other one was as it was the Moskva that resides in the Black Sea and I care about details like that. 6. EWR radar at Sukhumi airfield has been relocated just outside the airfield perimeter for the same reason as the targets at Gudauta airfield have been moved 7. A Pinpoint Strike has been added to Sector Zugdidi via radio to go along with some of the new missions

v104 is up Changelog v104: - Radio option to smoke the current objective added, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown - Persistency script changed to not explode statics, just cleanly remove them

v109 is up Changelog v109: Operation Secret Squirrel and Jupiter 1. Radio option for blue coalition to smoke the current objective has been added, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 2. Persistency script changed to not explode statics, just cleanly remove them 3. Blue coalition default skins made more consistent (full invasion stripes) 4. B-17 missions now also spawn a flight of Axis planes that will be vectored to intercept them roughly West of Le Havre on their flight paths. 4. Various script fixes and improvements 5. Carpiquet airfield and all North-Western French airfields set to blue coalition to hopefully stop red coalition planes attempting to land at Carpiquet airfield etc when damaged

v106 up Changelog v106 Operation Secret Squirrel and Jupiter 1. Radio option to smoke the current objective added, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown. There is a seperate cooldown for each coalition, and the smoke colour is different for each coalition (red coalition mark with blue smoke, blue coalition mark with red). 2. Persistency script changed to not explode statics, just cleanly remove them 3. Briefings for Secret Squirrel Blue Coalition Enguri Dam Flak Battery targets have been corrected 4. Various script fixes and improvements

Just figured I'd drop a note to say where things are at as I'm working on a bunch of things at once. Operation Snowfox 1. Has been increased to 130 missions 2. Has been given a radio option to smoke the current objective, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 3. Persistency script changed to not explode statics, just cleanly remove them 4. An Anti-Shipping strike has been added to Sector Seerik via radio to go along with one of the new missions Operation Clear Field 1. Has been increased to 125 missions 2. Has been given a radio option to smoke the current objective, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 3. Persistency script changed to not explode statics, just cleanly remove them 4. Targets at the Gudauta airfield relocated just North of the airfield perimeter to try to avoid blowing up the runway by accident and screwing up the AI. Because of this the Tu-160 has been swapped for an Mi-24V Helicopter. The group name has been left the same so progress will not be affected. 5. The Black Sea Fleet has had the cruiser swapped over to the Moskva instead of whatever the other one was as it was the Moskva that resides in the Black Sea and I care about details like that. 6. EWR radar at Sukhumi airfield has been relocated just outside the airfield perimeter for the same reason as the targets at Gudauta airfield have been moved 7. A Pinpoint Strike has been added to Sector Zugdidi via radio to go along with some of the new missions Operation Black Spire 1. Has been given a radio option to smoke the current objective, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 2. Persistency script changed to not explode statics, just cleanly remove them 3. I think I will relocate the targets from Sector Caliente Charlie and remove that sector from the board, as I don't really like how that plays out, all the others seem fine Operation Secret Squirrel and Jupiter 1. Have been given a radio option to smoke the current objective, to avoid the potential for smoke spamming on skip mission etc, the smoke is on a 5 minute cooldown 2. Persistency script changed to not explode statics, just cleanly remove them 3. Briefings for Secret Squirrel Blue Coalition Enguri Dam Flak Battery targets have been corrected 4. Various script fixes and improvements I will hopefully have all this stuff ready to push out the door before next weekend

Pre-ordered :)

I have tested Zugdidi and Gudauta sectors with CAP and SEAD flights and everything is working as it is supposed to for me. Are you spawning the flights and then trying to click all the push commands from the menu at the same time? For each push command that you issue you would be best to go out of the menu and back in before giving the next push command as the script needs a second or two to re-organise the menu after each push is clicked (it has to issue the command then remove the option from the menu). That's the only thing I can think of that might be giving it problems. Try calling for just one support flight and tell it to push and let me know what happens.

That's the spirit! I can also highly recommend a good sized dosage of BRRRRRRRRT :thumbup:

This made me spit my coffee all over the place when I read it :lol: First of all, there are 4 of them in total, 2 on the Hoover Dam wall, and 2 on the bridge looking over towards the dam. Just pop a few flares as you are on your attack run, and/or when you see them launch on you. Or call in CAS on the Hoover Dam and they'll do it for you. However ... if you absolutely must ... yes you can add in a random tank to deal with them ;) For maximum fun, don't attack them at all, and fly in between the bridge and the dam wall and dodge all the rockets using flares :thumbup:

There is some scripting that has to do with the Stennis, it will remain to be seen if the scripting works with the new carrier or not.

Strange, I honestly would have thought more people would be into the carrier module :noexpression: Fair enough, I suppose I will leave it as default then. Meanwhile, I will add some Scud launchers in, and a couple of warships to blow up in the Eastern side for good measure. That will bring the total up to 130 missions.

They orbit at the spawn point until you radio them to push.

Sorry I have just got back from a holiday where I wasn't really able to respond to this. Be advised AI flights heading to the Western sectors will fly due West for a significant amount of the flight before turning North to attack, this is to avoid crossing the border until the absolute last second that they can to avoid being intercepted for as long as possible. Which sector had you called them too and I will double check regardless.

The current big question for everyone is this ... who is planning on getting the Supercarrier module, and who is not ... I originally intended to replace the Stennis fleet with a Supercarrier fleet when the time comes ... but I am aware this would not be ideal for some people. Also didn't really want to have to put 2 fleets in the same mission, nor do I want to have 2 seperate versions of Snowfox (and Clear Field) where one version is Supercarrier and the other version is not.

Sorry this is not going to happen as that would require a major re-write of the code, and mission design/layout. I have said previously that airfield capture was not something I was planning on doing.

Yeah you can blow things up whether they are the current mission or not. The script will figure out that the group or building has been destroyed already when it tries to select that mission, and will just mark it as completed already and go select another one.

So it turn's out I 'can' just remove the static objects without having to explode them. This would mean we don't cause collateral damage after all, but we won't have the dead looking object on the ground with the smoke, which is of course good fun. So like everything else I've had to build into this thing, it's a compromise. The other option would be to do something similar to what you suggested, but perhaps get a bit more scientific about it and pull the life values out of the objects and try to calculate how many smaller explosions it would take to blow up a given thing and do it that way (so we aren't guessing how much to blast it by). Or another method is just remove the static object without exploding it, and put the smoke down where it was without having the damaged building left behind. That may look a little strange though. I'm leaning towards option 1 as it's quick, clean and will stop the problem of blowing things up unnecessarily around statics and not suck up resources by not putting smoke everywhere. Let me know what you would prefer. for i = 1, StaticIntermentTableLength do local SnowfoxStatic = STATIC:FindByName(SnowfoxStaticInterment[i]) local coord = SnowfoxStatic:GetCoordinate() coord:Explosion(1500) --works for Workshop size statics, may hit other things, not exact science :/ coord:Explosion(1700) --added by Super Wabbit to destroy missile bunkers coord:BigSmokeMedium(0.25) SEFDeletedStaticCount = SEFDeletedStaticCount + 1 end would just end up being for i = 1, StaticIntermentTableLength do StaticObject.getByName(SnowfoxStaticInterment[i]):destroy() SEFDeletedStaticCount = SEFDeletedStaticCount + 1 end for example.

The 'not exact science' comment is from Pikey as the basis for this was from his simple group saving script. Statics are basically evil. That's the short version. The outpost bug was being caused by a problem in the mission status watcher script thing, were looking for the object could potentially return nil ... it was the same bug that was in in the validation routine that checks if a target is dead or not before assigning it as a mission or not. And yes, the biggest problem with having to explode the statics is the blast kills things near it. This is collateral damage, and the price we pay for persistent statics lol. I'm about to go on holiday with the family, when I get back from that I'll see If I can work something out for this. Thanks for letting me know, tis' a good catch :thumbup:

Just fired it up again to host it normally, target report is fine for me. If you see it fail again can you use check current objective and tell me which target you are looking at? I've tried skip a few times to get different types of targets and I can get the report for all of them so far. When you ran into this issue were you the host?

That's very strange ... the only time I know of where target report will have an issue is when the target is a group of ships and you destroy one of the ships, but it is still in the process of 'sinking'. During that time it is unable to determine how many units are alive in the group, so the function doesn't run. Once the ship sinks it will work again as normal. I haven't ever seen the persistency files break like that, doesn't sound like something I can do anything about. Edit: Just jumped into dedicated server and the target report is working fine.

Easiest would be to do a copy and paste from the Huey or Mi-8 instead, and change the new flight to Gazelle's. :thumbup: I don't own the Gazelle hence never remember to put it in :music_whistling:

v121 is up Changelog v121 - Critical fix in mission target status script - LHA-1 Tarawa added, Tacan 75X Radio Freq: 128.000Mhz AM - 2x Harrier's added to Tarawa doing runway starts from positions 3 and 4 on the runway, be careful in multiplayer not to run over each other as I can't set these planes to start on a ramp - F-14B Loadouts changed to 4x AIM-54A Mk60 2x Sparrow 2x Sidewinder instead of 6x AIM-54A Mk60 - Bukha oil field positions corrected - Sid and Sic oil fields added Edit: There were a few other things I was going to add in but the emergence of the script bug forced an update. Fixing the script and getting the update out obviously took priority.

v115 is up Changelog v115 - Critical fix in mission target status script - Naming conventions updated to new format - F-14B loadouts changed to 4x AIM-54A Mk60 2x Sparrow 2x Sidewinder instead of 6x AIM-54A Mk60

v103 is up Changelog v103 - Critical fix in mission target status script