FlightControl

Do you have mods installed or anything?

*** REPOST *** Sry, but i had included the wrong link :-( Now it contains the correct one. --- Guys, Been working on the AI_A2A_DISPATCHER module, which is a new capability that may be an addon or something similar like the GCICAP module, but in its current form may require some coding experience or coding practice to use it and set it up. Why? Because there are a lot of parameters that you can set and define. What i suggest you do is, can you please have a look at this video here, which is explaining how it works, and what to expect: After watching the video, do you think the methods as explained in the video would be something you could apply? Or is this totally out of the question. I know that opinions may differ, as there is a broad audience. I haven't released this module yet, as I want to have it fit for purpose. I am getting some very good feedback on slack, and need to let this sink in a bit. I don't want to release something that people will reject or find too difficult to use. I get mixed feedbacks from the moose community, but wanna try with a larger audience, like here ... (It takes some courage to write this...) @Stonehouse and Pikey, and @beamrider14, I have understood the views and will try to accomodate those. If okay would like to hear other people and understand their unbiased opinion. FC

This is an example how missiletrainer works with a ship missile ... MIT-002 - Missile Trainer Ship.miz

This is exactly how the CLEANUP class within the MOOSE framework is working around the problem. But from experience it is marginally successful. CLEANUP monitors the hit events. When hit, and the unit has a damage level beyond a %-tage, it will be removed. It also tracks the height of the unit and the position. When the unit is above the runway, and below a certain altitude above the ground, it will be removed if the direction vector and the speed is such that it would crash. This is done with a timer. It also checks when groups are dead. If a unit or a group is artificially destroyed, CLEANUP will generate a S_EVENT_CRASH artificially. In this way, I try to keep the air base clean while still having some game experience. But the slightest hickup or delay in the check process can still make an airbase operations stall. I understood from ciribob, that for ED to fix this issue, it is not so easy. There seems to be a difficulty with accessing destroyed units. Probably they are removed from the sim when dead... It used to work though till version 1.2.6, when a unit would be destroyed using Destroy(), directly after processing the S_EVENT_DEAD or S_EVENT_CRASH, it would remove the unit!!!! Even in muti player! However, indeed Kyridious, there are ways around this issue, but it is far from perfect and consumes CPU. http://flightcontrol-master.github.io/MOOSE/Documentation/CleanUp.html I didn't want to publish this because it is a crappy solution for the moment. Fc

My friend this development already exists i think.... http://flightcontrol-master.github.io/MOOSE/Documentation/MissileTrainer.html No? Sven

Missile trainer will only work for missiles. What other things you want to get it to work for? Also you confuse me a bit. Are you talking about the MISSILETRAINER class in moose? So, how does the defense jamming script related to the MISSLETRAINER class? the :getRadar() will only work for airborne units. Ships aren't detected by radar. They should be detected with the detection capabilities of the dcs scripting engine. Sven

Yeah. But strangely enough, my kids were last week giving me hugs :-)

Ok. Have a look here to setup your environment. It contains some useful material to setup a cool dev environment.

Sure! There are many ways to add trigger zones using lua. When you use lua, a whole world opens with new possibilities. I assume you are familiar with lua, as you're asking. The low level APIs within DCS are documented at hoggit. There you can find the definitions how to use trigger zones in lua. http://wiki.hoggit.us/view/Simulator_Scripting_Engine_Documentation namely here: http://wiki.hoggit.us/view/DCS_func_getZone But there isn't really an API to set new trigger zones. Instead, there are frameworks that have created new types of zones! These possibilities are endless ... There are a couple of frameworks that you can use. Grimes has listed them for you here: http://wiki.hoggit.us/view/Simulator_Scripting_Engine_Documentation#Classes If you like to develop procedural lua, and you don't have a lot of time, learn and use Mission Scripting Tools or MIST authored and managed by Grimes. If you like to develop Object Oriented lua, and have some extra time to invest learning a larger framework, use MOOSE, which at the end provides you with a lot of extra stuff and faster implementations. I suggest you have a look at this video that shows you how things are done the "MOOSE" way. The video is a bit old, but still valid. You can try these things out yourself here by running one of these test missions: https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master/ZON%20-%20Zones Hopefully this helps! If you like this and would like to use, please come back and send me a PM. FC

Ok. However, you'll need the FSM classes for this. I can explain you how to get up to speed with this stuff. AI_FORMATION as an example. AI_PATROL, AI_CAS... The trick is to understand the technique and the design components to make these processes. Suggest I help you with this explanation. Once understood, you'll be launched. There are many tricks in the sleeve and dont want you to reinvent the wheel. You know what i mean.

....

Writing this from a cozy terrace in a lovely weather in front of an authentic Belgian beer ... Duvel ... The CDT problem in DCS world 2.1 has been mitigated. There is still a minor issue in the DCS scripting engine, but could be workaround in MOOSE with adding an extra test. The dev team of ED has been reported of this issue and may go for a fix. Patch 2.1.5 has been published of the MOOSE framework. You can download it from here. Please use the new moose.lua in your missions for Normandy and Nevada. https://github.com/FlightControl-Master/MOOSE/releases The fix is also implemented on the master branch of the MOOSE repo for beta testers and contributors. Thanks for your patience and thanks @PVI_Eagle for reporting the issue. Thanks Mike, Nicolo and TJ for the testing and communication. Sven

