Puddlemonkey

We are able to transmit radio messages and by the looks of it, with the next patch release, we will be able to customise the F10 menu in multiplayer so can allow players to instigate radio conversations and make responses. Is there a method, trigger or whatever to capture when a radio message is actually received? Otherwise, how do we tell whether a radio message was actually received by someone with their radio correctly tuned? Thanks PM

You can try ivona.com to make speech and Sony Sound Forge to emulate the affect of the radio. The following has good results: 1. Normalise RMS to -6dB 2. Distortion effect, transistor 1 3. Reverb plate with a decay time of 0.5s 4. Parametric Equaliser with 2KHz x 0.7 octave, amount = -60dB and output gain adjusted to give you -3dB peak 5. Normalise RMS to -3dB 6. Set volume to -3dB

Seems like it. I can't get it to work either. It really ought to and being able to customise the R-828 frequencies would do a lot for integrating the KA-50 with the other aircraft. This is especially true if the functionality to add menu items to the radio menu worked in multi-player. Failing that, could ED at least issue a standard R_828.lua with all 10 frequencies specified so I don't have to keep replacing it every time a new version is released?

Are the custom menus working in multiplayer now? I recall there were issues. If so, is it possible to identify who selected an option from the menu?

try this thread http://forums.eagle.ru/showthread.php?t=81309

Hi, I tried this and it didn't work. Could someone post a .miz with it working please so I can work out where I went wrong? Thanks PM

that looks like a bad idea and why would you want a country to be on both coalitions??

You can do this but you also have to edit the section where all the units reside. In your example, say you move country 19 from red to blue, you will need to: remove [3] = 19 from red and insert it to blue as [15] = 19 Then... find the mission = {, then within that the coalitions = { and within that the ["red"] = { under there, you will find the [3] = { which contains all the units belonging to that country. You will need to move this to the mission > coalitions > blue as [15]. Should work - I've done this several times now without issues. It's just a bit tricky to find the parts to move when you have lots of units. Maybe worth trying it with a very simple mission with only two units to practice.

Cheers guys, that has saved me some hassle :-)

Grimes, I''m curious what the simulation's own randomisation scripting is? I have been using random flag values to set the math.randomseed. Are you saying that the DCS lua environment already randomises it and nothing is necessary? Thanks

+another one

by default, scripts can't access the OS. You can desanitize the lua environment by commenting out lines of some DCS lua files but it isn't recommended that you do it, unless it is for your own testing. What is this supposed to achieve? Maybe you can do it another way? Maybe if you post the mission, someone will sort it for you :-)

Yes. You can add a triggered action to "Perform Command", "Transmit Message". You can type a subtitle. Or you can do it with LUA: local tabCommand = { id = "TransmitMessage", params = { subtitle = "Some text", duration = 3, loop = false, file = "sound.wav", } } local objGroup = Group.getByName("group 1"):getController() Controller.setCommand(objGroup, tabCommand) If using LUA, you need to inject the wav file into the .miz.

@Teapot. The hats are 8-way but there isn't a separate command for the diagonals. This is a result of the driver or the electronics, I think the driver. It is not a DCS limitation. @Pigwiggen. Do you see the movement of your X52 throttle when you are in the settings screen, adjusting the axis for the collective?

Not sure if this helps but I use: {combos = {{key = "JOY_BTN18"}, }, down = 3009, up = 3009, cockpit_device_id = 4, value_down = 0, value_up = 1, name = "Cut-off valve left engine on", category = "Ins Engines start-up control panel and levers"}, This works for me, using a toggle switch. However, there is one drawback and that is that the position the switch needs to be in is different, depending on whether it is a hot or cold start in the mission.

Sorry, yes, I meant to say collective, not throttle.

It is simply a case of selecting the right axis in the options. You may choose to invert the axis so it is more like a heli collective. Options > Controls. Select the drop-down and change from All to Axis Commands. Select the throttle line, under the column for the X52 Throttle. Then press axis assign to choose the correct axis and axis tune to select the invert option.

me too

Does this help? Anapa runway_homer_pair(Airdrome[Anapa], nil, localizedAirdromeName(terrainAirdromes[Anapa])) Batumi "{ [ADF_HOMER_NEAR] = airdrome_homer(Airdrome[batumi], Airdrome[batumi][""airdrome""][1], localizedAirdromeName(terrainAirdromes[batumi])) }" Belbek runway_homer_pair(Airdrome[belbek], nil, "Belbek") Beslan runway_homer_pair(Airdrome[beslan], nil, localizedAirdromeName(terrainAirdromes[beslan])) Dzhankoy runway_homer_pair(Airdrome[Dzhankoy], nil, "Dzhankoy") Gelendzhik "{ [ADF_HOMER_NEAR] = airdrome_homer(Airdrome[Gelendzhik], Airdrome[Kutaisi][""airdrome""][1], localizedAirdromeName(terrainAirdromes[Gelendzhik])) }" Gudauta "{ [ADF_HOMER_NEAR] = runway_homer(Airdrome[Gudauta], nil, BEACON_TYPE_AIRPORT_HOMER_WITH_MARKER, localizedAirdromeName(terrainAirdromes[Gudauta])) }" Gvardeyskoe runway_homer_pair(Airdrome[Gvardeyskoe], nil, "Gvardeyskoe") Kerch runway_homer_pair(Airdrome[Kerch], nil, "Kerch") Khersones "{ [ADF_HOMER_NEAR] = airdrome_homer(Airdrome[Khersones], Airdrome[Khersones][""airdrome""][1], ""Khersones"") }" Kirovskoe "{ [ADF_HOMER_FAR] = runway_homer(Airdrome[Kirovskoe], nil, BEACON_TYPE_ILS_FAR_HOMER, ""Kirovskoe""), [ADF_HOMER_NEAR] = runway_homer(Airdrome[Kirovskoe], nil, BEACON_TYPE_RSBN, ""Kirovskoe"") }" Kobuleti runway_homer_pair(Airdrome[Kobuleti], nil, localizedAirdromeName(terrainAirdromes[Kobuleti])) Krasnodar runway_homer_pair(Airdrome[Krasnodar], nil, localizedAirdromeName(terrainAirdromes[Krasnodar])) Krasnodar_P runway_homer_pair(Airdrome[Krasnodar_P], nil, localizedAirdromeName(terrainAirdromes[Krasnodar_P])) Krasnogvardeyskoye runway_homer_pair(Airdrome[Krasnogvardeyskoye], nil, "Krasnogvardeyskoye") Krymsk runway_homer_pair(Airdrome[Krymsk], nil, localizedAirdromeName(terrainAirdromes[Krymsk])) Kutaisi "{ [ADF_HOMER_FAR] = runway_homer(Airdrome[Kutaisi], nil, BEACON_TYPE_ILS_FAR_HOMER, localizedAirdromeName(terrainAirdromes[Kutaisi])), [ADF_HOMER_NEAR] = airdrome_homer(Airdrome[Kutaisi], Airdrome[Kutaisi][""airdrome""][1], localizedAirdromeName(terrainAirdromes[Kutaisi])) }" Lochini runway_homer_pair(Airdrome[Lochini], nil, localizedAirdromeName(terrainAirdromes[Lochini])) Maykop runway_homer_pair(Airdrome[Maykop], nil, localizedAirdromeName(terrainAirdromes[Maykop])) MinVody runway_homer_pair(Airdrome[MinVody], nil, localizedAirdromeName(terrainAirdromes[MinVody])) Mozdok runway_homer_pair(Airdrome[Mozdok], nil, localizedAirdromeName(terrainAirdromes[Mozdok])) Nalchick runway_homer_pair(Airdrome[Nalchick], nil, localizedAirdromeName(terrainAirdromes[Nalchick])) Novorossiysk nil --[[no beacons--]] Octyabrskoe runway_homer_pair(Airdrome[Octyabrskoe], nil, "Octyabrskoe") Razdolnoe runway_homer_pair(Airdrome[Razdolnoe], nil, "Razdolnoe") Saki runway_homer_pair(Airdrome[saki], nil, "Saki") Simpheropol 01L/19R runway_homer_pair(Airdrome[simpheropol], "01L/19R", "Simph 01L/19R") Simpheropol 01R/19L runway_homer_pair(Airdrome[simpheropol], "01R/19L", "Simph 01R/19L") Sochi "{ [ADF_HOMER_NEAR] = runway_homer(Airdrome[sochi], nil, BEACON_TYPE_AIRPORT_HOMER_WITH_MARKER, localizedAirdromeName(terrainAirdromes[sochi])) }" Sukhumi runway_homer_pair(Airdrome[sukhumi], nil, localizedAirdromeName(terrainAirdromes[sukhumi])) TbilisiMilitary nil --[[no beacons--]] Tskhakaya runway_homer_pair(Airdrome[Tskhakaya], nil, localizedAirdromeName(terrainAirdromes[Tskhakaya])) Vaziani "{ [ADF_HOMER_NEAR] = airdrome_homer(Airdrome[Vaziani], Airdrome[Vaziani][""airdrome""][1], localizedAirdromeName(terrainAirdromes[Vaziani])) }"

I use this spreadsheet to create my ark.lua. ARK ADF Configuration Tool.zip

Ok, that proved a tricky one. The lua ipairs iterator stops if there is a gap in the list (you didn't have a weapon on the 6th pylon so it would ignore 7 to 11. Should be fixed now. Also, when I run your 'BeforeScript.miz', it rams the ground too.

Yeah, just looking at that now....

I think the reason why the filesize is smaller is that I have used the tab character to indent rather than several spaces. Once compressed, I doubt it makes any difference. Glad its working for you :-)

Strange. I did of course test it. The first time, I didn't have planes in my missions so hadn't spotted the issue that you did. However, I tested it with your previous mission inserted into a .miz and have just run it on your @MissionEditorTesting.miz. It renames the units, I can save in Mission Editor and I can even fly it (before and after the script). So I'm stumped. Looking at your log, it looks like it can't open the zip file. I wonder about the filename or what you're using to extract and insert from the .miz zips. As I say though, it's all working for me, even with your files. This is the miz after I have run the script and inserted the new mission into the zip. :noexpression: @MissionEditorTesting.miz

Hi, I took a look at this and it turns out that mission files have some tables which are a combination of numbered (array) and labelled key elements. I have modified the script to deal with this. Hope it works, give it a try and let me know. PM