Chump

I have all versions of the Ka-50 as well, and was wondering the same thing. When I follow the unbind directions above and confirm, it says, "One or more parameters are invalid." I don't see anything else I need to fill out, as I'm not binding it to another account. Any advice? Am I missing something?

Apolloace, assuming that you pre-defined the groups in the editor and set them all to delayed start, as well as defined the zone: NOTE: MiST makes this stuff super easy 1) Define a list of group names. local groupNames = {"Group1", "Group2", "Group3"}2) Choose a random group name. local groupName = groupNames[mist.random(#groupNames)]3) Figure out how many seconds from now that you want it to respawn. local randomTime = timer.getTime() + mist.random(120) // up to 120 seconds in the future4) You will need to have something that checks the current time to trigger the spawn. A simple approach would be to create a new scheduled function that fires immediately and checks each second thereafter. local timerNum = mist.scheduleFunction(checkTime, {groupName, randomTime}, timer.getTime(), 1)5) Create the new function that checks the current time against the desired spawn time. function checkTime(obj) if timer.getTime() >= obj.randomTime then mist.respawnInZone(obj.groupName, "myZone") end endThis should work, although it is from memory and not verified. There is some extra code that could be written to stop the timer. Please let me know if you have issues with it.

I tried the pcnsl.exe with the same result you mention. Once I followed the Deleting product registry entries method mentioned in the PDF, it was all good.

No need to get angry or uninstall anything. Please see the following post for an update regarding your issue: https://forums.eagle.ru/showpost.php?p=3095521&postcount=1

ATME uses trigger.action.outSoundForGroup(). I would love it if we could put ambient sounds in the actual world instead of over the radio.

There is always the Flak script by Stonehouse for mission designers: https://forums.eagle.ru/showthread.php?t=125774

You could loop through all of the coalition's groups and destroy them: (example to destroy all RED groups) local groups = coalition.getGroups(coalition.side.RED) for _, group in pairs(groups) do group:destroy() end

GreyEcho, I believe what you are looking for is TransmitMessage, not transmitMessage for the command ID. Also, trigger.action.radioTransmission() does not handle subtitles, as far as I know. You would need to combine it with one of the trigger.action.outText* methods. Here is the only documentation I could find with the command ID in Pascal case instead of camel case: http://dcs.readthedocs.io/en/latest/task.html#dcs.task.TransmitMessage

Ensure that dcsw.css is in the root directory of the site. The default type attribute value for rel=stylesheet is text/css, so I wouldn't think that you'd need to add that. No ending tag or self-closing forward slash required. I don't see anything wrong with your HTML at first glance. Is this the page that it is supposed to be on? http://www.c9114110.myzen.co.uk/sim/dcsw/dcsw.htm If so, I do not see the link tag in the markup head section. If not, could you please provide a URL?

As Grimes noted, the string values in the actual mission file are referenced inside the .miz archive in the /l10n/DEFAULT/dictionary file. I have always figured this was for localization, and now it is confirmed! For example, after saving a new mission designed with the latest release build (not sure when this was changed to this behavior, using the dictionary lookup), the mission file has a key/value of ["name"] = "DictKey_GroupName_5". If I look in the dictionary file, I see ["DictKey_GroupName_5"] = "MyGroupName" (or obviously whatever I set it to be in the mission editor). I do not believe that there is anything wrong with your setup, Wright_GR1. The mission will behave fine. They groups are queried via LUA fine as well.

I'm using 378.49 without issues, but I'm also running a GTX 1070. Wife has a GTX 970 using 376.33 and DCS runs smooth as silk for her. I've been lucky and never encountered the issues that some others have. </2¢>

I keep something running in the background (text editor or browser). I find that I don't need to do the ctrl-alt-del that way, only alt-tab.

It appears to have come out with v1.5.4.55952.150 Update 4 on 8/19/16. Although the official changelog (https://forums.eagle.ru/showpost.php?p=2878359&postcount=31) did not mention it, it was listed in the Gazelle changelog (https://forums.eagle.ru/showpost.php?p=2769411&postcount=1). I see that it is listed on the Polychop website (http://www.polychop-sims.com/dcs-module-gazelle-sa-342/) also: Interestingly enough, as you point out, I see no mention of this feature on the DCS website. Instead, I see this: "sniper team in rear compartment". :) I'm sure that Polychop has their hands full right now, and we will see some cool features/fixes/adjustments yet to come!

Multicrew is indeed working, but with a few issues. To get around the majority of the sync problems, just make sure that the helo is fully started before the second player joins.

Trip, I got a chance to test this today. We found out that if we fully start the helo before second player joins (as normal procedure), fly around and shoot enemies, then land and shut down, I am able to restart the helo and continue to have full functionality. The issue seems to be during the first startup and second player joining.

You can always edit the [DRIVE]:\Users\[uSERNAME]\Saved Games\DCS\Config\serverSettings.lua file manually if the UI is being stubborn. Set cfg.require_pure_clients = false

TripRodriguez, the wife and I play over LAN all of the time. Here is how we set it up: Using DCS 1.5.5 (release) 1) On host PC, Start DCS and choose the Multiplayer tab 2) Choose New Server at the bottom 3) Enter Server Name & Server Description - I uncheck Public Server, leave the Password field blank, lower the Player Limit to 2, and unselect Integrity Check 4) Add mission to Mission List 5) Hit Start and let the mission load Host PC (no port forwarding, open firewall, or anything like that) [WAN IP masked]: 6) On client PC, start DCS and choose Multiplayer tab 7) Choose Connect By IP at the top 8 ) Enter LAN IP - I don't enter port nor Password 9) Hit the arrow to connect Client PC (again, nothing special done to firewall/AV, just hooked to same router): SA342 Notes: We wait for the server to completely load, the first player chooses the coalition and enters the helicopter (and unpauses the server in our case), and starts the helo all the way up before the second player joins. It has been our experience that there are sync issues if we don't follow this procedure (tail falls off during startup, weapons missing, players see different things, and so forth). Once the helo is spun up completely, my wife joins in and selects the second seat. There will be a permission box that pops up for player one to confirm the join of a second player to the helo. Select their name, hit OK, and enjoy SA342 multiplayer! Hit me up if you have any questions. We do this all of the time without any special/fancy network setup or equipment/software. The only thing we have to do is have our own licenses (two copies of the game) and ED accounts.

