Surrexen

If there are no files are present when the mission starts, then by default it will be 5 minutes after mission start when they are created. It then updates those files every 5 minutes by default. I assume there are still some units that are not creating dead events (like the speedboats), although I have not checked in the latest beta.

No that's not how it works. If you are not going to do it via script, you set up the trigger in the mission editor, and select the sound that the trigger will play and it will embed the sound file into the mission when you save it. I'll post some screenshots of how it will look in the editor shortly. In the example above, a trigger of 'once' type is used to play the sound file 10 seconds after the start of the mission. When you select the sound file and then save the mission, the sound file will be embedded into the .miz. The trigger will not require any further change as it will know that the file is part of the mission. Hopefully that explains it a bit better.

When you select a sound file to open from the mission editor, it will package that sound file into the .miz for you when you save the mission. You don't need to then tell it where to look internally from the .miz Alternatively, if you are packaging the sound files into the .miz manually outside of the editor, then you will want to trigger the sounds via script. trigger.action.outSound('SoundName.ogg')

From what I can see, speedboats are not triggering an on death event when they die. I am not sure whether there are any other objects that are also not triggering on death events when killed. The in game event log no longer shows 'dead' as an event type (not sure how long that has been the case as I don't play much, and not sure if it's intentional or a bug). I have briefly tested swapping over to make use of on event kill to do the logging, but have already run into cases where objects can die without a 'killer', so then you get objects that die that don't get logged at all, which is of course not very useful. This isn't the first time that things have gone sideways after an update. The amount of times I have had to recode things Is bordering on ridiculous. I'm honestly not sure what the best approach is now ... I'm strongly considering removing all persistence from the missions. Suggestions welcome.

After todays update it appears statics are being recorded properly in the persistence files (I haven't tested every type yet). Please start new persistence files and let me know if you run into issues with any particular type of static object. Edit: Speedboats don't record at all still, it seems they don't trigger an on death event when they die?

It would affect all of them.

Yes, as previously stated, there is a bug. Can't do anything about it. Hopefully fixed in next patch?

No there isn't a light version, I tried to keep the unit count reasonable for the map size ... I was holding back as it was May isn't that far away really! I am currently working on a new concept which I will build something for on the Normandy 2.0 map if the concept comes together properly (so far so good). It will be completely different to how I've done things before.

Ah fair deal, thanks Grimes.

No version numbers sorry, not for a long time. Again,this isn't something I can test, as I don't have voice attack/viacom etc. I'm afraid you are on your own on this one.

Does anyone know how to get the zone type values and vertices data from a quad point zone placed in the ME during runtime via script? For example I have: local Sector = trigger.misc.getZone(RED_SectorList[i]) local SectorVec3 = Sector.point local SectorRadius = Sector.radius It looks like a quad point zone has a 'type' of 2 and a table of vertices, but if I try Sector.type I get a nil return. Can't seem to find anything about it anywhere.

I've just had a quick look and yes there is definitely something wrong with it. Will investigate, thanks for letting me know. Edit: Looks like there are some known bugs going on in the scripting engine to do with static objects, so have to wait until that's fixed.

I have been away for a few days and have barely even looked at MT etc. Sounds like something changed, I'll check it out during the week.

I'm afraid I've got no idea why something like this would happen, I don't have voice attack etc so I can't even test it. That said, the generals script is basically identical between my missions so it seems rather strange that one would not work and all the others are ok. Have you looked at the log files to see what's going on? Maybe it will spit out a particular error about it. I have no heard of this issue from anyone else as yet.

Indeed. The real question is do you want to become a heretical charlatan like the rest of us or not.

You will probably need to explain a bit more about exactly what you want to do, as in exactly what you want in the mission to be persistent. That said, the place to start would be Pikey's Simple Group Saving script, which will keep a record of everything that is alive in the mission. When using this, the script will remove all units from the map at mission start and replace everything as per what was recorded as alive, including coordinates and facings etc. This method is best if you are planning to use dynamically spawned ground units. Alternatively you can look at what I did in Operation Snowfox. It is basically Pikey's script in reverse, it will only record units that were killed, and remove dead units from the mission at mission start. This method is only for when you are going to hand place everything in the editor and not use dynamic spawns for ground units. Either method will require you to modify MissionScripting.lua to allow the saving of lua files (which will contain the list of alive/dead units etc). It's hard to answer further without knowing exactly what you are intending to do. There are lots of ways to skin this cat, so to speak.

It's a fairly 'heavy' mission in terms of objects etc, so VR will likely be rough unless you can run it on a dedicated server or something like that to take the load off your machine. I have a G2 but don't use VR for DCS simply because the performance isn't there for me (unless I do NTTR map or something ... then it's 'ok' but not great). I do other stuff in VR no problem. Perhaps the Through the Inferno series would be better for you in VR as that is more tuned for that sort of thing. There is not a filter for selecting closer targets at present. You can use the radio menu to 'skip mission' and it will randomly pull another active target, you can keep skipping until you get one that is closer. A feature like this is something that has been requested many times, not sure if/when I'll get time to do it. Also you can use radio menu 'target report' to get exact coordinates of the target including altitude etc etc. For the mission that was in the wrong grid square, I may have typo'd it ... I'll take a look when I can and correct it for next update (probably whenever the F-15E comes out or something). Hope that helps

Operations Scarlet Dawn/Snowfox/Clear Field/Sea Slug Have been updated to include the Mirage F1EE and to fix a typo in a script for Scarlet Dawn/Snowfox that could affect the F-14A's launching from the Forrestal. Thanks to @phrogZ for reporting the problem!

I've looked it over and everything appears to be fine. Yeah originally it was simply destroy all targets, but now you can also win via capturing all necessary airfields (take and hold victory conditions).

Sounds like you met the requirements for a 'take and hold' victory as opposed to an 'annihilation' victory. That said, I'll take a look at it during the week and get back to you.

Yes, as it says on the tin, you have to edit them after any update or repair.

So long as you set it up as per the instructions, then yes absolutely it will.

You can run it singleplayer, host it locally, or run on dedicated server.

If you edit the 'generals' script and find: timer.scheduleFunction(SEF_REDGENERAL_ATTACKAIRBASE, nil, timer.getTime() + math.random(900, 1200)) timer.scheduleFunction(SEF_BLUEGENERAL_ATTACKAIRBASE, nil, timer.getTime() + math.random(900, 1200)) And remark it out so it looks like this: --timer.scheduleFunction(SEF_REDGENERAL_ATTACKAIRBASE, nil, timer.getTime() + math.random(900, 1200)) --timer.scheduleFunction(SEF_BLUEGENERAL_ATTACKAIRBASE, nil, timer.getTime() + math.random(900, 1200)) Then the entire base capture part along with bomber attacks and all those things will not run, and it will only have the red and blue cap planes.

Operation Scarlet Dawn/Snowfox/Clear Field/Sea Slug all updated to correct the issue with the crates not being able to unload from helo's (reverted back to old moose). All Ka-50's have been updated to be Ka-50 III's, and Ka-50 III's are able to use the helo ops menu. Spirit of Maradona be with you.