Iceviper

Cheers. Tried that but it threw up an error when hit. I'll have another go tomorrow. Appreciate the help

Thanks for the speedy response and taking the time to reply. I might also get off the ride at that point lol. I've had some limited success loading moose/mist but by no means am a coder. It makes perfect sense just not quite sure how to implement that. Will chew it over. Much appreciated

If you don't want to script it and would rather do it in ME then this video should help. SUNTSAG has some great ME vids to follow. He also posts some great mods here in the forums

Ok, I think I'm being a bit thick but I've tried all sorts of ways to do this without success. What we are trying to to do is to have client aircraft (set to immortal) that have been attacked by AI aircraft to go invisible for a short period of time and then for them to become visible. The purpose is so that if flying long missions the player will be allowed to continue flying and engage in tasks but receive a message that they are dead or have been hit. That way they can continue to fly without having to sit around waiting for buddies to finish the mission. A Red Flag type scenario. Honestly, I've tried all sorts of things. My latest and what I thought might be the easiest was to use triggered actions on switched conditions. I'll attach the miz file for the latest attempt and a couple of screenshots. What is happening is that any which way I do it in ME, A. The Ai attacks. Hits the client then breaks off and a message shows that the player has been hit (great that's what I want to happen repeatedly) B. After 30 seconds I switch invisibility off and the AI attacks again but instead of breaking off the second time it continues to pummel the player Can anyone tell me if this can be done either scripted or preferably within the ME Thanks in advance :thumbup: Test_Shot_Flag_On_Flag_Off_AC7.miz

Saw that myself yesterday however if you put your cursor over the area of interest then the coordinates are at the left top of the F10 screen. Just not sure how accurate that is. Seemed pretty good for me when punching in a wypt last might Sent from my EVA-L09 using Tapatalk

Yep already watched the video. It's definitely not a set up issue. We are setting up the bombs in the correct way. Some bombs just explode and some don't. Just trying to see if anyone else is having similar problems. The three of us are seeing the same issue. Thanks for the replies so far Sent from my EVA-L09 using Tapatalk

Has anyone else noticed unguided bombs not exploding since the most recent update to the open beta? Been flying with three people for the last two days and we are all experiencing inconsistent bombing results. We were all getting consistent results until the last couple of days. All flying Hornets on Persian and Caucasus maps with no mods installed. I am a noob (before all the wisecracks come about just being crap :) ) but the other two lads are decent with DCS. We've all tried different unguided bombs, and tried CCIP, Auto, Wypt Designate auto bombing and the results have been all over the place. Lots of bombs that are definitely on target not exploding. We are setting fuses etc in exactly the same way we've always set them without any issues before, so can't understand what's going wrong? Anyone else having trouble?

Yeah it's the GitHub that threw me as I had no issues the last time I used it. I realise there's not enough hours in the day for developers to update videos and code as well. I'll take your recommendation and join the discord channel. Thanks for the reply.

@Hardcard Thanks so much for taking the time to reply. You make things much clearer. I'll take another look. I think I need to spend more time looking at GitHub. Things do look slightly different in the setup videos though and I'm not the only one who was caught out. I'll set things up again to ensure I'm using the correct versions. By issue I only meant that error.No others Thanks again. Cheers

Master Moose issue and the development environment? Guys, I'm having an issue. I've not used Moose in a long time but decided to go back and take a look at it today. I downloaded the master from https://github.com/FlightControl-Master/MOOSE (after a little digging for it). It says version 2.4.14. So I presume its the most up to date version. I've followed the to the letter to set up my Lua environment again and to get intellisense working. There are comments to the video regarding errors being received. Error [string 'C:\Users\xxx\AppData\Local\Temp\/DCS~mis000000920']:4: attempt to index 'EVENT' (a nil value) slack traceback: [C]: ? [string 'C:\users\xxx\AppData\Local\Temp\DCS\/~mis000000920']:4: in main chunk I also get that error when trying to load the Moose.lua, which incidentally is now in a different location to the video C:\MOOSE-master\Moose Development\Moose, which is different to the video, however. In the comments, someone helpfully instructs us to use the correct Lua and points to download file. I've done this and instead of placing it in the development folder I've placed it in C:\MOOSE-master and loaded that into my mission it's working brilliantly. My questions are this though. 1. Is there an issue with the original Lua or is to something to do with the file structure? 2. What happens to future updates? Will I just download the lua file and overwrite the one I was supplied by the helpful youtube guy. 3. Is this having any effect on my development environment as I won't be using the same lua as the moose master. If I overwrite the moose file in the development folder with the 2.4.1 version won't it be an old version. Everything seems to be working fine but will I be using the correct version? If I use the one in the development folder I always get the above error. 4. Are the issues being caused because I'm a noob? Have I done something wrong in the installation? bearing in mind I have used this before with success so am not totally green. I also went back over all the setup videos and guides and followed them to what I thought was the letter. Sorry but I'm a noob with this so please go steady with the replies lol. Just as a side note there are a few links in the documentation website that need to be updated to point to the correct files. eg. The documentation here supplies a link for the latest version of moose but it takes me to the moose patch files on GitHub. It looks as if the moose master file has the latest version rather than the patch files nor is it clear how to get from the patch files to the moose release for a GitHub noob like me. Perhaps the website start-up guide would be better pointing to the master repository and a version number could be included there in the guide as well so that we can ensure we are getting the correct version from GitHub. I appreciate this all takes time but I think a few people may be put off from using what is really a fantastic system for the sake of the instructions? Apologies for the length of the post