Surrexen

v118 is out to remove the clearview on the target report.

v106 is out to remove the clearview on the target report.

v111 is out to remove the clearview on the target report.

v108 is out to remove the clearview on the target report.

v123 is up Changelog v123 IMPORTANT: If you are using persistence, you MUST remove your SnowfoxUnitInterment.lua and SnowfoxStaticInterment.lua files from your DCS World installation folder before starting the mission so new lists can be generated as many group and unit prefixes have changed!!! 1. A 2.5.6 compatible Moose version has been added 2. Group/Unit/Static prefixes for certain sectors have been revised so that pinpoint strikes will work on all targets in a sector 3. Infantry units have been set to not disperse under fire so they don't go hiding in trees etc 4. Target report clearview added to the text output to help alleviate the issue in the note below. 5. Various script adjustments 6. Carrier Defenze Zone code disabled due to SM-2 issue being an intentional ED change 7. An extra set of helo's have been put in at Sharjah Intl 8. Patriot system with 3 launchers has been added to Al Minhad 9. Other stuff that I can't remember right now Note: For busy multiplayer servers, an issue has been identified where the target report can take up a lot of space in VR (for example when a flight of 4 is full of players and the report is given to the whole group). To get around this issue, it may be best to change the client slot groups to single planes only and duplicate the single planes so that instead of one group of 4 planes, you have 4 groups of 1 plane each. This way the target report will only come out once per player and not take up their whole screen. Extra note: While I have tested all the tacan channels in single and multiplayer, it seems that at random people have issues with either the carrier tacan going missing, or the refuelling tankers tacan's going missing. If anyone has any smart ideas on why this happens please let me know as it always works for me, then I submit the file and chaos happens from there.

v117 is up Changelog v117 IMPORTANT: If you are using persistence, you MUST remove your ClearFieldUnitInterment.lua and ClearFieldStaticInterment.lua files from your DCS World installation folder before starting the mission so new lists can be generated as many group and unit prefixes have changed!!! 1. A 2.5.6 compatible Moose version has been added 2. Group/Unit/Static prefixes for certain sectors have been revised so that pinpoint strikes will work on all targets in a sector 3. Infantry units have been set to not disperse under fire so they don't go hiding in trees etc 4. Target report clearview added to the text output to help alleviate the issue in the note below. 5. Various script adjustments 6. Carrier Defenze Zone code disabled due to SM-2 issue being an intentional ED change 7. An extra set of helo's have been put in at Tbilisi-Lochini and are Georgian 8. Poti SA-3 system has now been made operational because I'm a donkey and forgot to add the P-19 radar or whatever it is to it all this time. 9. SA-3 system added near Tbilisi 10. SA-11 system added to Senaki-Kolkhi 11. SA-2 systems have been added around Nalchik and Beslan 12. Other stuff that nobody will care about 13. Time of day set to sunrise again to get the pretty new lighting effects 14. Other stuff that I can't remember Note: For busy multiplayer servers, an issue has been identified where the target report can take up a lot of space in VR (for example when a flight of 4 is full of players and the report is given to the whole group). To get around this issue, it may be best to change the client slot groups to single planes only and duplicate the single planes so that instead of one group of 4 planes, you have 4 groups of 1 plane each. This way the target report will only come out once per player and not take up their whole screen.

v105 is up IMPORTANT: If you are using persistence, you MUST remove your BlackSpireUnitInterment.lua and BlackSpireStaticInterment.lua files from your DCS World installation folder before starting the mission so new lists can be generated as many group and unit prefixes have changed!!! You will only need to do this once! Changelog v105 1. A 2.5.6 compatible Moose version has been added 2. Group/Unit/Static prefixes for certain sectors have been revised so that pinpoint strikes will work on all targets in a sector 3. Infantry units have been set to not disperse under fire so they don't go hiding in trees etc 4. Target report clearview added to the text output to help alleviate the issue in the note below. 5. Various script adjustments Note: For busy multiplayer servers, an issue has been identified where the target report can take up a lot of space in VR (for example when a flight of 4 is full of players and the report is given to the whole group). To get around this issue, it may be best to change the client slot groups to single planes only and duplicate the single planes so that instead of one group of 4 planes, you have 4 groups of 1 plane each. This way the target report will only come out once per player and not take up their whole screen. Extra Note: Turns out the NTTR airfield ID's are kind of messed up with Moose still, so if you use ground AI starts ... interesting things will happen like red air taking off from North Las Vegas instead of Pahute Mesa. So basically leave it in GameMode 0 for air starts until I can get an updated Moose etc etc. Updates for Operation Snowfox and Operation Clear Field will likely be out tomorrow.