The AI has a mind of its own. We can however let the AI use its mind, and guide it to what you wanna let them do. The initial requirement that you wrote is a bit high-level and unclear. I'll repeat here: Suggest we first define what is missing, and what you are looking for. Get onto slack again. Let's discuss. FC

And four persons I would like to thank additionally! I don't care if some may find this too much blah blah blach, but I have my reasons to write this down to the community! @grey-echo: He developed BEACON and RADIO in the framework. These 2 classes are great, and are enabling beacons and radio communications within your mission scripting using OO principles. On top, he was making a complete new documentation system that was almost finished. @grey-echo, if you ever read this, a big thanks to your contributions and even more. You designed a new release system for the framework! @Pikey: You've been the most online at slack.com. You were all the time there to advice and help people with scripting issues. You learned lua to a level now that is fantastic to see how much you have evolved. Thank you! @Delta: Same as Pikey, your continuous efforts on the slack site helping others! On top, your lua skills have sometimes kicked me during your tests. Your thorough reports and the complexity of your missions has helped to improve the framework and get the details smoothened out. The new event handling system is an example of that! Thank you! @stonehouse: Been online with me for a couple of sessions, explaining me all about GCICAP. Helping me with the principles of the current solution, and shared the existing documentation. Thank you for your time, which I understand is very limited! I hope the new AI_A2A_DISPATCHER will become a big fun for the community as a result of this after release 2.2. of MOOSE. This is not a one man show, that's all I wanna say. Sven

@PVI_Eagle and others, I found the root cause. Now I need to go for a fix in MOOSE. I need to workaround this problem. Not sure if destroy scenery for SCORING can be kept... Need to check. https://forums.eagle.ru/showpost.php?p=3170996&postcount=9 Thanks for the guys who helped with the testing!

Pls allow me to say a few words. I have mixed feelings about all this. reading the post of Viff, Pikey etc. This should not be a competition. It is silly to make these kind of contributions a competition. These scripts are made for the enjoyment of others, nothing more, nothing less. People who like me code as a hobby, to make something that is liked and used by others. Let me add the following. Ciribob, Xcom, Grimes without your endless efforts this famework would never have been established. There is a ton of advice, techniques and code that was there. Grimes because of MIST, and the fantastic documentation by the way, of the DCS API. Ciribob, I enjoyed your pop-ins from time to time on slack, and always at the moment when it was needed. Without you, the DESIGNATE class would never have have been completed. Xcom, who indeed I learned the basis of the event handling from. And many others who helped. I would like to say however a big thank you to those many people who have joined the sharing site on slack, and have been helping with ideas, requirements, logo design, mission design, their questions, their answers, their continuous contributions. If it was not for Pikey, Delta, Dutch Baron, Ironjockel, DwPenney, Stonehouse, Gunterlund, Wingthor, Beamrider, FunkyFranky, Easy, RobGraham, Greyecho!, Entropy, Afinegan, Alpenwolf, Alwandy, Birgersp, Ciribob, Craigowen, Dooom, Danny, Delta!, Dexa, Dr_Marianus, Dutch Baron!, Eno, Eric, Fubarbundy, Gecko, Hafody, Hijack, Homefries, Ignition, Lemoen, Loosecannon, Mechanist!, Midnite (he was the first to join :-)), Porcorosso (thanks for your testing yesterday and today!), Prof Hilactic, Raf_raven, Ripcord, Sage, Sithspawn, tuka, Tbear!, Vitormoura, Whiplash, ! And a thank to those I may have forgotten! (If I did forget, drop me a PM). Look, I thought writing this polite email as a word of thanks. And also to share what I've learned. Sven

Well, then just drop by when you have time :-) Happy to help you out.

I think the root cause of the issue has been found. I'll try to workaround this DCS crash issue, but maybe SCORING won't work anymore for SCENERY objects as a result of this... It is not a MOOSE issue, it is a DCS bug. https://forums.eagle.ru/showpost.php?p=3170349&postcount=8 FC

Thank you for this message by the way. The problem has been confirmed on our side and we could resimulate this problem. Wanna let you know that people are looking into this problem. It is a weird crash. It will take time to dig into this problem and identify the root cause! Some people from Italy even are helping :-) I am afraid that if we don't find this issue quickly, ED won't look at it anymore later. It is somewhere deep in the event handling where we experience this. I just bought also Normandy map to help find a solution. FC

DESIGNATE may look similar to autolase/smoke, but it works a bit different and interaction is also richer. And it has illumination for night missions. Designate is one little piece of a larger puzzle though :-)

Mobile layout would be good to have.

Hi matador, what is meant with this sentence? "but I finnally never got any finnalized proyect" You mean, you started with something but never finished it? Just curious.

Thank you! May i ask, are you already subscribed to our community on slack.com? Otherwise do me a PM with your email address. It is easier to debug this interactively. While both being on slack we can try to find the root cause together. Sven

Maybe this can be an option? Note that ciribob also helped me making this stuff!!! It concerns the DESIGNATE capability of the MOOSE framework. Find the documentation here. http://flightcontrol-master.github.io/MOOSE/ http://flightcontrol-master.github.io/MOOSE/Documentation/Designate.html YouTube videos explaining it:

How much memory did your device have again?