TEMPEST.114

Thanks so much for the info.

So is there any way around this? Any work around? Anything in scripting?

Here is a mission with a 3000ft radius, yet every one of the 16 cruise missiles hits the same spot on the ground. Whatever 'random' position generator within the radius function you're using is not working at all. This means it's impossible to shell a large area with cruise missiles as they will only ever hit the same pin point position. Ticon.miz

None for red either? Cool. Thanks so much. just a follow on, are scuds ‘cruise missiles’ or something else?

I must admit I don't really know military tech other than the aircraft, but I've been asked to build a mission that uses 'Cruise Missiles' or their equivalent from both BLUE and RED. But other than the TICONDEROGA I have no idea what units can do this - or what 'weapon name/type' are 'cruise missiles' or their equivalents. Thanks

Okay, I just thought this was a place to register bugs and have them addressed...

Okay, it's just that in say, the F18, it gives you the option to see the time in Z or L, so therefore somewhere they've done the function for that and I wanted to know if there was a way of getting that? I'll make my own lookup table for the maps.

This gives LOCAL - CORRECT? DCS func getAbsTime - DCS World Wiki - Hoggitworld.com So where in the api do I get the timezone offset to convert to Zulu? It's not in atmosphere, land or weather...

so, in 'me_mission.lua' There is this function that's loading them and putting them into a table: function fixBriefingPictures() mission.pictureFileNameR = mission.pictureFileNameR or {}; if 'string' == base.type(mission.pictureFileNameR) then local name = mission.pictureFileNameR; mission.pictureFileNameR = {}; if name ~= '' then table.insert(mission.pictureFileNameR, name); end; end; mission.pictureFileNameB = mission.pictureFileNameB or {}; if 'string' == base.type(mission.pictureFileNameB) then local name = mission.pictureFileNameB; mission.pictureFileNameB = {}; if name ~= '' then table.insert(mission.pictureFileNameB, name); end; end; if mission.version < 8 then for i = 1, #mission.pictureFileNameR do local curId = mod_dictionary.getNewResourceId("ImageBriefing") local filename = "l10n/DEFAULT/"..mission.pictureFileNameR[i] --base.print("-------curId, v, filename=",curId,mission.pictureFileNameR[i], filename) mod_dictionary.fixValueToResource(curId, mission.pictureFileNameR[i], filename) mission.pictureFileNameR[i] = curId end for i = 1, #mission.pictureFileNameB do local curId = mod_dictionary.getNewResourceId("ImageBriefing") local filename = "l10n/DEFAULT/"..mission.pictureFileNameB[i] --base.print("----d---curId, v, filename=",curId,mission.pictureFileNameB[i], filename) mod_dictionary.fixValueToResource(curId, mission.pictureFileNameB[i], filename) mission.pictureFileNameB[i] = curId end end end I think the 'bug' is here. There's still NO NEED to obfuscate / localise the image file names like this.

Easiest way to do this is via the F10 Radio Menu. Get the flight lead to make a radio call when they've confirmed the ID, which turns on a flag that you can do stuff with in other trigger conditions. AFAIK there's no way to do it automatically from a TGP. the api is very, VERY bare bones and relatively unsupported.

I don't think you understand the problem or a proper solution. Thanks for playing.

I don't care about the model - but why is it called an E-2D in the mission editor? That tiny meta data fix would have prevented this entirely. You mean someone won't edit one file and change a D to a C?!

HOW is that helpful for a SCRIPTING solution that can handle any map / time of year automatically?

I love the document you found.. I'm just not convinced that ED are doing it that way... I could get the 'real' number but DCS could be off... so it wouldn't help me. And as I need this to work from scripting, it's not something the mission designer needs to get involved in.

So you're saying go to every map and play with the daytime slider for every day/month/year for each map and make a table of it? Sheesh... It's in the backend somewhere because the Carrier will tell you if it's CASE 2 or 3 when 'official night' kicks in - I just need that function / boolean.

that doesn't tell me if it's day or night for a given location and month / day... Some places it will be night at 1600, others 1800 and then in winter/summer those could be flipped...

No response? Surely this is a significant bug?

radio enum

Of course there is - you just can't get access to it or use it. Hence, mods.