v110 is up IMPORTANT: It is highly recommended to start new progress files for this update, therefore remove your JupiterUnitInterment.lua and JupiterStaticInterment.lua files from your DCS World installation folder before starting the mission. Changelog v110 1. A 2.5.6 compatible Moose version has been added 2. Parking slots corrected after 2.5.6 update 3. Target report clearview added to the text output 4. Flak site added to Falaise

v107 is up IMPORTANT: It is highly recommended to start new progress files for this update, therefore remove your SquirrelUnitInterment.lua and SquirrelStaticInterment.lua files from your DCS World installation folder before starting the mission. Changelog v107 1. A 2.5.6 compatible Moose version has been added 2. An extra flight of F-86 client slots has been added 3. Infantry units have been set to not disperse under fire so they don't go hiding in trees etc 4. Target report clearview added to the text output

Can we can get an ROE 'attack planes only' option added then?

Well the things that didn't spawn are actually spawning now, so it'll probably be ok ... but definately don't use ground starts for AI ...

As in the stuff to enable the persistence? No unfortunately there is no other way than to make the edit to the MissionScripting.lua file after each update or repair. I'll pull you up here before you make any changes because I will be putting out an update but it's not fully tested yet and there are major changes. See the Snowfox thread for details on where things are up to. Editing client slots should not break anything.

So here is the deal at the moment. I have updated all 5 missions and from my side of the fence, everything appears to be working with the exception of the Carrier Defence zones due to the SM-2 missiles no longer tracking their target when the ships get set back to ROE weapons hold, the missiles either detonate or fly into the water. Will have to wait on ED for a fix (hopefully) for that one. Edit: NineLine has confirmed with the team that the SM-2 issue is an intentional change, so I will have to now disable that code :( I was hoping to upload the updated missions today, but it appears there are still several issues that ED need to work through before I can really do that and know that everything is 100% fine in 2.5.6. I will therefore, hold off on submitting the updated missions and continue testing everything over the weekend etc until a further patch comes out. Now for the bad news. Operation Snowfox, Clear Field, and Black Spire have had to have some significant unit/group renaming as I found an issue that was causing Pinpoint Strikes to not always find their target due to mismatched prefixes. Therefore, when I do release the updated missions, your progress files (SnowfoxUnitInterment.lua and SnowfoxStaticInterment.lua etc) will need to be removed so that those missions can generate new ones. If you don't, then the mission will spit out a list of the units and statics that it cannot find from the saved list and skip trying to remove that particular object from the map. If you are feeling really adventurous you could run it and get the list of units etc that it errors on and then make the necessary edits to those files, but I'm not even going to get into that here. It'll just be easier to start from scratch. I apologise in advance for that one. Operation Jupiter and Operation Secret Squirrel should run fine with the existing progress files. The good news is, the Pinpoint Strike missions should now work for every single mission target. Operation Clear Field has had Pinpoint Strike AI routes added for the sectors that it didn't have previously. Further, the persistence script being a little more robust should not fall over anymore if one of the objects in the saved list doesn't spawn correctly. Anyway, that's where it is at currently.

SEAD flights firing missiles is totally reliant on ED's AI code. I point the planes and tell them to engage in a zone, the rest is out of my control. The red bombers do not have any special significance at this stage, just to have some bombers hanging around. The carrier groups SM-2's currently have issues due to a change that ED have made. The bombers do not fly inside the range of the Khasab Hawk site, or the Patriot system. No, I will not be doing separate versions of my missions, as I have spent the last 4 days working on fixes and workarounds for the 2.5.6 update for the 5 different missions I already have. I am already having nightmares of when I have more missions to update in the future (Mariana's / Channel Map / Syria). Putting missions into a logical order is something I would like to do later down the line, but that would not be a trivial task. Airfield capture is not going to happen. Wingmen are not going to happen either, I do have a couple of flights available in Operation Jupiter that have wingman, but since the wingman do not respawn when a player respawns in the client slot, it makes it of very limited use.

This still has not been addressed: 2020-02-20 23:59:57.421 ERROR_ONCE DX11BACKEND: texture 'mig-15_dif_cockpit_spec' not found. Asked from 'NGMODEL' 2020-02-20 23:59:57.421 ERROR_ONCE DX11BACKEND: texture 'pilot_mig15_helmet' not found. Asked from 'NGMODEL' 2020-02-20 23:59:58.586 ERROR_ONCE DX11BACKEND: texture 'pilot_mig15_parachute' not found. Asked from 'NGMODEL'

There are 2 lines for each of the commands for search light on, search light off, and search light stow. When I look at my command list for the Huey it is the same as Goa's screenshot. It must be a bug as there should not be 2 entries for each of those commands.

Anything that uses the Moose SpawnAtAirbase function will blow up on spawn. There is a development Moose update that resolves this issue.

Guys I am sure deadlyfishes will get an update happening (like the rest of us) once he's had a chance to go through it all. Some of it will be Moose related and some of it will be ED related so we all have to wait for ED to get some fixes out before we can do any serious mission updates. A little patience is required at this stage.

I understand that, but unfortunately swapping from weapons hold to weapons free and back again is the only way to have ships not spam missiles all over the map. If this is an intentional change then we need some new ROE rules for ships that do 'engage planes only' etc.

My log file is showing a lot of this error after fighting a MiG-21Bis: 2020-02-17 11:30:42.698 ERROR DCS: Can't find score constants for GSH_23_HE

Also be careful because it looks like some of the tasking tries to change itself, my P-51 flights tried to make themselves CAS flights instead of CAP flights while adjusting the parking spots.

I'm seeing some different behaviour for Naval Vessels, if they fire an SM-2 and then are told to weapons hold, the missile in the air now either detonates as soon as it goes to weapons hold, or it flies into the water. In 2.5.5 the missile would still track it's target and the ship would not fire any more missiles until told to go back to weapons free. Naval SM2 Test.trk

While I agree with Pikey in regards to Conditional items at Mission Start, trigger.action.outText definitely worked from a Mission Start trigger in 2.5.5 and is not a conditional item in the test I provided. It needs to be checked for other items that may have been unintentionally affected by the update.

Still investigating, but so far: - Persistence script is falling over at random depending on the statics that you have killed, because some static objects do not spawn correctly when the mission loads - Persistence script does not give the player messages about how many units etc have been removed as outText does not work currently from a Mission Start type trigger event - Moose AI A2A Dispatcher does not work for ground starts (planes explode on spawn), only air starts will work - Moose Settings menu does not appear to be switching off correctly - Sounds not firing correctly at the start of the mission - Log files throwing lots of errors that i'm still trying to figure out whats going on - Users have reported they cannot run the mission for more than about 30 minutes without it crashing (probably due to memory leaks or something along those lines). - Missiles fired from the Carrier Groups explode or fly into the water as soon as they switch back to ROE Weapons Hold Now for the one error that I found in my own code along the way - Pinpoint strikes not working for the Bandar-e-Jask sector. I have fixed this for the next update, but sadly this is going to require starting new campaign progress files, or editing the existing ones for any dead units or statics from the Bandar-e-Jask sector as I had to rename all units and statics in that sector from Bandar-e-Jask sector prefix to just "Jask" as it didn't like the hyphens in the prefix when using string.find function. The short version is it could be a while waiting on ED updates, and then possibly even Moose updates before I can sort this out.

+1 I liked the BDA 2.5.5 box more.