My wife and I fly together in the Gazelle, and it is a blast. I get us there and back in one piece, and it is her job to navigate, shoot, and yell "incoming" a lot! I have flown many hours by myself, and there is no comparison when there is another person in the seat beside you. The workload of trying to fly and shoot is almost too much when in hostile territory. When you have another person, you can really focus on your tasks and not have to jump back and forth between seats. There are a few bugs that still need to be ironed out (ADF), but I'm sure that Polychop is on top of it and we will see many excellent updates in the future. I would highly recommend the multiplayer experience in the Gazelle.

For those who don't like the light sounds (or don't want the boss to hear you having fun): User CP -> Edit Options -> Christmas lights settings -> Silent

https://forums.eagle.ru/showthread.php?t=91074

local redFlagValue = trigger.misc.getUserFlag("1") local blueFlagValue = trigger.misc.getUserFlag("2") local msg = string.format("RED: %i BLUE: %i", redFlagValue, blueFlagValue) trigger.action.outText(msg, 10)This will display the message for ten seconds to all players.

After modification of your LUA script, save it on your PC. Delete the Do Script File action in the mission editor and hit Save. Then, add the Do Script File back into your mission pointing to the updated script and hit Save again. This should update the .miz file with your latest script. This has been a "thing" for a while now.

https://forums.eagle.ru/showthread.php?t=176477

Post deleted.

I do not think so: https://forums.eagle.ru/showpost.php?p=2629387&postcount=542