With DCS, mods are life. If you wait for ED to do it, your kids might get it. Or maybe theirs...

as title says AWACS Group Dump: { ['hiddenOnPlanner'] = false, ['tasks'] = { }, ['radioSet'] = false, ['task'] = 'AWACS', ['uncontrolled'] = false, ['taskSelected'] = true, ['route'] = { ['points'] = { [1] = { ['speed_locked'] = true, ['type'] = 'Turning Point', ['action'] = 'Turning Point', ['alt_type'] = 'BARO', ['y'] = 235748.91270383, ['x'] = -226466.34662103, ['ETA'] = 0, ['alt'] = 9400.032, ['speed'] = 169.44444444444, ['ETA_locked'] = true, ['task'] = { ['id'] = 'ComboTask', ['params'] = { ['tasks'] = { [1] = { ['enabled'] = true, ['auto'] = true, ['id'] = 'AWACS', ['number'] = 1, ['params'] = { } }, [2] = { ['number'] = 2, ['auto'] = true, ['id'] = 'WrappedAction', ['enabled'] = true, ['params'] = { ['action'] = { ['id'] = 'EPLRS', ['params'] = { ['value'] = true, ['groupId'] = 2 } } } }, [3] = { ['number'] = 3, ['auto'] = false, ['id'] = 'Orbit', ['enabled'] = true, ['params'] = { ['speedEdited'] = true, ['speed'] = 169.58333333333, ['pattern'] = 'Circle', ['altitude'] = 9400.032 } } } } }, ['formation_template'] = '' }, [2] = { ['speed_locked'] = true, ['type'] = 'Land', ['action'] = 'Landing', ['alt_type'] = 'BARO', ['linkUnit'] = 9, ['ETA'] = 878.0451111848, ['y'] = 355239.12264509, ['helipadId'] = 9, ['formation_template'] = '', ['ETA_locked'] = false, ['speed'] = 138.88888888889, ['x'] = -250839.80288154, ['task'] = { ['id'] = 'ComboTask', ['params'] = { ['tasks'] = { } } }, ['alt'] = 0 } } }, ['groupId'] = 5, ['hidden'] = true, ['units'] = { [1] = { ['alt'] = 9400.032, ['type'] = 'E-2C', ['alt_type'] = 'BARO', ['psi'] = -1.7720146047262, ['livery_id'] = 'E-2D Demo', ['onboard_num'] = '010', ['unitId'] = 29, ['y'] = 235748.91270383, ['x'] = -226466.34662103, ['name'] = 'DARKSTAR1-1', ['payload'] = { ['pylons'] = { }, ['fuel'] = '5624', ['flare'] = 60, ['chaff'] = 120, ['gun'] = 100 }, ['speed'] = 169.44444444444, ['heading'] = 1.7720146047262, ['callsign'] = { [1] = 5, [2] = 1, [3] = 1, ['name'] = 'Darkstar11' }, ['skill'] = 'Excellent' } }, ['y'] = 235748.91270383, ['x'] = -226466.34662103, ['name'] = 'AWACS', ['communication'] = true, ['start_time'] = 0, ['modulation'] = 0, ['frequency'] = 251 } NOTICE: ['type'] = 'E-2C', ['livery_id'] = 'E-2D Demo',

as title says.

American men and women and someone who can do a passable Russian 'English' voice (male or female or both). I can't do accents even with VoiceMod software, so if anyone wants to volunteer or just register as available to this thread perhaps other mission designers can contact you too for your services. For myself, this isn't a paid thing - I just need some people to record some lines for my script. Thanks

Thank you both. In both cases, there were two points directly over each other - ODD that I would have mistakenly 'double clicked' at the exact point when drawing two different lines at two different times - so I think some more investigation into this as it might still be a ME bug, but after removing the 'extra' point then the 0,0 was gone and now I understand that each is an offset from the original map x and y (not clear in the documentation ) then I can now use them. Thanks.

There are also apps like VoiceMod to disguse your own voice such that they sound fully human but NOTHING like you. When you really need something with more 'energy' or 'voice acting' than straight TTS then 'VoiceMod works brilliantly. That being said, ED should put TTS inside the API for scripters / mission editor designers to use, which supports n number of voices (included in the miz file)