MK-82_1_EACH

Older post but this has been like this a long time. Probably one of my bigger annoyances. Unless there has been some development I am not aware of.

I haven't gone through all the scenarios, personally I don't do cold starts that often and most of the time just leave it at default 1688. But I would assume that Razbam settings for the laser codes should work (a/c additional settings tab - mission editor) to avoid snags or the priority, since there is some functions with the kneeboard that Razbam has implemented.

What I have experienced TPOD/LST if starting in the air(airstart) will be 1688. If starting from ground will be 1111. Also it seems that if you set the laser code with the mission payload option with the bomb fuzing options (the new fuze options that ED recently added) vs the Razbam options the Kneeboard won't show the correct laser code that is set the bomb. IMHO would be an issue or bug. This module has not been updated in a long time.

My comments got cut off... TPOD is set to 1688 while the LGB are set to 1532 in the mission.

You need to save a track after playing the mission ...

Ha Ha, for sure this drove me nuts at the time. I think its intentional just due the way MP functions and the mission editor. The mission editor does not know the intention or if the mission is multiplayer. Therefore you can do things that will obviously choke if the mission is played as multiplayer and there is no warning. Probably a good example of why DLC creators avoid MP campaigns. You can't trust building a mission to work the same if played in single player vs multiplayer at least in this scenario as there are no warnings of MP constraints when building the mission in the editor.

The changelog indicated: ME. Added trigger "Smoke Marker Stop" and "Smoke Marker on Unit Stop” for the coloured target marking smoke. These trigger actions seem to be missing. My version of DCS is current or DCS 2.9.11.4686 So the question is, does anyone have these triggered actions in their install or are they missing? Thanks in advance.

I was testing this as well and noticed the same results (no visibility and repeating message output (action message). In the log: I went through the various iterations of visibility with the same results with the trigger action "SET VISIBLE DRAW" and it chokes with the above error. In addition - IMHO there seems to be contradictions with the invisible property checkbox (Figures) for the object and the F10 options box for player visibility. Even though this feature is in the documentation, it's vague on intent of the "SET VISIBLE DRAW" action other than to trigger visibility. Documentation (DCS USER MANUAL) : Current behavior: invisible property checkbox (Figures) - will hide the drawing. F10 options box for player type - will hide the drawing. It's not elaborated for the trigger action "SET VISIBLE DRAW" is intended, specifically the invisible property checkbox (Figures) or F10 options box for player visibility. In any case testing both options resulted with the error.

You probably need to apply the stop condition as you don't indicate that you did. It's part of the hold tasking.

Thank you and no need for apologies. Documentation to reach all audiences is a daunting and difficult task.

Looking at Documentation concerning the delicates module, there was no reference on whether moving zones were supported (maybe I missed it - I'm old and somewhat dyslexic ). My testing indicates it's not, otherwise works great. Not a big deal but you might document that it's not supported for moving zones. Of course I assume that is the intent. BTW- Thanks for all the work on DML

I been flying WSO a lot in solo. It's rather tedious or a PIA. I expected that this would have been a feature, pretty much disappointed that it's not a planned feature as with the F-14. Of course trying set up alternate bindings to not conflict with the WSO is even more tedious. I know pretty much this appeals to a smaller audience, at the same time, I assumed this would be a standard with HB multi-role cockpits. I guessed I missed it somewhere in some of the pre-launch communication.

I just found this topic, after trying to complete some WSO training. I guess I can work around with modifiers as I only have one control stick. IMHO I would nice to have a ICEMAN variant for scenarios where or one does not have a real human pilot to avoid the multiple bindings which gets rather tedious.

There is an option in the radio options under "Other" that will disable the pictures (checklists).

After the hotfix this no longer occurs, but I won't contribute this as being fixed by the hotfix. Most likely just restarting DCS/Mission editor resolved it. On occasion seen this in the past when odd things occur and a restart corrects what ever odd state has occurred.