MOOSE - Mission Object Oriented Scripting Framework

[X_Man]

It's working!!!!

 

00322.307 INFO SCRIPTING: *** MOOSE STATIC INCLUDE START ***

00322.307 INFO SCRIPTING: Moose Generation Timestamp: 20170120_1818

00322.307 INFO SCRIPTING: Init: Scripts Loaded v1.1

 

I did notice Include.programpath = Scripts/moose/moose

 

Include.missionpath = c:users/*** were not in the log - is that OK?

Edited January 22, 2017 by X_Man

[FlightControl]

It's working!!!!

 

00322.307 INFO SCRIPTING: *** MOOSE STATIC INCLUDE START ***

00322.307 INFO SCRIPTING: Moose Generation Timestamp: 20170120_1818

00322.307 INFO SCRIPTING: Init: Scripts Loaded v1.1

 

I did notice Include.programpath = Scripts/moose/moose

 

Include.missionpath = c:users/*** were not in the log - is that OK?

 

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

[TBear]

Update, my mission built with Moose is available now here: https://www.digitalcombatsimulator.com/en/files/2333673/index.php

 

I was waiting for this kind of mission long time...thank U very much :thumbup:....BUT....dont we need also the relative .lua file? :smilewink:

[FlightControl]

I was waiting for this kind of mission long time...thank U very much :thumbup:....BUT....dont we need also the relative .lua file? :smilewink:

 

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

 

FC

[TBear]

No..not "relative.lua"...my bad way to talk, sorry.

 

I mean his "... .lua" file. I guess his name is "Valley Patrol.lua"

In the download page there is only the . miz file and not his .lua file. I guess its needed.

[FlightControl]

No..not "relative.lua"...my bad way to talk, sorry.

 

I mean his "... .lua" file. I guess his name is "Valley Patrol.lua"

In the download page there is only the . miz file and not his .lua file. I guess its needed.

 

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

 

FC

 

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

[TBear]

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

 

As u say there is the trigger that loads the Moose.lua file (and i already have it in my "Missions" folder).

 

Thene there is another trigger:

MISSION START(load mission) --> DO SCRIPT FILE(Valley Patrol.lua)

 

what is missing is the Valley Patrol.lua file that is needed to be in the "Missions" folder (it wasn't in the ED download page)

[FlightControl]

This is where I'm at with it too. I got eclipse (neon 2?) loaded- I think that's what we needed? Or no?

 

I downloaded the whole moose master folder from github- not sure if that was right (sorry, not really familiar with it).

 

I'm not sure what file needs to be loaded in eclipse... from there I can see the various missions that help you add what content you want. I know FC is busy today- maybe someone else can weigh in?

 

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

[FlightControl]

yup - you are right on track - there is a youtube development tools setup video that FC did that walks through setting up eclipse/logedit/github etc... from what i see on git, there is a plan to get a new develpment environment setup video up real soon to help us new folks get up and running... some of the framework file structure is not the same as what was in the tutorial vid anymore so i think it stumbled a few of us up...

 

i am really looking forward to it now that i have watched his demonstration videos.

 

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

[FlightControl]

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

[blklobo]

Thanks a lot FC!

MOOSE is so amazing.

 

thank you.

[TBear]

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

 

Then Delta99 forgot to upload it togethr with the .miz file :music_whistling:

[FlightControl]

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

[FlightControl]

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

Edited January 22, 2017 by FlightControl

[shagrat]

ctts is the Complete Troop Transport Script by geloxo ... it is a very popular script being used by many of the helicopter mission designers as it allows for the simulated transporation and pickup of troops by helo along with the associated F10 menu commands. It can also allow clients to drop beacons and build forward site units like SAM sites and outposts by transporting crates. Although i know MOOSE has some great board/unboard abilities within, I am unsure how to expand this transportation to mimic the wider funtionality of CTTS yet in terms of the beacons etc.

 

another neat function of CTTS is that the dropped infantry will seek out the enemy i believe. I think this could be achieved with moose by transporting and then using the patrol zone capabiliities but im unsure yet..

i am super looking forward to the setup videos to get my eclipse setup finally all squared away (im stuck at that add DCS to the build part :) ) as soon as i get past that, i'll start playing with LDT and the test missions you provided.

 

great stuff FC!

CTTS is more or less obsolete. I recommend to use CTLD by Ciribob. Basically a rewrite of Geloxos script, with many, many enhancements. ;)

[Delta99]

Then Delta99 forgot to upload it togethr with the .miz file :music_whistling:

 

TBear are you saying for learning purposes or to get the mission to work? The .lua is embedded within the .miz file as FlightControl mentioned so the mission will work as is.

[Delta99]

I was waiting for this kind of mission long time...thank U very much :thumbup:....BUT....dont we need also the relative .lua file? :smilewink:

 

Thanks. I will be expanding on this as well I hope.

[FlightControl]

Thanks a lot FC!

MOOSE is so amazing.

 

thank you.

 

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

[Delta99]

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

Don't sell yourself short. At this point Moose is amazing even if left in its current state.

[FlightControl]

CTTS is more or less obsolete. I recommend to use CTLD by Ciribob. Basically a rewrite of Geloxos script, with many, many enhancements. ;)

 

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

[shagrat]

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

Good idea. I reckon we can have typical "cargo" class, that can include normal "cargo" objects like a box we currently have in DCS for slingload, etc. and a special cargo object "Infantry" that contains "people". If we can have two different "load" actions (sling/internal) we could easily model troop transport and sling loading "stuff" in one general class?!

[awjudge]

Hi FlightControl,

 

I've tried this and it does't appear to do anything, I don't get a DCS folder under Moose Development. Is there another method for syncing the submodule?

 

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

[FlightControl]

Good idea. I reckon we can have typical "cargo" class, that can include normal "cargo" objects like a box we currently have in DCS for slingload, etc. and a special cargo object "Infantry" that contains "people". If we can have two different "load" actions (sling/internal) we could easily model troop transport and sling loading "stuff" in one general class?!

 

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

[FlightControl]

Hi FlightControl,

 

I've tried this and it does't appear to do anything, I don't get a DCS folder under Moose Development. Is there another method for syncing the submodule?

 

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

[awjudge]

Thanks for the quick reply!

 

I have Git desktop installed, and I have Moose added as a repo.

 

I've tried both the .bat file and the git shell. When I try the gitshell I don't get any output from that command, it returns me to a prompt without any output.

 

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