Moose Install

[GunghoGW]

HI All

I am trying to crank my mission skills up and move to the next level.

 

Question about the Moose install and Java.

 

 

I am running W10 64X and my normal browser is Chrome with secondary FireFox. Looking at the Moose documents it is recommended to install the Eclipse Lua Development Tools IDEwhich requires Java.

 

 

The trouble is that all of the latest browsers have removed the applet element.

 

 

Question is how to solve this please

 

 

Thanks

Edited November 4, 2018 by GunghoGW
spelling and spacing

[Maverick87Shaka]

HI All

I am trying to crank my mission skills up and move to the next level.

 

Question about the Moose install and Java.

 

 

I am running W10 64X and my normal browser is Chrome with secondary FireFox. Looking at the Moose documents it is recommended to install the Eclipse Lua Development Tools IDEwhich requires Java.

 

 

The trouble is that all of the latest browsers have removed the applet element.

 

 

Question is how to solve this please

 

 

Thanks

I'm not sure why are you talking about browsers java support.

You need the JRE to run Java application.

And the JDK to develop java APP.

 

I Think JRE should be enough to run Eclipse Lua Development Tools IDE

[GunghoGW]

Apoologies, I was confused and realise that i need JAVA JDk and JRE, i have them instalkled now.

 

 

Next is the Eclipse and then MOOSE ..... I think?

[doodenkoff]

If you want to learn scripting and how to script .lua specifically, by all means get the Eclipse LDT.

 

 

 

If you want to start using MOOSE to make mission designing a bit more fun, skip it, install Notepad++ and use the generously provided examples to incorporate elements of MOOSE.

[Hardcard]

Use LDT rather than Notepad++, intellisense is something you want to have available.

[Ignition]

LDT is not so difficult to set up and as Hardcard said it has intellisense which will facilitate a LOT the scripting.

[doodenkoff]

I’ll never understand why hurdles and challenges must to be thrown in the way of someone who wants to start having fun with MOOSE. The folks that have developed this incredible framework have also created one of the most chaotic environments I’ve ever seen as far as simply getting and using the tools.

 

Again, if you want to learn the scripting, and about the .lua scripting language specifically, go ahead and get the Eclipse environment. I use their Python environment and it’s the bomb. But if you just want to make an armor group patrol in a zone, or setup some random air traffic, do this.

 

Go here and get Moose.lua –

 

https://github.com/FlightControl-Master/MOOSE/releases

 

Click the Moose.lua link and save it to a location you remember.

 

Go here and get the example missions and scripts –

 

https://github.com/FlightControl-Master/MOOSE_MISSIONS

 

I highly recommend using the “Clone or download” button and getting the .zip archive. It will include everything you see in the list.

 

Open a mission. Create a trigger that occurs at mission start. It will have no conditions. Its action will be “DO SCRIPT FILE” and the file will be Moose.lua. That will load the Moose framework in to the mission and make it available for ‘stuff’. Personally, I keep my missions in individual folders and within there I have a copy of Moose and whatever script files I create.

 

Create an armor group somewhere on the map. Name the group armor_patrol and give it a route to follow with some waypoints. Make it “patrol-like” by looping the waypoints back to near the starting point. Maybe around an airport or small village or something like that. I’d suggest a relatively short route for this first test.

 

Navigate in the example scripts and missions to GRP – Group Commands/GRP-550 – Patrol a route. Right click on GRP-550 – Patrol a route.lua and open it with Notepad++ (no matter what anyone says, you should have Notepad++ for general purposes anyway).

 

From that example, copy these two lines into a new, blank document in Notepad++. Take note of the comment lines. They offer hints about what these lines do. You can copy them as well, but they aren’t needed:

 

Vehicle = GROUP:FindByName( "Vehicle" )
Vehicle:PatrolRoute()

Replace the word “Vehicle” with “armor_patrol”. On the Notepad++ menu bar, you’ll see “Language”. Click it, scroll down to “L” and choose Lua. Save the file as armor_patrol.lua where you can find it.

 

Make a new trigger. Set it to occur ONCE. I like to stagger events a bit, so use a condition of TIME MORE and 2 or 3 seconds. The action will be another DO SCRIPT FILE and the file will of course be armor_patrol.lua.

 

A little hint here. Either make the route short for this first test, or use the Ctrl + Z combo to speed things up.

 

Run the mission. The armor group should run through its route repeatedly.

 

Now your taking your mission skills to the next level. Congratulations!

 

If you’d like to learn about classes and finite state machines and wrappers and blah, blah, there’s a lot more depth to this than what I’ve described. But if you want to have fun right away, Keep It Simple.

[GunghoGW]

Moose Load Error

 

Continued with the load and config yesterday but got a 1292 to build error when adding moose to the Eclipse LDT.

 

 

Versions ...

 

 

JAVA: jdk1.8.0_191 & jre1.8.0_191

 

 

org.eclipse.ldt.product-win32.win32.x86_64

 

 

 

MOOSE-2.4.7

 

 

Any thoughts onthe error and will moose still work?

[Habu_69]

