Surrexen

Attached track showing a Mission Start trigger with a message and a Once trigger with a message. Only the once trigger message will show up. Mission Start Trigger Test.trk

Please be aware that the 2.5.6 update has broken a lot of things with my missions. I suspect at this stage I will be waiting for ED to patch things before I can even attempt to try to solve what is going on.

Is StaticObject.getByName() working for anyone else properly if it is being run from a Mission Start type trigger event (like in a script fired from Mission Start).

The CAP flights that you can enable will defend their zones by themselves, no further input required. The support requested planes will spawn when requested and then orbit their first waypoint and await a 'push' radio command before proceeding with their flight plans. Once they have been told to push, no further input is necessary. You can however radio any of the support requested flights and tell them to RTB under 'abort directives'.

Does this mean that any trigger action from a mission start type trigger won't work? As in trigger.action.outText would also be affected? Just trying to figure out why certain things are not behaving properly.

Yep I have it loading about 3 times longer as well ... maybe more. It's definitely a lot slower to get into the main menu.

I could not launch from the catapult either, happy enough to know you guys are aware of it. Hopefully ED will get it sorted quickly.

Does the new kill event feed into the pilot log? And does that mean it works for dynamically spawned aircraft etc?

No the target report shows 3 different formats: 1. DMS (Degrees Minutes Seconds) 2. DDM (Degrees Decimal Minutes) 3. DMSDS (Degrees Minutes Seconds Decimal Seconds) If you are programming in JDAM's / JSOWS etc you would follow the coordinates of the DMSDS format.

You shouldn't need to add the waypoints in the editor. If you go into the radio menu and ask for the target report you will get the target coordinates and altitude in 3 formats so you can plug whatever you need into the jet.

This isn't really possible as there could be multiple players attacking the same mission targets. Also would require extensive re-writes of how to deal with targets and the way they are handled with persistence. The mission is challenging enough as it is without punishing players by not counting the ground kills if they don't return to base successfully after a sortie. This is further complicated when being done in single player, where a single mission may take multiple sorties to complete. In that case, it would be even more complicated to deal with.

I am sort of waiting on some of the new assets to come out before I do anything further right now. Things like the U-Boat, the P-47, Ju-88 etc etc. Once some of the new assets are out I'll be more than likely re-working this mission. Ideally I will re-work it so both sides have missions and both sides have bombers to intercept etc but we'll have to see how it goes. Also waiting on the fancy new damage model to release.

This should probably be posted under the Hunters of the Yalu section here: https://forums.eagle.ru/forumdisplay.php?f=718

Yes :thumbup: And you definitely would want the newest version available as it has all the major script fixes in place.

Not really as the most Western part of the map is low detail and there are no airfields. Otherwise I would have made the whole thing over Kuwait. I have been considering doing a "Phase 2" type operation in the Northern part of the map though. I won't be doing anything for a while though. Most likely the next thing will be working on Operation Jupiter more when more WWII assets get released.

I had made the decision very early on that I didn't want to run both MIST and MOOSE in the same mission, and decided to go with MOOSE because of the AI A2A Dispatcher methods for the way it can handle the randomisation of the squadron makeups and respawns. I never really looked into MIST because of that. The other big one is how sets of groups and units is really easy to do with MOOSE, this was pretty much what allowed me to implement persistence into the mission. The downside to both MIST and MOOSE is that dynamically spawned planes do not get counted towards the pilots logbook. If ED did have a respawn function that allowed the spawned planes to count towards logbook then yes, perhaps given the time, I would find a way to drop MOOSE entirely since I don't really use that many of it's functions. Also I am sort of stuck now with a slightly customised version of an older Moose version from August last year as I don't really like how the planes behave in versions newer than that, this is not a complaint about Moose, just a personal preference on how they behave. Of course, re-writing everything would be a major rework, and is not something that is realistically going to happen. As it stands right now, I have spent a massive amount of time and effort to get my missions working to the level that they are now. I think I have finally ironed out all the major bugs in my scripts and the current versions of my code are stable enough that I effectively call it done (at least for now). Also I know that there are several servers/groups out there that have taken what I have done and added MIST to it to provide things like CTLD etc to their liking. I can't really make Snowfox or Clear Field any bigger than they are now anyway as I kind of feel they are at their limits for what the engine can provide me. Perhaps when Vulkan gets added some of those limitations might be alleviated ... but who really knows. Anyway, I figure with what I have now, I can at least whack together the same system into any further maps that get released without too much hassle. I am looking forward to putting something together for the Mariana's map ... and when the time comes ... Syria. I am not sure at this stage whether I will make one for the upcoming channel map or not. Long story short, anything you want to do in terms of mission design, and scripting, ends up being a compromise based on limitations you run into along the way. You guys have only really seen the bits that I have tried out and decided are 'ok'. What you haven't seen is the countless ideas on the drawing board that only got so far before something didn't work out quite right and the idea would have to be scrapped. Anyway, with 3000+ combined downloads on my missions I must have gotten at least something right :thumbup:

The Tarawa fleet has it's own missile defence zone already. The zone is pretty tight though :smilewink:

Absolutely no idea, but I have a feeling that the minimum time doesn't work properly, only the maximum time seems to be reliable. To be honest if ED had a respawn function, I would be seriously considering dropping Moose altogether and re-write everything to function without it.

You could just do skip mission until you pull one of the SAM sites and then use the radio menu target report to get given the target coordinates and altitude.

Super Wabbit's Tip 6 ... totally this. Only press the attack when the time is right. Timing is everything.

Assuming that you have persistence up and running, then patience is the key. At the very beginning when all the SAM sites are up, it is very hard to break them down. You need to keep chipping away until you eliminate them. Remember each time you blow up a ground unit, you have made progress. And most importantly, use the support requests!

Please tell me that the Mosquito is going to come with an AI Lancaster to go with it.

It seems the first client slot you jump into in a mission the threat circles will show properly on the HSD, if you then change slots to another member of the flight, or a different flight, the threat circles don't show up.

Yes there are 4 new missions where Scud Launchers are the targets :thumbup:

You should be able to continue on :thumbup: