FlightControl

Okay guys, thanks for the feedback. Will dig into this as soon as I can trying to find the root cause and fix it. Sorry this happens... Sven

You have git desktop installed? Right click on the moise repository on git desktop. Select open gitshell... In the gitshell, execute: git submodule update --init What does that do? Fc

This is already done in the moose framework... However, slingload cargo is still an open to be added... Check the test missions. Really, check them out. https://github.com/FlightControl-Master/MOOSE/tree/master/Moose%20Test%20Missions/CGO%20-%20Cargo Our the videos: local CargoSet = SET_BASE:New() CargoSet:Add( "Engineer1", AI_CARGO_UNIT:New( UNIT:FindByName( "Engineer1" ), "Engineers", "Engineer", 81, 2000, 25 ) ) CargoSet:Add( "Engineer2", AI_CARGO_UNIT:New( UNIT:FindByName( "Engineer2" ), "Engineers", "Engineer", 64, 2000, 25 ) ) CargoSet:Add( "Engineer3", AI_CARGO_UNIT:New( UNIT:FindByName( "Engineer3" ), "Engineers", "Engineer", 72, 2000, 25 ) ) CargoSet:Add( "Engineer4", AI_CARGO_UNIT:New( UNIT:FindByName( "Engineer4" ), "Engineers", "Engineer", 69, 2000, 25 ) ) local InfantryCargo = AI_CARGO_GROUPED:New( CargoSet, "Engineers", "Engineers", 2000, 25 ) local CargoCarrierFrom = UNIT:FindByName( "CarrierFrom" ) local CargoCarrierTo = UNIT:FindByName( "CarrierTo" ) -- This call will make the Cargo run to the CargoCarrier. -- Upon arrival at the CargoCarrier, the Cargo will be Loaded into the Carrier. -- This process is now fully automated. InfantryCargo:Board( CargoCarrierFrom ) -- Once the Cargo has been loaded into the Carrier, drive to a point and unload the Cargo. function InfantryCargo:OnEnterLoaded() self:__UnBoard( 1 ) self.OnEnterLoaded = nil end -- Once the Cargo has been unloaded from the Carrier (the Cargo has arrived to the unload gathering point), OnBoard the Cargo in the other Carrier. function InfantryCargo:OnEnterUnLoaded() self:__Board( 1, CargoCarrierTo ) self.OnEnterUnLoaded = nil end

Spoke with ciribob a few weeks ago shortly. He would be supportive to rework the CTLD within the moose framework. Unfortunately, he does not have time now. My take in this would be to slowly get cargo functionality in, to support the basics like pickup, deploy and transport cargo. These functions are planned both for AI as for HUMAN cargo handling. Nite that moose already has cool cargo handling... https://github.com/FlightControl-Master/MOOSE/tree/master/Moose%20Test%20Missions/CGO%20-%20Cargo Just copying over scripts like the CTLD would be silly. There needs to be an additional value. I believe that creating components that can handle cargo tasks would be a first piece of the puzzle. I am a helicopter pilot myself and can follow totally what Dooom is aiming at. But lets first walk and then run :-) Fc

I wouldn't call it amazing (yet) :joystick:, my friend. It contains useful parts, but it's not amazing. It is good to level the expectations a bit. It can get to amazing, probably, if people are open to adapt it and extend on it. That would be amazing. Fc

Solve DCS folder sync problem Many had problems with syncing the DCS folder. Follow this installation manual, and browse to section 2.2.3 that explains how to get your DCS folder on your pc. http://flightcontrol-master.github.io/MOOSE/Installation.html Here's the extract: 2.2.3) Sync the Dcs folder in the MOOSE repository On your local MOOSE directory, execute the batch file DCS_Folder_Sync.bat. This will sync the dcs folder in the MOOSE repository from the submodule DCS API. The Dcs folder is what we call a GITHUB submodule, which needs to be synced separately. You will be notified when you need to re-sync the Dcs folder through GITHUB channels. FC

MOOSE documentation Had an hour or two today, I've updated the moose documentation site adding: - Installation documentation - Configuration documentation - Social media documentation - Example and MOOSE explanation - Restructured the main page Added with pictures and explanations. You can find the MOOSE framework documentation here: Moose by FlightControl-Master Let me know what is unclear, what is missing or what is too much documentation :-) thanks, FC

THANK YOU GRIMES! @Grimes, I've seen you added the MOOSE framework link in the Hoggit scripting site: http://wiki.hoggit.us/view/Simulator_Scripting_Engine_Documentation Would like to say THANK YOU for this generous deed! Fantastic! Note that I am currently also reworking the MOOSE documentation site. Any comments or feedback from your side is welcome and will be listened to! Sven

On top, I am also improving on the documentation of the MOOSE framework main site. This to allow anybody independently from videos set the environment, including screenshots etc. If you browse now to the site, you'll see work in progress (= incomplete stuff). (The site in on the first post in this thread). I'll let you know when it is setup. FC

Okay, I think I understand what you are looking for: you want to see the script file of the mission, right? Each .miz file is actually a .zip (=zip file). You can uncompress this file with unzip or 7zip or any other compression tool. Unzip the mission file into a separate directory. Now go into the directory, and follow the following file path: l10n\DEFAULT You'll find the mission.lua file in there. Sven

Open the mission in the dcs mission editor. In the DCS ME, click the "triggers" icon. You'll see 2 or 3 triggers only which are activated at mission start. The first trigger contains a DO SCRIPT FILE action. This trigger loads the Moose.lua file. The second or third trigger also contains a DO SCRIPT FILE action, and usually will load your mission script USING the MOOSE classes declared in the previous trigger (Moose.lua). Side note: This kind of your feedback is important for me to understand on what "level" potential users are and what I will need to explain in the Moose documentation and videos. so, thanks! Fc

