Highwayman-Ed

Fixed! It was the Armed houses that have been removed from the latest versions of DCS World :) I edited the mission file directly with Notepad++ and I swapped them out for infantry. It now loads up perfectly in the ME, so I'm off to fly it! Thanks for the mission Megagoth edit: single player fixed now, appologies for the false start! SP Angels in the Dark v0.8.miz COOP 4 Angels in the Dark v0.8.miz

Me too, looking to see if I can find the issue...

To keep everyone in the loop, I think that I've identified a way to update the missions for DCS World without breaking them... I'll post up here when they're confirmed as fixed.

Nice Beech :)

Sweet, thanks guys Edit: Thanks, but it still doesn't work propperly... Now some sounds play, but not all and the ogg files play perfectly well in VLC.

Any sound command in a triggered action is not working. I've been messing around with VERGEEV campaign to make it compatible for DCS World, but sounds in the triggered actions do not occurr. To test this out, I built a fresh mission from scratch and implemented a trigger after TIME IS MORE: 10 Seconds and listed the actions as MESSAGE TO ALL: TEST and SOUND TO ALL: sample.ogg When I press play in the Mission Editior, the sound file plays correctly. In game however, the trigger is actioned, the message comes up on screen, but the sound does not play. Maybe related to this issue: http://forums.eagle.ru/showthread.php?t=91038

So the missions themselves work fine, but there are a couple of caveats when installed into a clean DCS World environment with Ka-50 (and other modules) installed... 1. You must extract the missions into a folder in the DCS World\Mods\Ka-50\Missions\EN\Campaigns folder for the campaign to be seen by DCS. 2. The skins for the players Ka-50 have changed in DCS World since Black Shark and the result is the Orange missing texture template as seen below. 3. The Yak 40 also has the Georgian skin in place of the Russian Aeroflot skin due to changes in DCS World. Ka-50 skin error Yak-40 skin error As I said, the structure of the missions, and the triggers in mission 1 function as they should. The unit disposition and activations occur as they should. The English translation could do with a little brushing up from a native speaker, but it is clear what is expected of you and for the money it's absolutely worth it. I'm editing my missions to tweak these inconsistencies out and resisting the urge to look 'under the covers' too much at the mission logic, but unfortunately as soon as they're editied and saved they loose the briefing images and the sound, and although I've managed to get the originals by extracting them from the miz files, despite implementing the hot fix that Wags posted for the in game sound files, only some of them will then play in the ME and in game :(

Excellent production

+1 Purchase was smooth (from my iPad), but PayPal is also my preferred method and I would have liked to use it. Seeing a payment method listed that is not available next to all of the 'verification tags' from MasterCard, Visa and so forth makes you think twice about entering you details and the sites legitimacy... Just my thoughts... Waiting for the email and download links now. Once installed into DCS: World I'll post back.

Looks like it, I'll pick it up and give it a go and post back

I think you're asking the wrong question. I'd be surprised if anybody wouldn't like to have the Super High (which is where I put my vote). I think you'd be better asking what is the minimum fidelity that you'd accept. Like: Super High Accept: High

Looking great there Diveplane :) Have you built a collision model for it yet and a dead version of it for when our Mavericks fly though into those sneaky SA-19's? Also, have you thought about tank revetments, they'd be great too!

If Fog of War is enabled in the options, only OPFOR units that have been detected will appear on the map view

Fixed, thanks Mustang :thumbup:

In fullscreen mode, whenever I start a mission in DCS: World the GUI shrinks down and the new window pops up whilst loading the environment. When the mission is loaded, I'm presented with the briefing dialogue or the choose unit / side box, but the window is not 'in focus' and my mouse interacts with the desktop under the simulation window. ALT-Tabbing around to the DCS: World window brings it back into focus and it then works correctly.

Not a significant issue, but when starting the ME to work on something you have in progress for example without having done anything else, you're warned that all unsaved changes will be lost when you click on the 'open' button when there haven't been any.

Working fine at 1920x1080, looks like a resolution issue, have you tried a lower resolution to see if the issue remains?

Quite right on the perform types :) edited to make them more accurate. I was typing on the fly ;) As you've said, a stop condition can be applied to an enroute task the same way as I've described for the Perform Task : Attack Group above which I have in this mission for a CAS tasking.

I think that the way the logic works, it evaluates a statement in the list from the top down and executes it based on the current situation. For example; 1: Perform Command: Switch to Waypoint = 7 Condition: User = 1 2: Perform Task: Attack Group = Enemy1 In this scenario, as soon as the AI starts this waypoint leg it will evaluate the first statement. Let's say that the trigger you have set to set flag 1 has not yet been triggered, so the AI disregards the Action because the condition User = 1 is false and it moves to the next statement. Now the AI will begin to Attack Group: Enemy1 until all of the units in the group are dead or it is out of the required munitions, at which point it will look for another statement. If none are found, as in this case, it will move on to the next waypoint. The way to stop them here should be to add a Stop condition to statement 2, such as User = 1, the same as you've set for it to switch to waypoint 7. You can then either copy statement 1 after statement 2 or set the same statement at the top of the list in the next waypoints actions. 1: Perform Command: Switch to Waypoint = 7 Condition: User = 1 2: Perform Task: Attack Group = Enemy1 Stop Condition: User = 1 3: Perform Command: Switch to Waypoint = 7 Condition: User = 1 With these statements, the AI should start this waypoint leg and evaluate the first statement. 1: If flag 1 is true it will immediately switch to Waypoint 7. If Flag 1 is false, it will move on to the next statement. 2: Start attacking group Enemy1 until all units are dead, AI is out of the required munitions or until such a time that Flag 1 is true, then move to the next statement. 3: If flag 1 is true it will immediately switch to Waypoint 7. If Flag 1 is false, it will move on to the next waypoint as there are no more statements. I hope this makes sense, and I'm hoping it works that way as I'm currently building a mission using this same logic :)

Running DCS: World 1.2.0.3205 with A-10, BS2 and Combined Arms modules installed. I've set up a trigger in game to add a radio item to scrable a Combat Air Patrol to the RED team, and I also have one added in exactly the same way for the BLUE team as shown here: It appears that setting the COALITION: condition is having no effect however. The result is that both sides see two radio messages, but the messages do work correctly. If the Red team selects the first message, it scrambles the RED CAP as it should. If the RED team select the second message it does nothing whereas if the BLUE team selects the second message, the BLUE CAP scrambles and selecting the first message does nothing.

Kind of related to a handbrake issue is that if you're barrelling along in your M1 and you want to stop quick, hit the Autopilot key and you will stop instantly!

This game has massive potential, and as a multi-player human only game it's very good, the flight model is as you say one step above ArmA, but it's still very basic. My biggest issue with it is the AI sucks at anything but being infantry. Vehicles and aircraft pathfinding are appalling, so if you're planning to play the campaign, move along... My rating 5/10 :(

Great, Thanks Wags :)

In my opinion, dust trails of the vehicles and the smoke from firing weapons such as seen from the sight of the M1 Abrams in the screens below is much too dense. the result is that by the time the smoke has cleared, your shot has landed and the resulting impact mark can not be seen, unless of course the target was destroyed :)

Fantastic, I loved this game and I can't believe that I missed this mod! Time to dust off the DVD and get it back on my system!