Starting with moose and first issue?

[dr_hippo]

Hi all,

 

Just started with Moose and I have my first issue.

I think installation is ok. No errors!

 

I use Moose version 2.5.0 pre1 and DCS latest 2.5.6

 

As I runned into problems with my first mission I scaled it down to the most easy thing.

Spawning a Tank as in the example.

 

The following errors occurs starting the mission. See attachemetns.

 

I have added the 2 triggers were the load moose is the first trigger.

What is differrent from the guide is the name of the moose file. In this release it is calle "Moose_Create.Lua" intead of moose!

 

Code in LDT

Spawn_Vehicle_1 = SPAWN:New( "Spawn Vehicle 1" )

Spawn_Group_1 = Spawn_Vehicle_1:Spawn()

 

Group and unitname in DCS are "Spawn Vehicle 1"

 

And of course the tank does not spawn.

 

Thanks for any hint

[Habu_69]

You are using the wrong file to load Moose. Download the group of files from here:

https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop

 

 

then load the Moose.lua from the Moose_Include_Static folder. It is about 5 mb.

[dr_hippo]

Thanx Habu_69

 

I am futher, no errors anymore!!!

 

I was able to make my first mission with the simple spawn as described above.

Any addition to the code ore changing the Name ( also changed the name in DCS of course )

and it was not working anymore.

 

So here a couple of questions.

1) Are the versions that I use the right ones?

2) Do I need to copy all the content from "MOOSE_INCLUDE-develop" in the "MOOSE-2.5.0pre1"folder?

 

Thanx for helping me to get started!

[Habu_69]

1. Not sure what you mean by "versions". When DCS spawns a late-activated unit it adds a post-script identifier to the unit names, like "Spawn Vehicle 1 001", or something like that. To overcome problems with changing names you can use the Moose spawn method SPAWN.InitKeepUnitNames() or other methods described in the docs. The most recent version of Moose can be found in the develop branch link that I referenced.

2. If you installed Moose to work with LDT, then over-write all the files and folders with the updated ones from the Github develop branch. But then for LDT intellisense to work properly you have to do the following:

 

 

1. In LDT, Rt.click Moose_Framework

2. L click: Build Path/Configure Build Path

3. Select Source Tab

4. Select Add Folder

5. Select in box: Moose_Framework/../

6. Click OK

6. Select APPLY AND CLOSE

7. Observe LDT refreshing workspace.

[dr_hippo]

What you described is exatly what I have done!

Seems to work somethimes!

 

I do my test with launching the mission from within the missioneditor.

I have the feeling that he doesnot load the updated luas script file?

 

Is this correct?

 

Thanx

[Habu_69]

The Load Script File trigger for your script must be updated at every instance of changing the script. The mission file does not update automatically. Alternatively you can use this device in a Load Script trigger action for testing:

dofile([[Full_Path_To_Your_Script.lua]])

 

-- for example:

dofile([[e:\Game Data\Scripts\Mission Scripts\Air Boss.lua]])

 

 

This will reload the script each time you run a mission. Be aware that this is the script path on your PC, which will not work for anyone else, so on completion of testing replace the dofile with the normal Load Script File trigger action.

[dr_hippo]

Thank you so much!

 

It is working!!!!

[Habu_69]

One other time saver you may be unaware of is to do mission/script testing with the DCS ME in window mode. This allows for very efficient script editing and testing.