What do you mean with a "relative.lua" file? FC

Yes. Moose loads in 2 different modes. Static for users. Dynamic for developers. Just use the static method for the moment ... Have fun. And... Where is that PM that you need to send me :-) (You don't have an email?) Sven

Ehh... Syntax error... %$#@!?... Just kidding ... What do you mean with ctts? Maybe elaborate a bit.

In the meanwhile, click this link: http://flightcontrol-master.github.io/MOOSE/ Browse to the section"MISSION DESIGN WITH MOOSE". This may help you. Fc

Today is weekend. Horse riding at 14.30 with the kids. Tomorrow violin lessons and a concert from my 3nd daughter, who is 10 :-) I like to cook. I'll enjoy making waffles this afternoon. The next time I'll be looking into moose videos is Monday or Tuesday. Hope you can wait till then... Will make some videos to get the starters on board. And redo the videos to get the environment setup, completely with tools et all. Thank you really for the nice messages and appreciation. Sven

Hi Shagrat. I thank you for your message. There is not much I need to add to it. You are a nice person. And by the way. Many people active on this forum could evaluate the underlying message of your mail also, for themselves. Let me send you a PM. Sven

Have a look at this test mission: https://github.com/FlightControl-Master/MOOSE/tree/master/Moose%20Test%20Missions/ZON%20-%20Zones/ZON-510%20-%20Send%20message%20if%20Clients%20fly%20the%20first%20time%20in%20the%20Polygon%20Zones -- Name: ZON-510 - Send message if Clients fly the first time in the Polygon Zones -- Author: Wingthor and FlightControl -- Date Created: 20 January 2017 -- -- # Situation: -- -- There are a couple of player slots of Su-25Ts, that need to fly through two poly zones. -- Once a player flies through a poly zone, a message will be sent. But only once. If he flies back through the same zone, -- nothing is displayed anymore. Unless he logs off and rejoins the mission. -- -- # Test cases: -- -- local PolyZoneGroup1 = GROUP:FindByName("PolyZone1") local PolyZoneGroup2 = GROUP:FindByName("PolyZone2") local PolyZone1 = ZONE_POLYGON:New( "PolyZone1", PolyZoneGroup1 ) local PolyZone2 = ZONE_POLYGON:New( "PolyZone2", PolyZoneGroup2 ) local RedClients = SET_CLIENT:New():FilterCoalitions("red"):FilterStart() SchedulerInit, SchedulerInitID = SCHEDULER:New( nil, function() RedClients:ForEachClient( function( MooseClient ) -- Here we register the state of the client in which step he is in. -- We set the state of the client "ZoneStep" to 0, indicating that he is not out of the first zone. local function ResetClientForZone( MooseClient ) BASE:E("Reset") MooseClient:SetState( MooseClient, "ZoneStep", "0" ) end BASE:E( { "Alive Init", Client = MooseClient } ) MooseClient:Alive( ResetClientForZone ) end ) end, {}, 1 ) Scheduler, SchedulerID = SCHEDULER:New( nil, function () RedClients:ForEachClientInZone( PolyZone1, function( MooseClient ) BASE:E( { Client = MooseClient, State = MooseClient:GetState( MooseClient, "ZoneStep" ) } ) if MooseClient:GetState( MooseClient, "ZoneStep" ) == "0" then MooseClient:SetState( MooseClient, "ZoneStep", "1" ) MESSAGE:New("Lorem Ipsum", 15, "Pilot Update" ):ToClient( MooseClient ) end end ) RedClients:ForEachClientNotInZone( PolyZone1, function( MooseClient ) BASE:E( { Client = MooseClient, State = MooseClient:GetState( MooseClient, "ZoneStep" ) } ) if MooseClient:GetState( MooseClient, "ZoneStep" ) == "1" then MooseClient:SetState( MooseClient, "ZoneStep", "2" ) MESSAGE:New("Ipsum Ipsum", 15, "Pilot Update" ):ToClient( MooseClient ) end end ) RedClients:ForEachClientInZone( PolyZone2, function( MooseClient ) BASE:E( { Client = MooseClient, State = MooseClient:GetState( MooseClient, "ZoneStep" ) } ) if MooseClient:GetState( MooseClient, "ZoneStep" ) == "2" then MooseClient:SetState( MooseClient, "ZoneStep", "3" ) MESSAGE:New("Lorem Lorem", 15, "Pilot Update" ):ToClient( MooseClient ) end end ) end, {}, 10, 1 )

Will try to make a demonstration mission to show you how to use the API. FC

Hi ENO, I read your response and felt that there is a potential moose user here, but something are missing. Therefore, and if this is true, may I ask you what can get you from noob to a confident user? I mean, is it ...: - time? - find your way? - documentation (quality)? - lua knowledge? - learning curve too steep? - other topics? Pls feedback. Fc

Went for a run in the park this morning. Quite cold here these days.

Ha! That is why there are members with astronomically high green boxes! Fc

Well.. I got recently 3 new votes with green. I was at 11, but am still at 11.

Yes and no. Yes, because you can easily setup a front line engagement using the SPAWN class. For this, I advise you check the gori valley mission video series. I've just only created 4 videos, but check out the 2nd one, and the briefing one. No, because there is no "front line" governor in the framework. Concerning the CAP, this is currently in beta. In our group we're just discussing how it can be made more efficient and govern the patrol of groups of planes in a more coordinated fashion. FC

Hence my question, the list is large (growing), but reputation didn't increase... So I was wondering and took the courage to ask ...