I am a new-ish MOOSE user with practically no previous background in coding. Regarding Doodenkoff's post, starting with Notepad++ may be fine for one's first venture into MOOSE, BUT once the power of MOOSE becomes apparent, a new mission designer will very quickly want to start tweaking the example scripts and developing unique scripts, for which LDT/intellisense is an invaluable tool.

 

Regarding the LDT 1292 error, it pops up all the time and can be ignored, if the intellisense is working.

Related issue: Not sure of other's experience, but any MOOSE script that includes a SCHEDULER method generates an LDT error: "Something probably wrong with this script" upon opening the script. Error disappears when I start typing.

[Hardcard]

@GunghoGW

 

Don't worry about those build module errors, I get them too.

 

As long as intellisense is working, you'll be fine.

 

 

@doodenkoff

 

I’ll never understand why hurdles and challenges must to be thrown in the way of someone who wants to start having fun with MOOSE.

 

I honestly don't know what it is that you find so complicated about LDT.

All that it requires is source folder setup (which is no hurdle), other than that, you can simply think of it as an advanced text editor (like Notepad++, but better).

 

LDT provides essential information about syntax, available class functionalities, function structure and hierarchy, etc. Notepad++ doesn't.

 

Do you want to know which functionalities are available for, say, GROUP class?

 

Notepad++: Sorry, check the MOOSE documentation if you want to know.

LDT/Intellisense: Here you have them!

 

Do you want to know whether your script is syntactically correct?

 

Notepad++: Why do you ask me? Don't you know your Lua?

LDT: You made a mistake there. / Everything is fine!

 

Do you want to know whether that parameter / variable is being passed the way you want it?

 

Notepad++: Why do you ask me again? You should know your Lua!

LDT: This variable / parameter is being taken from there, see?

 

and so on...

 

In other words, LDT removes very real obstacles and challenges for newcomers (I'm a relative newcomer myself, that's how I know this), it speeds up the learning process and makes it far less painful.

 

Recommending Notepad++ over LDT in this case doesn't make much sense, imho.

But, hey, it's ok to disagree.

Edited November 5, 2018 by Hardcard

[doodenkoff]

[

Recommending Notepad++ over LDT in this case doesn't make much sense, imho.

But, hey, it's ok to disagree.

 

But I'm not recommending a person never use the LDT. I have been very careful to state that if you're interested in learning more about Lua and scripting in general, it's a great idea. I'm not disagreeing with anyone.

 

Why does it seem so difficult to admit, "Yes, the 43 individual steps described in the MOOSE Setup Guide aren't really needed to get started using Moose.lua"? Intellisense literally does nothing to improve the quality of a mission created in the Mission Editor. It serves as an addon in a scripting environment only and improves the quality of scripting; not mission design.

 

I'll repeat this: the developers who have collaborated and created this great framework, have done a miserable job of lowering barriers to using it. There are four important things a person needs to start using Moose.lua immediately; the latest Moose.lua file (2.4.7), the example .lua and .miz files, a basic understanding of triggers, and a text editor.

[Hardcard]

@doodenkoff

 

I think we have different interpretations of the OP's intentions here.

 

I am trying to crank my mission skills up and move to the next level.

 

To me, that means "I want to learn Lua / MOOSE scripting", rather than "I want to grab some random bits of MOOSE code and incorporate it in my missions... maybe I'll even learn something, eventually".

 

Also, as Habu_69 noted, the ability to create your own scripts from start to end is what matters, if the OP doesn't know how Lua / MOOSE work, grabbing random bits of MOOSE code ain't gonna cut it (imho).

 

So, based on all that and on my personal MOOSE learning experience, I recommend LDT over Notepad++ without a doubt, that's what I was trying to say.

 

 

Now, I don't know about you, but I won't derail this thread by starting an argument over what MOOSE developers should or shouldn't have done. I don't think the OP cares about that, tbh.

Also, if a halfwit like myself managed to learn MOOSE by following those terrible instructions, perhaps they weren't THAT bad after all. :D

 

Cheers :thumbup:

Edited November 6, 2018 by Hardcard

[GunghoGW]

Ok I worked out the error

 

When I loaded the mouse framework I forgot to untick the create default template.

 

I simply deleted that framework, and reloaded Moose Framework, then the Moose Missions etc and everything is now working fine.

 

Regards

 

 

 

 

 

Sent from my iPhone using Tapatalk

[Muybonito523]

Month old thread, but has anyone had issues with MOOSE actually working? I just tried to do the simple GCICAP tutorial 1 after doing the setup because it had been a while since I have messed with moose. Nothing happens, I've tried spawning, nothing happens, its like even though moose is in the mission and I ask it to load at the beginning and my script, nothing happens, however, any mission that I load and use, works. I have even tried not using LDT and just posting a simple GCICAP script into the Do Script trigger, and nothing happens still.....

[Habu_69]

Did you check log to make sure MOOSE actually loaded. Should be a log entry near end of all the positionable registrations. Next check log for scripting errors. When developing, I usually place message at the end of the script "Script loaded" so that when in game I can see that the script processed without interruption.If these steps show no errors, then it is time to debug script.

Edited December 14, 2018 by Habu_69

[Muybonito523]

Didnt put any special messages at the end no, good idea, but yes there was a moode include start and end in the log, miz file has a 4mb moose.lua in it.